I have a issue with calls coming from my Siemens PABX to my MS Exchange Voice mail system.
My setup is as follow,
My PSTN is connected to my Siemens PABX, The Siemens connects via 2 Qsig trunk to my CCM.
I have a IP Sip trunk from my CCM to my MS Exchange Server.
Calls from CCM system to Exchange works without any issues but when I call from a Siemens extension I get the following error on my gateway.
Could you guys please assist.
May 4 14:27:40.031 SAST: ISDN Se0/0/0:15 Q931: RX <- SETUP pd = 8 callref = 0x0039
Bearer Capability i = 0x8090A3
Standard = CCITT
Transfer Capability = Speech
Transfer Mode = Circuit
Transfer Rate = 64 kbit/s
Channel ID i = 0xA9838F
Exclusive, Channel 15
Facility i = 0x91AA068001008201008B0100A1200202371006042B0C0900A114040F4A555354494E204D41525348414C4C020101
Calling Party Number i = 0x0083, '9086'
Called Party Number i = 0x80, '13706'
High Layer Compat i = 0x9181
May 4 14:27:40.047 SAST: ISDN Se0/0/0:15 Q931: TX -> CALL_PROC pd = 8 callref = 0x8039
May 4 14:27:40.103 SAST: ISDN Se0/0/0:15 Q931: TX -> ALERTING pd = 8 callref = 0x8039
Facility i = 0x91AA06800100820100A10B02010106042B0C09018400
Progress Ind i = 0x8088 - In-band info or appropriate now available
May 4 14:27:40.243 SAST: ISDN Se0/0/0:15 Q931: TX -> CONNECT pd = 8 callref = 0x8039
Facility i = 0x91AA06800100820100A10B02010206042B0C09028400
Connected Number i = 0x80, '13706'
May 4 14:27:40.255 SAST: ISDN Se0/0/0:15 Q931: TX -> DISCONNECT pd = 8 callref = 0x8039
Cause i = 0x8090 - Normal call clearing
May 4 14:27:40.315 SAST: ISDN Se0/0/0:15 Q931: RX <- CONNECT_ACK pd = 8 callref = 0x0039
May 4 14:27:40.319 SAST: ISDN Se0/0/0:15 Q931: TX -> STATUS pd = 8 callref = 0x8039
Cause i = 0x80E2 - Message not compatible with call state or not implemented
Call State i = 0x0B
May 4 14:27:40.367 SAST: ISDN Se0/0/0:15 Q931: RX <- RELEASE pd = 8 callref = 0x0039
May 4 14:27:40.379 SAST: ISDN Se0/0/0:15 Q931: TX -> RELEASE_COMP pd = 8 callref = 0x8039
The call originates from Siemens, but you see CCM send out the disconnect immediately after the connect:
This is virtually always a problem with media - check over the gateway configuration (regions etc) to ensure that it is able to connect to Exchange using the correct codec.
Please rate helpful posts...
Ah - also, as the error you highlighted appears after the disconnect/disc_ack exchange, I wouldn't be too concerned about it. The call is already
You do often see that sort of message as CCM or the other end don't fully agree on or implement all the possible QSIG messages...