Is MJ's CID different from Bellcore/US format in any way?

premudriy · Post by **premudriy** » Tue Oct 05, 2010 4:11 am

Hello people,

Recently I bought a Rosewill RNX-56USB modem from NewEgg. According to specs and some credible forum feedbacks that I have read, this modem is well capable of getting CID info from calls.

While testing, however, I found that I cannot make this particular modem recognize CIDs coming from the MagicJack.

I've seen some people on NewEgg also complaining about CID capability of this modem, but I wonder if they used this modem with MJ as well and that's why it didn't work.

So, does MJ using some non-standard CID format or something? Also, has anyone by some chance happened to try using this specific modem (RNX-56USB) with MagicJack for CID collection purposes?

sabresfan · Post by **sabresfan** » Tue Oct 05, 2010 5:17 am

I've heard of some people getting the caller id to work without the resistor fix or magicfeatures but not many. Look in the sticky section here for the resistor fix and look in the for sale section for magicfeatures. Both will provide caller id. The resistor fix just does the number while magicfeatures will provide caller id name. Personally I would go with magicfeatures as you get a bunch of features at a great price and they are continually upgrading this product.

premudriy · Post by **premudriy** » Tue Oct 05, 2010 5:22 am

sabresfan, thank you for replying. I'm already using a 100K Ohm resistor. My home phones (Uniden) display the CID info. It is just this modem that's not displaying the CID for some reason. I have tried connecting it with resistor and without resistor, but it still won't get CID from MJ.

premudriy · Post by **premudriy** » Tue Oct 05, 2010 10:14 pm

Another possibility is the voltage that MJ uses could cause the issues. The on-hook voltage is normal, around 47 volts, but ringing voltage is just on the edge of the allowed normal ringing voltage, 60 volts. But here comes the worst part: between the rings voltage drops to pity 22 volts.

I know that in CID capable modems there's a separate circuitry that captures the data even when the modem is on-hook and apparently the difference in ringing voltages causes this modem not to see the CID data. This is just a peculation though. If someone can correct me, please, do so.

Any other suggestions to try to make it work?

oldtimercurt · Post by **oldtimercurt** » Tue Oct 05, 2010 10:53 pm

Somewhere in one of Redpepper's posts he gives a pretty complete picture of MJ and CID. Since his outfit has developed so many of the really nifty gadgets for MJ, I'd give it some credence.

Took me about 3 minutes on search http://www.phoneservicesupport.com/the- ... t8011.html

OTC

premudriy · Post by **premudriy** » Tue Oct 05, 2010 11:41 pm

oldtimercurt wrote:Somewhere in one of Redpepper's posts he gives a pretty complete picture of MJ and CID. Since his outfit has developed so many of the really nifty gadgets for MJ, I'd give it some credence.

Took me about 3 minutes on search http://www.phoneservicesupport.com/the- ... t8011.html

OTC

Ok, that's very very helpful and explains a lot. I will try find someone with real/regular phone line and a caller id service and test: if my modem will pick up the CID, then MJ is really at fault and I should get the magic features. And if not, then it could be that NewEgg got a batch of faulty modems or modems intended for other countries/regions.

It still surprises me that many phones still get the CID even with this bug. I guess the RNX-56USB modem is an exception.

Thank you, Oldtimercurt.

redpepper · Post by **redpepper** » Wed Oct 06, 2010 5:00 am

The caller id is sent in Bellcore format. Based on your description, it should work.

For reference, your modem uses a Conexant chipset and needs the correct AT command "AT +VCID=1\xd\xa" to tell it to report the caller id. Reference http://www.blackice.com/Help/Tools/Voic ... Method.htm .

You should also check the customer feedback at NewEgg.com for this modem. A lot of people reported having the same problem as you but there are a few select people that did get caller id reporting to work.

Good Luck !!!

premudriy · Post by **premudriy** » Wed Oct 06, 2010 5:13 am

redpepper wrote:The caller id is sent in Bellcore format. Based on your description, it should work.

For reference, your modem uses a Conexant chipset and needs the correct AT command "AT +VCID=1\xd\xa" to tell it to report the caller id. Reference http://www.blackice.com/Help/Tools/Voic ... Method.htm .

Good Luck !!!

Thank you for your help, Redpepper. I have done extensive testing and jumped though hoops already with this modem (5 days of testing already).

I'm not sure what "\xd\xa" part is exactly, but I tried the following in the Hyperterminal:

at [ENTER]
OK
at+vcid=1 [ENTER]
OK

then I placed a few test calls on MagicJack and all I got back was:

RING

RING

RING

...

i.e. there was no usual NMBR or any sign of received CID.

I thought of possibility that I've got a faulty modem, but all other functions except CID work flawlessly (faxin, voice, DUN). As for reviews on NewEgg: I was wondering if those people also using this modem with MagicJack. I guess I will know once I test it with regular landline.

So, what is that "\xd\xa"? Should I type it literally like that in hyperterminal? I assumed that "at+vcid=1" sufficed because when I typed "at+vcid?" it showed "1", so seems like value was set.

I also tried messing with modem's region (using at+gci=_hex_value_) and still no success with CID. The default region is "B5" in hex, which I assume is correct for US and MagicJack, but I've tried other ones and it still didn't work. That's why I finally asked about region/format of CID on this forum.

[EDIT]: I see what "\xd\xa" is - that's for Voice C++ invocation. Nevertheless, I have not had success with hyperterminal and at+vcid=1.