I know there is a article about MGCP and CallManager supporting Calling Party Name, is there no hope for H323 and Calling Party Name?
CORP-C3725-01#debug isdn q931
debug isdn q931 is ON.
*Mar 17 21:59:23.014 EST: ISDN Se2/0:23 Q931: RX <- SETUP pd = 8 callref = 0x02
Bearer Capability i = 0x8090A2
Standard = CCITT
Transfer Capability = Speech
Transfer Mode = Circuit
Transfer Rate = 64 kbit/s
Channel ID i = 0xA98381
Exclusive, Channel 1
Facility i = 0x9F8B0100A10F02010106072A8648CE1500040A0100
Progress Ind i = 0x8283 - Origination address is non-ISDN
Calling Party Number i = 0x2183, '9044914588'
Called Party Number i = 0xC1, '7391000'
*Mar 17 21:59:23.030 EST: ISDN Se2/0:23 Q931: TX -> CALL_PROC pd = 8 callref =
Channel ID i = 0xA98381
Exclusive, Channel 1
*Mar 17 21:59:23.250 EST: ISDN Se2/0:23 Q931: TX -> ALERTING pd = 8 callref = 0
*Mar 17 21:59:23.414 EST: ISDN Se2/0:23 Q931: RX <- FACILITY pd = 8 callref = 0
Facility i = 0x9F8B0100A116020101020100800E4141524F4E53204A41534F4E2052
*Mar 17 21:59:23.414 EST: ISDN Se2/0:23 **ERROR**: Ux_BadMsg: Invalid Message fo
r call state 7, call id 0x6A1, call ref 0x828B, event 0x62
*Mar 17 21:59:23.414 EST: ISDN Se2/0:23 Q931: TX -> STATUS pd = 8 callref = 0x8
Cause i = 0x80E262 - Message not compatible with call state or not imple
Call State i = 0x07
*Mar 17 21:59:23.534 EST: ISDN Se2/0:23 Q931: TX -> CONNECT pd = 8 callref = 0x
*Mar 17 21:59:23.566 EST: ISDN Se2/0:23 Q931: RX <- CONNECT_ACK pd = 8 callref
*Mar 17 21:59:23.566 EST: %ISDN-6-CONNECT: Interface Serial2/0:0 is now connecte
d to 9044914588 N/A
calling name is supported in the H.323 also however only in Display IE mode. H.323 can not decode Facility messages.
If i check the debug isdn q931, the calling name is being sent has a facility message. This is NOT SUPPORTED.
So your best bet is to ask the Telco to change it to display IE or change the gateway to MGCP.
Feel free to post if you have any further questions
It seems that Facility IE is the default Calling Party Name for most US carriers. Is this a H323 protocol issue, or a Cisco IOS bug? Seems this issue is more than 3 years old with no resolution. Telco will say this is a switch wide implementation, and can't be set on a per PRI basis, thus they can't change it.
Till the time i was in TAC (till last month) there has not been any FIX. I have worked with lot of US carriers and many have been able to send this in display IE format. However i will double check with few of my friends in TAC to see if there has been a enhancement fix for this issue.
Give me a days time.
Another thing, Did you call up and check with your Telco in regards to sending the name in display IE.
The issue is not fixed. I have double checked.There are few bug id's CSCdz72442 ,CSCdt03385.
So you best bet is to either convince the telco to change the format (which i think they can do) or change the protocol of the gateway to mgcp.
Feel free to post any questions you have in regards to this issue.
We have the same problem. Moving to MGCP is not a viable option, as you cannot do T.37 Faxing with MGCP. This is really an issue that Cisco needs to address and resolve if it's not an issue inherent to the H.323 protocol. I can clearly see the calling name in a q931 debug, so I know I am getting it. Suggesting that users force telco's to change the calling name format to a non standard format for a long term fix doesn't seem like the right way to handle this.
Not related to CM but rather CME, but thought I'd post it in case someone's searching. Supposedly this is scheduled to be fixed in the next CME release, Q2 2006.
Hopefully they'll fix it once and for all, everywhere.
Is there any update on this issue?
I am having a conference call with my telco provider tomorrow to determine the feasability of receiving the calling party name information in Display IE instead of Facility IE.... I dont see how it would be a huge deal to fix however as the text just scrolls across my terminal screen when I am doing a q931 debug ....
I haven't found a telco yet that will change their IE, or uses the same IE as Cisco. You'll have to switch to MGCP.
We asked for this bug to be fixed in 2001, so I doubt it will happen any time soon.
Major bummer. I need to have t.37 faxing capabilities so that rules out mgcp. Just got off the conference call and was told basically that my telco had no option to change this.