04-30-2008 12:13 PM - edited 03-15-2019 10:23 AM
getting the following error when calling a dn.
Cause i = 0x82E1 - Message type not implemented
Dialing phone to phone (4 digit) works fine. Any thoughts? Route Plan Report shows no overlapping
04-30-2008 12:22 PM
Are you pulling this from your gateway or trace logs from your CUCM? Can you be a bit more specific about the DN you are calling? Is this an internal or external call?
04-30-2008 12:31 PM
Pulling it from debug q931 off the gw. Actual number is external coming in through PRI. It originates as an inbound 800#, terminating on the 9200 DID
04-30-2008 12:47 PM
Does dialing the DID number work? Can you post the full debug?
04-30-2008 12:53 PM
Dialing the terminating DID number does not work. Here is the debug
*Apr 30 20:55:14.010: ISDN Se2/0:23 Q931: RX <- SETUP pd = 8 callref = 0x03EB
Bearer Capability i = 0x8090A2
Standard = CCITT
Transfer Capability = Speech
Transfer Mode = Circuit
Transfer Rate = 64 kbit/s
Channel ID i = 0xA98381
Exclusive, Channel 1
Calling Party Number i = 0x2181, '6309558983'
Plan:ISDN, Type:National
Called Party Number i = 0x80, '9200'
Plan:Unknown, Type:Unknown
*Apr 30 20:55:14.062: ISDN Se2/0:23 Q931: TX -> SETUP_ACK pd = 8 callref = 0x83EB
Channel ID i = 0xA98381
Exclusive, Channel 1
*Apr 30 20:55:14.090: ISDN Se2/0:23 Q931: RX <- STATUS pd = 8 callref = 0x03EB
Cause i = 0x82E1 - Message type not implemented
Call State i = 0x06
*Apr 30 20:55:14.134: ISDN Se2/0:23 Q931: TX -> DISCONNECT pd = 8 callref = 0x83EB
Cause i = 0x80E5 - Message not compatible with call state
*Apr 30 20:55:14.158: ISDN Se2/0:23 Q931: RX <- RELEASE pd = 8 callref = 0x03EB
*Apr 30 20:55:14.202: ISDN Se2/0:23 Q931: TX -> RELEASE_COMP pd = 8 callref = 0x83EB
04-30-2008 01:09 PM
Message not compatible with call state:
The remote equipment received an unexpected message that does not correspond to the current state of the connection. This is usually due to a D-channel error.
http://www.cisco.com/en/US/docs/ios/12_0/debug/command/reference/disdn.html
04-30-2008 01:11 PM
Are you sure you have the correct ISDN switch type configured? Since this sounds like a D channel error, perhaps the signaling is not compatible? Does the error occur just on this DID?
04-30-2008 01:13 PM
yes, all other did's and 800 inbounds work fine
04-30-2008 02:11 PM
do all the other numbers come in on thru the SAME PRI??
or do they use a different PRI??
HTH
javalenc
if this helps, please rate
05-01-2008 04:57 AM
Did you port these numbers from another carrier? Perhaps they didn't port this DID correctly? Is it a part of another DID block or is a single number?
11-09-2010 02:16 PM
I know this is an old Post, but I am having the same issue with the exact same setup mess
age you are getting, it is only happening on one DID, Telco is saying
Gateway is sending a Set_ACK instead of Call Proceding thus
they are sending back a "Message type not Implemented". Did you ever r
esolve this?
11-10-2010 07:55 AM
Looks like you have an overlapping dialplan on that number somewhere.
The Setup_Ack is sent if overlap receiving is enabled. For MGCP that is controlled with 'Overlap Receiving Flag for PRI' service parameter in CM, and is enabled by default. For H323/SIP, issue 'no isdn overlap-receiving' which is disabled by default. That will prevent the setup_ack from going out.
The error from the provider is a result of either your provider not supporting overlap sending, or perhaps you are configured for the wrong ISDN switch type.
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: