h323 inbound caller id name

Unanswered Question
Oct 14th, 2008

Question ,

I'm looking to enable caller id name on inbound caller h323 gateway . I've been looking for command reference, but havent' found anything great ,

!- System based configuration

router(conf-serv-h323)#h323

router(conf-serv-h323)#h225 display-ie ccm-compatible

!- H323 Class based configuration

router(config)#voice class h323 1

router(config-class)#h225 timeout ntf 100

router(config-class)#h225 display-ie ccm-compatible

router(config-class)#

!- Interface Configuration

router(config-class)#int s0/2/0:23

router(config-if)#isdn supp-service name calling

anything to watch out for ?

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 4 (1 ratings)
Loading.
Rick Arps Tue, 10/14/2008 - 12:55

I was able to get caller id name working on one of my pri's, the pri is from Windstream. Do an isdn q931 debug to make sure the telco is sending you the info. You may need to check with them to see how exactly they're sending it as well. I've got one from At&t that I can't get working, even though they say they're sending the info. Also, are you using h323 or mgcp? I know the h323 support for name was just recently added.

Here's a debug from my gateway that works:

Oct 14 16:50:20.585: ISDN Se0/3/0:23 Q931: RX <- SETUP pd = 8 callref = 0x02BD

Bearer Capability i = 0x9090A2

Standard = CCITT

Transfer Capability = 3.1kHz Audio

Transfer Mode = Circuit

Transfer Rate = 64 kbit/s

Channel ID i = 0xA18381

Preferred, Channel 1

Facility i = 0x9F8B0100A11002021ABC06072A8648CE1500040A0100

Protocol Profile = Networking Extensions

0xA11002021ABC06072A8648CE1500040A0100

Component = Invoke component

Invoke Id = 6844

Operation = InformationFollowing (calling_name)

Name information in subsequent FACILITY message

Progress Ind i = 0x8483 - Origination address is non-ISDN

Calling Party Number i = 0x2183, 'XXXXXXXXXX'

Plan:ISDN, Type:National

Called Party Number i = 0xC1, 'XXXXXXX'

Plan:ISDN, Type:Subscriber(local)

Oct 14 16:50:20.609: ISDN Se0/3/0:23 Q931: TX -> CALL_PROC pd = 8 callref = 0x82BD

Channel ID i = 0xA98381

Exclusive, Channel 1

Oct 14 16:50:20.725: ISDN Se0/3/0:23 Q931: TX -> ALERTING pd = 8 callref = 0x82BD

Progress Ind i = 0x8188 - In-band info or appropriate now available

Oct 14 16:50:20.793: ISDN Se0/3/0:23 Q931: RX <- FACILITY pd = 8 callref = 0x02BD

Facility i = 0x9F8B0100A11602021ABC020100800D43656C6C2050686F6E65204F48

Protocol Profile = Networking Extensions

0xA11602021ABC020100800D43656C6C2050686F6E65204F48

Component = Invoke component

Invoke Id = 188

Operation = CallingName

Name Presentation Allowed Extended

Name = Cell Phone OH

Hope this helps

Rick

colin.flanagan Sun, 02/15/2009 - 11:54

i've never seen this

Facility i = 0x9F8B0100A11602021ABC020100800D43656C6C2050686F6E65204F48

Protocol Profile = Networking Extensions

0xA11602021ABC020100800D43656C6C2050686F6E65204F48

Component = Invoke component

Invoke Id = 188

Operation = CallingName

Name Presentation Allowed Extended

Name = Cell Phone OH

must be a carrier issue , I think these are ATT pri's as well

Paolo Bevilacqua Sun, 02/15/2009 - 12:06

That is ASN.1 encoding and is very common. As you can see, the router doesn't have a problem in decoding it.

Actions

This Discussion