I cant get caller ID to appear! HELP

[Conleyjo]

I have a VG 200 running vg200-i6s-mz.122-11.T10.bin IOS, with an NM-2V and FXO-M1 cards installed in the NM-2V. The VG 200 is an MGCP gateway, and I have Caller-id enable on the voice ports.

Call manager version is 3.3.3

I have one of the FXO ports set to an attendant DN number so all calls on that port go to an IP-Phone (7960) with a shared line. All the inbound calls show up as Unknown number from external call.

What am I missing here????

Thanks in advance
John

 

[talbotpat]

Do you have caller-id feature on the actual CO lines? Can you get a regular phone with caller-id or a standalone caller-id display device on the line to show caller-id on an inbound call? You can see what is going on with your inbound call by debugging at the VG200 console. 'debug vpm all' should be somewhat revealing.

 

[Conleyjo]

Caller ID does work when I plug in a phone to the co line. After running Debug, I see the VG200 is picking up the caller ID information, but it is not displaying that on the IP-Phone. In fact when I run "show call history" the caller ID information is there for the inbound calls. For some reason the Caller id is getting lost between the VG200 and the IP-Phone.

John

 

[jerake75]

I have the same setup as you, and asked the same questions to Cisco awhile back. You cannot do caller-id on FXO ports while the VG200 is running MGCP. It will work on H.323.

jerake

 

[Conleyjo]

How did you setup the VG200 on H.323? Did you create a h.323 trunk to the VG200?

Thanks John

 

[jerake75]

I have the VG200 setup file from Cisco; I can email it to you if you like. I followed it word for word for the H.323 setup.

TMH

 

[Conleyjo]

I would appreciate it!!! My wife is ready to pull the plug on my system at home because she wants Caller-ID.
Did you setup the VG200 as a h323 gateway in call manager or a trunk?

Thanks
John@ip-telecomm.com

 

[simonxts]

Are you sure Called-id is supported on the FXO ports? As far as I know this is a feature only supported (yet) on ccm 3.3 in combination with ISDN Qsig.

any comments?

 

[jerake75]

I had the same reaction when Cisco told me that MGCP/VG200 would not support caller ID - disbelief. Check out their forums if you want to see them telling others the same thing.

Tina

 

[Conleyjo]

Caller ID is supported with VIC-2FXO-M1 ports, and the ports are picking up the Caller ID. I see the information when I run debug. Its the communication between the gateway and the Call Manager that is giving me grief.

 

[jerake75]

http://forum.cisco.com/eforum/servl...Cmd=MB?cmd=display_location&location=.ee950f3

TMH

 

[jerake75]

Straight from the VG200 Data sheet:

In typical applications, the Cisco VG200 operates as an H.323 Version 2 VoIP gateway and communicates as an intelligent gateway device with the Cisco CallManager. The following features are supported in H.323 mode:

ISDN Primary Rate Interface (PRI) (T1/E1): Both user and network sides
ISDN BRI: Both user and network sides
T1 CAS FGD
E1 CAS R2
Interface Type E&M
-->Caller ID for FXO/FXS
Analog direct inward dial (DID)

The Cisco VG200 can also operate as an MGCP gateway under control of the Cisco CallManager. The following interface types are supported in MGCP mode:

VIC FXS
VIC FXO
T1/E1 PRI
T1 CAS
T1/E1 QSIG (CCM 3.3 required)
-->Caller ID for FXS
Analog direct inward dial (DID)

 

[Conleyjo]

Hey Jerake57 Could you e-mail me your VG200 Config file (and yes... please take out all the confidential info..) I would like to see the h.323 version since i am having trouble with inbound calling in H.323 gateway mode.

Thanks John
John@IP-Telecomm.com