cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
5017
Views
0
Helpful
9
Replies

Information element not implemented

After implementing a new voice gateway, we are having problems receiving a call from ISDN. Layers 1 and 2 are functioning well. On debug ISDN standard I get a message 0x82E328 - Information element not implemented followed by 0x80E5 where the router disconnects the call with the message not compatible with call state error code.

The gateway is a mgcp gateway controlled by CM. Could anyone help with this issue?

9 Replies 9

JOSE TORRES
Level 1
Level 1

Can you post a copy of the isdn debug.

Run a debug isdn q931.

Here is the output from debug isdn q931

Nov 1 14:12:15.376: ISDN Se1/0:15 Q931: RX <- SETUP pd = 8 callref = 0x0080

Bearer Capability i = 0x8090A3

Standard = CCITT

Transer Capability = Speech

Transfer Mode = Circuit

Transfer Rate = 64 kbit/s

Channel ID i = 0xA98393

Exclusive, Channel 19

Calling Party Number i = 0x00C3,

show_data: bad length 0 size 10

Plan:Unknown, Type:Unknown

Called Party Number i = 0xC1, '5768410'

Plan:ISDN, Type:Subscriber(local)

Sending Complete

Nov 1 14:12:15.748: ISDN Se1/0:15 Q931: TX -> CALL_PROC pd = 8 callref = 0x8080

Channel ID i = 0xA98393

Exclusive, Channel 19

Nov 1 14:12:15.924: ISDN Se1/0:15 Q931: TX -> ALERTING pd = 8 callref = 0x8080

Progress Ind i = 0x8088 - In-band info or appropriate now available

Nov 1 14:12:20.296: ISDN Se1/0:15 Q931: TX -> CONNECT pd = 8 callref = 0x8080

Display i = 'Test Israel Extension'

Nov 1 14:12:20.384: ISDN Se1/0:15 Q931: RX <- STATUS pd = 8 callref = 0x0080

Cause i = 0x82E328 - Information element not implemented

Call State i = 0x07

Nov 1 14:12:20.388: ISDN Se1/0:15 Q931: RX <- CONNECT_ACK pd = 8 callref = 0x0080

Nov 1 14:12:20.740: ISDN Se1/0:15 Q931: TX -> DISCONNECT pd = 8 callref = 0x8080

Cause i = 0x80E5 - Message not compatible with call state

Nov 1 14:12:20.812: ISDN Se1/0:15 Q931: RX <- RELEASE pd = 8 callref = 0x0080

Nov 1 14:12:21.172: ISDN Se1/0:15 Q931: TX -> RELEASE_COMP pd = 8 callref = 0x8080

Many thanks

On the MGCP gateway endpoint config page check the option Display IE delivery and see if that helps. Make sure you reset the gateway (or do a no mgcp, mgcp ) on the gateway before testing a call..

Sankar Nair
UC Solutions Architect
Pacific Northwest | CDW
CCIE Collaboration #17135 Emeritus

It is already checked. The endpoint settings are as follows:

Network Locale: UK (even though it is in Israel)

PRI protocol type: PRI Euro

Protocol Side: User

Channel Selection order: Bottom Up

Channel IE type : Use number when 1B

PCM type: A law

Checked boxes:

Inhibit restarts at PRI initialisation

Display IE delivery

Re-directing Number IE delivery (outbound and Inbound)

Setup non ISDN Progress Indicator

Line Coding: HDB3

Framing: CRC4

Clock: External

What is frustrating about this issue is that layers 1 and 2 are OK. I have layer 1 active and Layer 2 MULTIPLE_FRAME_ESTABLISHED. From the Q931 debug the error code suggest that the voice gateway dropped the call because of a D channel error with the 'message not compatible with call state'. I know of a discrepency with the time settings whereby I am using the UK time on a gateway in israel but I cant see how that can effect the call establishment. Any ideas would be most welcome.

Also ask your SP if they need to tag the call with the calling/called party numbering plan as well as calling/called party IE number type. Default values for the above fields are Cisco Callmanager. Some SPs require you to tag them specifically as ISDN or National for the numbering plan and the IE number type as National.

Also if the Display IE was checked already, trying unchecking the option and see if that helps!

Make sure you make changes only one at a time, so that you can find out which option helped..

Hope that helps!!

Sankar Nair
UC Solutions Architect
Pacific Northwest | CDW
CCIE Collaboration #17135 Emeritus

Thanks for that info. I'll set up a call with the telco and check these things out. Interestingly I have received the following output from the show ccm-manager command:

Configuration Auto-Download Information

=======================================

Current version-id: {A422A6D8-CFD4-4B6F-A6C5-D833BB4BF024}

Last config-downloaded:3d01h

Current state: Waiting for commands

Configuration Download statistics:

Download Attempted : 2

Download Successful : 2

Download Failed : 0

Configuration Attempted : 2

Configuration Successful : 2

Configuration Failed(Parsing): 0

Configuration Failed(config) : 0

Last config download command: New Registration

Configuration Error History:

controller E1 1/0

interface serial 1/0:15

controller E1 1/0

interface Serial1/0:15

interface Serial1/0:15

controller E1 1/0

interface serial 1/0:15

controller E1 1/0

FAX mode: cisco

The configuration error history may indictate a problem with the configuration. I did a stop and start of the mgcp process to watch the endpoint renegotiation. Do you know if this output could be part of a previous misconfiguration or should it (as I suspect) reset itself and now I have configuration errors?

The interfaces are configured as follows:

controller E1 1/0

pri-group timeslots 1-31 service mgcp

interface Serial1/0:15

no ip address

no logging event link-status

isdn switch-type primary-net5

isdn incoming-voice voice

isdn bind-l3 ccm-manager

no cdp enable

JOSE TORRES
Level 1
Level 1

Have you checked that you and your provider are using the same switch type, make sure the correct switch type is selected in gateway endpoint config in callmgr.

L1 and L2 should not come up as Active and Multiple_frame_established if the switch type is set wrong.

Sankar Nair
UC Solutions Architect
Pacific Northwest | CDW
CCIE Collaboration #17135 Emeritus

Check this service parameter "DisableAlertingPI". The default value is False. If it is False, change it to True and see if that helps.

Regards,

Anup