I have upgraded our call managers 3.3(3) in hopes of getting Caller Name Delivery from the PSTN through the Facilities IE.
We are recieving the Caller Name in the Facilities IE Caller Name according the the carrier and I see it in the debug of ISDN q931
14w3d: ISDN Se1/0:23 Q931: RX <- SETUP pd = 8 callref = 0x010F
Bearer Capability i = 0x8090A2
Standard = CCITT
Transer Capability = Speech
Transfer Mode = Circuit
Transfer Rate = 64 kbit/s
Channel ID i = 0xA9838B
Exclusive, Channel 11
Facility i = 0x9F8B0100A10F02010106072A8648CE1500040A0100
Progress Ind i = 0x8283 - Origination address is non-ISDN
Calling Party Number i = 0x2183, '4325505980'
Called Party Number i = 0xC1, '6856584'
14w3d: ISDN Se1/0:23 Q931: TX -> CALL_PROC pd = 8 callref = 0x810F
Channel ID i = 0xA9838B
Exclusive, Channel 11
14w3d: ISDN Se1/0:23 Q931: TX -> ALERTING pd = 8 callref = 0x810F
14w3d: ISDN Se1/0:23 Q931: RX <- FACILITY pd = 8 callref = 0x010F
Facility i = 0x9F8B0100A117020101020100800F5045524D49414E204D494352
14w3d: ISDN Se1/0:23 **ERROR**: Ux_BadMsg: Invalid Message for call state 7
l id 0x2779, call ref 0x810F, event 0x62
14w3d: ISDN Se1/0:23 Q931: TX -> STATUS pd = 8 callref = 0x810F
Cause i = 0xC0E562 - Message not compatible with call state
Call State i = 0x07
14w3d: ISDN Se1/0:23 Q931: RX <- DISCONNECT pd = 8 callref = 0x010F
Cause i = 0x8090 - Normal call clearing
14w3d: ISDN Se1/0:23 Q931: TX -> RELEASE pd = 8 callref = 0x810F
14w3d: ISDN Se1/0:23 Q931: RX <- RELEASE_COMP pd = 8 callref = 0x010F
The debug show me bad message on facilities IE.
We have all of our routers configured H.323 gateways.
Is Caller Name Supported in H.323 or just MGCP. If it is only MGCP does anyone know when it will be supported on a H.323 Gateway.
Release notes only specify Non-QSIG trunks. They do not specify MGCP or H.323. I have it working with MGCP on a 3.3(3) CM. I just upgraded to 3.3(3) at another customer running H.323 and it was not showing up. I did verify the Teleco was sending it.
This PRI is connected to a SBC PRI and we will be switching it to MGCP to support the facilities IE.
IF you have H.323 Gateways the Call Name Delivery must come in the Display IE field. This is according to TAC.
Calling name delivery is supported on H.323 and MGCP gateways. To see the Calling name in the facilites IE you need to have a Q.Sig trunk and Call Manager 3.3. Otherwise, the MGCP/H.323 gateway needs to send the Calling name in the Display IE variable. And you can enable the Display IE Delivery checkbox under the gateway configuration.
Sorry for my ignorance, but how would I go about checking to see if I have this, or if I dont, implementing this? We will be doing the upgrade to 3.3(3) in the next month or two, but if only that wont do it I would like to know now.
We have a pri comming into our MRP 8 FXS on our ICS 7750 (with a 1 mft vic) and is setup as a MGCP gateway.
You don't need QSIG trunks, that's a separate capability in 3.3. Calling Name in Facilities IE is for non-QSIG trunks on CCM MGCP-controlled gateways. Calling Name in Facilities IE is not supported by CCM for H.323 gateways.
So is this only supported in 3.3(3). We are currently running 3.3(2) and would like to get the Caller information sent over in the Facilities field from a Nortel switch. Connected using MGCP and a 6608 blade.
You also have to be running MGCP on your gateway if you want to recieve the caller name in the Facilities IE field.
Seems to be conflicting responses here, could someone clarify what is / is not supported with H.323 re IE name display? I'm currently debugging name delivery with 3.3(3) and H.323 gateway using Facilities ID field for name and if it's not supported... I could be doing better things!
I am the person that opened this thread I also Called TAC and have verifed that H.323 does not support caller name in the Facilities IE it only supports caller Name if it is delivered in the Display IE. If you have an MGCP Gateway and Call Manager 3.3.3 Caller name is supported in Facilities IE and it works. I had a gateway that was configured as H.323 and moved it to MGCP and the Caller Name Started working properly from the Telco
Best of Luck
Thanks for the response... I did also open a TAC case and was told the same. However in my case I can't use MGCP because the gateway is a 7206 which is currently not supported as an MGCP gateway in CCM. Obvious next question is: When will MGCP on 7206 be supported by CCM?
Does anyone know if the 6608 with Skinny is supported for this? If so is there any peticular settings?
I would be curious to know what you hear. It seems the 7200 is not considered to be part of an "AVVID" solution, and the impression I got was there was never plans to support this.
If you hear otherwise, add it to this thread.
For what it's worth, it has been reiterated to me (through a contact who has ins with the BU) that there are no plans to introduce CCM/MGCP (IP-PBX) features to the Cisco 7200 platform at this time.