We have a global CUCM9.1 deployment and are having issues with one of our gateways in Hong Kong. This is only affecting International destinations through the gateway but results in the telco tearing down the call.
The telco have informed us that if we send an ISDN STATUS message that they will disconnect the call. Looking at a debug q931 on the gateway we are sending a STATUS message (step 3 below). Can anyone explain what the status message is and whether we can stop CUCM sending it ?
A Q931 from the gateway shows us this :-
1/ we send a TX SETUP to PCCW :-
Dec 11 04:35:18.943: ISDN Se0/0/0:23 Q931: TX -> SETUP pd = 8 callref = 0x00CC Bearer Capability i = 0x8090A2 Standard = CCITT Transfer Capability = Speech Transfer Mode = Circuit Transfer Rate = 64 kbit/s Channel ID i = 0xA98397 Exclusive, Channel 23 Display i = 'Michel xxxx' Calling Party Number i = 0x0081, '8910' Plan:Unknown, Type:Unknown Called Party Number i = 0x80, '00181xxxxxxxx' Plan:Unknown, Type:Unknown
2/ We receive a STATUS message (saying information elemnt not implemented), then an ACKNOWLEDGMENT from PCCW accepting the call on channel 23 :-
Dec 11 04:35:19.051: ISDN Se0/0/0:23 Q931: RX <- STATUS pd = 8 callref = 0x80CC Cause i = 0x82E3 - Information element not implemented Call State i = 0x01 hk1-crv-01# Dec 11 04:35:19.207: ISDN Se0/0/0:23 Q931: RX <- SETUP_ACK pd = 8 callref = 0x80CC Channel ID i = 0xA98397 Exclusive, Channel 23
3/ We then send a STATUS message cause code 0x80E1
Dec 11 04:35:19.447: ISDN Se0/0/0:23 Q931: TX -> STATUS pd = 8 callref = 0x00CC Cause i = 0x80E1 - Message type not implemented Call State i = 0x01
4/ We receive a disconnect from the telco – ie they tear down the call with a cause of 0x82E57D.
Dec 11 04:35:19.479: ISDN Se0/0/0:23 Q931: RX <- DISCONNECT pd = 8 callref = 0x80CC Cause i = 0x82E57D - Message not compatible with call state
5/ As requested from PCCW we tear the call down and send a RELEASE
Dec 11 04:35:19.991: ISDN Se0/0/0:23 Q931: TX -> RELEASE pd = 8 callref = 0x00CC Cause i = 0x80E5 - Message not compatible with call state hk1-crv-01# Dec 11 04:35:20.087: ISDN Se0/0/0:23 Q931: RX <- RELEASE_COMP pd = 8 callref = 0x80CC Cause i = 0x80E5 - Message not compatible with call state
You cannot control which ISDN messages CUCM sends, my understanding is that the ITU spec is pretty dictitorial. The better question here is what triggers the carrier to send us a STATUS with a progress indicator suggesting they didn't like our SETUP in the first place.
In HK I can take two guesses at this:
The IDD you are prefixing is wrong (i.e. maybe 007 instead of 001). I had a SIP turnup with Wharf T&T in Hong Kong which wouldn't accept international calls until I prefixed 007.
They don't like you passing CNAM (i.e. caller ID name) on an outgoing call. I have seen this with AT&T megacom PRIs here in the US. Try removing this from the serial interface then shut/not shut.
I suspect if you get the carrier to respond with a CALL_PROC instead of that strange STATUS message, you'll be back in business.
Sorry in the delay replying to this. The customer contact on site has been drip feeding information back to me and has been fairly vague about the resolution. The issue is resolved but this happened after a CUCM upgrade and a resync of the MGCP config on the gateway so it could have been down to either, or both :-(
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...
The below trick might come handy when you have to add a new node to a cluster but you don't have or is unsure of the security password for the publisher. This procedure has been around for ages.
1) Login into the CLI of the Publisher.