Calling Name not showing up on H.323 Gateway for Inbound Calls

Unanswered Question
May 7th, 2007
User Badges:
  • Bronze, 100 points or more

I have a 2821 gateway I've recently converted from MGCP to H.323. It has 2 PRIs to the PSTN, terminated on a VWIC-2MFT-T1 card.


When I receive an incoming call from the PSTN, the number shows up fine but I no longer see the name. It worked before, and I can verify it is being received from the Telco using "debug isdn q931".


In the Gateway configuration in CCM, I have "Display IE Delivery" checked. Is there something I'm missing?


isdn switch-type primary-ni

!

controller T1 0/1/0

framing esf

linecode b8zs

pri-group timeslots 1-24

!

controller T1 0/1/1

framing esf

linecode b8zs

pri-group timeslots 1-24

!

interface Serial0/1/0:23

no ip address

encapsulation hdlc

no logging event link-status

isdn switch-type primary-ni

isdn incoming-voice voice

trunk-group PSTN

no cdp enable

!

interface Serial0/1/1:23

no ip address

encapsulation hdlc

no logging event link-status

isdn switch-type primary-ni

isdn incoming-voice voice

trunk-group PSTN

no cdp enable

!

voice-port 0/1/0:23

!

voice-port 0/1/1:23

!

dial-peer voice 2 pots

description Calls from PSTN

incoming called-number ....

direct-inward-dial

!


Gateway IOS ver is 12.4(11)T1, CCM ver is 4.1(3)sr4d

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 3 (3 ratings)
Loading.
gogasca Mon, 05/07/2007 - 08:58
User Badges:
  • Green, 3000 points or more

Hi Johny,


If the Gateway is running MGCP and the CCM is running 3.3 or earlier, the Caller ID Name must be in the Display IE.


If the Gateway is running MGCP and the CCM is running 4.0 or higher, the

Caller ID Name can be Display or Facility IE.


If the Gateway is running H323 then CCM is not relevant and the Caller ID Name must be in the Display IE.


thisisshanky Tue, 05/08/2007 - 07:24
User Badges:
  • Purple, 4500 points or more

Gonz,


Any plans to fix this above issue indicated in the tac case collection ? There are situations where you cant use MGCP all the time, like NFAS trunk groups.

johnnylingo Tue, 05/08/2007 - 14:12
User Badges:
  • Bronze, 100 points or more

Grrr...my plan was to use H.323 for incoming calls, and MGCP for outbound. Might have to scratch that.

paolo bevilacqua Fri, 06/08/2007 - 16:40
User Badges:
  • Super Gold, 25000 points or more
  • Hall of Fame,

    Founding Member

You could try with SIP.

johnnylingo Tue, 11/06/2007 - 21:45
User Badges:
  • Bronze, 100 points or more

Do you have the specific IOS versions?

johnnylingo Fri, 11/09/2007 - 00:00
User Badges:
  • Bronze, 100 points or more

Super, thanks. Hopefully this feature will make its way to the T and mainline trains. I have a customer running an ISR, so convincing them to run the XW train in production is a hard sell. Generally, I prefer H.323 gateways to MGCP for stability and compatibility reasons.

mdeloach Tue, 03/11/2008 - 17:09
User Badges:

Is there an easy/obvious way to determine when this feature might make it into the T series?


I've been in and out of the feature lookup tool and release notes with out finding an answer.


The T series is about as much risk as we are willing to take, and this is a feature that we would really like to impliment.


joshuamarsh Fri, 05/09/2008 - 10:23
User Badges:

Check out CSCsm50874. Looks like Cisco is fixing this on CME. Any word if this will work for CallManager as well? Note the T release below in "fixed in."


CME: calling name in facility IE doesn't display on IP phone

Symptom:

CME 4.2 does not display calling name when sent in an ISDN facility IE message. The facility is received and interpreted correctly however it doesn't show up on the IP phone display.


Workaround:

IOS 12.4(11)XW3 and 12.4(15)XY correct display the calling name.


Fixed-In

12.4(19.3)T1

12.4(15)T5

12.4(15)XZ

12.4(11)XW7


paolo bevilacqua Fri, 05/09/2008 - 10:28
User Badges:
  • Super Gold, 25000 points or more
  • Hall of Fame,

    Founding Member

If it is fixed "for CME", will work for CM as well.

Actions

This Discussion