Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. If you'd prefer to explore, try our test area to get started. And see here for current known issues.

New Member

Invalid information element error in PRI call

Hi,

I am having difficulty getting past this error whenever I try to call across a back-to-back PRI connection. I have tried various isdn switch-types and CUCM settings for the MGCP port with no sucess. I'd appreciate it much if someone can tell me what's wrong with this config (also attached as text):

TIA.

CorpHQ#sh run
!
isdn switch-type primary-5ess
!        
controller T1 1/0
framing esf
clock source internal
linecode b8zs
pri-group timeslots 1-3,24 service mgcp
!
!
interface Serial1/0:23
no ip address
encapsulation hdlc
isdn switch-type primary-5ess
isdn incoming-voice voice
isdn bind-l3 ccm-manager
no cdp enable
!
voice-port 1/0:23
!
ccm-manager mgcp
ccm-manager music-on-hold
!
mgcp
mgcp call-agent 177.1.10.10 2427 service-type mgcp version 0.1
mgcp rtp unreachable timeout 1000 action notify
mgcp modem passthrough voip mode nse
mgcp package-capability rtp-package
mgcp package-capability sst-package
mgcp package-capability pre-package
no mgcp package-capability res-package
no mgcp timer receive-rtcp
mgcp sdp simple
mgcp rtp payload-type g726r16 static
!        
mgcp profile default
!        

CorpHQ#sh isdn stat
Global ISDN Switchtype = primary-5ess

%Q.931 is backhauled to CCM MANAGER 0x0003 on DSL 0. Layer 3 output may not apply

ISDN Serial1/0:23 interface
        dsl 0, interface ISDN Switchtype = primary-5ess
        L2 Protocol = Q.921 0x0000  L3 Protocol(s) = CCM MANAGER 0x0003
    Layer 1 Status:
        ACTIVE
    Layer 2 Status:
        TEI = 0, Ces = 1, SAPI = 0, State = MULTIPLE_FRAME_ESTABLISHED
    Layer 3 Status:
        0 Active Layer 3 Call(s)
    Active dsl 0 CCBs = 0
    The Free Channel Mask:  0x80000007
    Number of L2 Discards = 0, L2 Session ID = 118
    Total Allocated ISDN CCBs = 0
CorpHQ#

CorpHQ#
Nov 22 00:04:33.862: ISDN Se1/0:23 Q931: TX -> SETUP pd = 8  callref = 0x0003
        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 = 0x2881, '14071111003'
                Plan:National, Type:National
        Called Party Number i = 0xA8, '17577777001'
                Plan:National, Type:National
Nov 22 00:04:34.202: ISDN Se1/0:23 Q931: RX <- RELEASE_COMP pd = 8  callref = 0x8003
        Cause i = 0x82E470 - Invalid information element contents

PSTN-r4#sh run
!
isdn switch-type primary-5ess
!
!
!
voice service voip
allow-connections h323 to h323
allow-connections h323 to sip
allow-connections sip to h323
allow-connections sip to sip
redirect ip2ip
sip
  header-passing
!
controller T1 1/0
framing esf
clock source internal
linecode b8zs
pri-group timeslots 1-3,24
description == Voice Circuit to CorpHQ
!
interface Serial1/0:23
no ip address
encapsulation hdlc
isdn switch-type primary-5ess
isdn protocol-emulate network
isdn incoming-voice voice
no cdp enable
!        
!
!
voice-port 1/0:23
!
dial-peer voice 407 pots
preference 1
destination-pattern 10..
forward-digits all
prefix 1407111
!
!
telephony-service
load 7910 P00405000700
load 7960-7940 P0030702T023
max-ephones 2
max-dn 2
ip source-address 192.168.13.1 port 2000
auto assign 1 to 2
system message Welcome to PSTN
dialplan-pattern 1 7577777... extension-length 4
max-conferences 4 gain -6
web admin system name admin password cisco
web admin customer name johndoe password cisco
dn-webedit
time-webedit
transfer-system full-consult
create cnf-files version-stamp 7960 Feb 28 2002 23:57:08
!
!
ephone-dn  1  dual-line
number 7001
!        
!        
ephone  1
no multicast-moh
device-security-mode none
mac-address 0017.955B.0AC8
type 7960
button  1:1
!

PSTN-r4#sh isdn stat
Global ISDN Switchtype = primary-5ess
ISDN Serial1/0:23 interface
        ******* Network side configuration *******
        dsl 0, interface ISDN Switchtype = primary-5ess
    Layer 1 Status:
        ACTIVE
    Layer 2 Status:
        TEI = 0, Ces = 1, SAPI = 0, State = MULTIPLE_FRAME_ESTABLISHED
    Layer 3 Status:
        0 Active Layer 3 Call(s)
    Active dsl 0 CCBs = 0
    The Free Channel Mask:  0x80000007
    Number of L2 Discards = 0, L2 Session ID = 249

PSTN-r4#
Mar  1 09:36:27.978: ISDN Se1/0:23 Q931: RX <- SETUP pd = 8  callref = 0x0003
        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 = 0x2881, '14071111003'
                Plan:National, Type:National
        Called Party Number i = 0xA8, '17577777001'
                Plan:National, Type:National
Mar  1 09:36:27.990: ISDN Se1/0:23 Q931: TX -> RELEASE_COMP pd = 8  callref = 0x8003
        Cause i = 0x82E470 - Invalid information element contents

10 REPLIES
Green

Invalid information element error in PRI call

Hi,

This is a strage issue.

Reading release notes etc you may need to upgrade your IOS to the latest

available for your DRAM/FLASH capacity.

As a test can you apply this command to both routers

!

voice-port 1/0:23

shut

bearer-cap speech

no shut

!

HTH

Alex

Regards, Alex. Please rate useful posts.
Bronze

Invalid information element error in PRI call

what if you enable "deb ccm back events/messages", would you see any errors there?

_____ Please rate helpful posts Пожалуйста оценивайте полезные сообщения
Green

Invalid information element error in PRI call

Boris,

I have looked at a few urls re this error now,

They all seem to be saying that issue is to do with the ISDN bearer capabilities

Did you make the change I suggested.

Did it help ?

Regards

Alex

Regards, Alex. Please rate useful posts.
Green

Invalid information element error in PRI call

Boris

Another issue I have spotted

In the PSTN router

You will need to fix your dial peer

!

dial-peer voice 407 pots

preference 1

destination-pattern 10..

forward-digits all

prefix 1407111

!

Change this to :-

!

dial-peer voice 407 pots

preference 1

destination-pattern 10..

forward-digits all

prefix 1407111

incoming called-number .

direct-inward-dial

port 1/0:23

!

HTH

Alex

Please rate useful posts

Regards, Alex. Please rate useful posts.
New Member

Invalid information element error in PRI call

Hi, I made the following changes as you suggested...

CorpHQ(config)#voice-port 1/0:23
CorpHQ(config-voiceport)#shut
CorpHQ(config-voiceport)#bearer-cap speech
CorpHQ(config-voiceport)#no shut

CorpHQ#sh deb


The following ISDN debugs are enabled on all DSLs:

debug isdn error is             ON.
debug isdn q931 is              ON.   (filter is OFF)
Call Manager:
  Call Manager backhaul events debugging is on
  Call Manager backhaul packets debugging is on

CorpHQ#

// when I call from CorpHQ to PSTN, this is what I get...


Nov 25 16:17:36.519:
cmbh_rcv_callback: <-- Receiving backhaul msg for Se1/0:23 :
        | bk_msg_type = DATA_REQ
        | bk_chan_id (slot:port) = 1:0
        | Q.931 length = 71
        | Q.931 message type: SETUP
        | Q.931 message = 080200020504038090A21803A983811C159F8B0100A10F02010106072A8648CE1500040A0100200200F36C0D28813134303731313131303031700CA83137353737373737303031
Nov 25 16:17:36.535: ISDN Se1/0:23 Q931: TX -> SETUP pd = 8  callref = 0x0002
        Bearer Capability i = 0x8090A2
                Standard = CCITT
                Transfer Capability = Speech 
                Transfer Mode = Circuit
                Transfer Rate = 64 kbit/s
        Channel ID i = 0xA98381
                Exclusive, Channel 1
        Facility i = 0x9F8B0100A10F02010106072A8648CE1500040A0100
                Protocol Profile =  Networking Extensions
                0xA10F02010106072A8648CE1500040A0100
                Component = Invoke component
                        Invoke Id = 1
                        Operation = InformationFollowing (calling_name)
                                Name information in subsequent FACILITY message
        Net Specific Fa
CorpHQ#c i = 0x00F3
        Calling Party Number i = 0x2881, '14071111001'
                Plan:National, Type:National
        Called Party Number i = 0xA8, '17577777001'
                Plan:National, Type:National
Nov 25 16:17:36.575: ISDN Se1/0:23 Q931: RX <- STATUS pd = 8  callref = 0x8002
        Cause i = 0x80E4 - Invalid information element contents
        Call State i = 0x01
Nov 25 16:17:36.579:
cmbrl_send_pak: --> Sending backhauled msg for Se1/0:23 :
        | bk_msg_type = DATA_IND
        | bk_chan_id (slot:port) = 1:0
        | Q.931 length = 12
        | Q.931 message type: STATUS
        | Q.931 message = 080280027D080280E4140101
Nov 25 16:17:36.583: ISDN Se1/0:23 Q931: RX <- RELEASE_COMP pd = 8  callref = 0x8002
        Cause i = 0x82E470 - Invalid information element contents
Nov 25 16:17:36.587:
cmbrl_send_pak: --> Sending backhauled msg for Se1/0:23 :
        | bk_msg_type = DATA
CorpHQ#_IND
        | bk_chan_id (slot:port) = 1:0
        | Q.931 length = 10
        | Q.931 message type: RELEASE COMPLETE
        | Q.931 message = 080280025A080382E470

PSTN-r4#
.Nov 25 16:20:15.507: ISDN Se1/0:23 Q931: RX <- SETUP pd = 8  callref = 0x0003
        Bearer Capability i = 0x8090A2
                Standard = CCITT
                Transfer Capability = Speech 
                Transfer Mode = Circuit
                Transfer Rate = 64 kbit/s
        Channel ID i = 0xA98381
                Exclusive, Channel 1
        Facility i = 0x9F8B0100A10F02010106072A8648CE1500040A0100
                Protocol Profile =  Networking Extensions
                0xA10F02010106072A8648CE1500040A0100
                Component = Invoke component
                        Invoke Id = 1
                        Operation = InformationFollowing (calling_name)
                                Name information in subsequent FACILITY message
        Net Specific Fac i = 0x00F3
        Calling Party Number i = 0x2881
PSTN-r4#, '14071111001'
                Plan:National, Type:National
        Called Party Number i = 0xA8, '17577777001'
                Plan:National, Type:National
.Nov 25 16:20:15.523: ISDN Se1/0:23 Q931: TX -> STATUS pd = 8  callref = 0x8003
        Cause i = 0x80E4 - Invalid information element contents
        Call State i = 0x01
.Nov 25 16:20:15.523: ISDN Se1/0:23 Q931: TX -> RELEASE_COMP pd = 8  callref = 0x8003
        Cause i = 0x82E470 - Invalid information element contents
PSTN-r4#

// So I changed it to this but seems to have no difference, same error on both sides...

PSTN-r4#sh run | b dial-peer voice 407 pots
dial-peer voice 407 pots
preference 1
destination-pattern 10..
incoming called-number .
direct-inward-dial
port 1/0:23
forward-digits all
prefix 1407111
!

// when I call from PSTN to CorpHQ, this is what I get...

PSTN-r4#
Nov 25 16:25:40.899: ISDN Se1/0:23 Q931: Applying typeplan for sw-type 0xD is 0x2 0x1, Calling num 7577777001
Nov 25 16:25:40.907: ISDN Se1/0:23 Q931: Applying typeplan for sw-type 0xD is 0x0 0x0, Called num 14071111001
Nov 25 16:25:40.907: ISDN Se1/0:23 Q931: TX -> SETUP pd = 8  callref = 0x0084
        Bearer Capability i = 0x8090A2
                Standard = CCITT
                Transfer Capability = Speech 
                Transfer Mode = Circuit
                Transfer Rate = 64 kbit/s
        Channel ID i = 0xA98381
                Exclusive, Channel 1
        Progress Ind i = 0x8583 - Origination address is non-ISDN 
        Calling Party Number i = 0x2180, '7577777001'
                Plan:ISDN, Type:National
        Called Party Number i = 0x80, '14071111001'
                Plan:Unknown, Type:Unknown
Nov 25 16:25:40.951: ISDN Se1/0:23 Q931: RX <- RELEASE_COMP pd = 8  callref = 0x8084
        Cause i = 0x8081 - Unallocated/unassigned number
PSTN-r4#

Thanks.

-MG

Green

Invalid information element error in PRI call

MG,

at least now we are getting the number does not exist.

The called number is 14071111001

Where does this exist.

Regards

Alex

Regards, Alex. Please rate useful posts.
New Member

Invalid information element error in PRI call

4071111001 is located at the CorpHQ site under CUCM v.8.6 with a 2620XM as an MGCP GW. 7577777001 is located at the remote site "PSTN" under CME 4.0. I'm trying to get the call across the PRI between them. Strange that I would see "Information Element" error when calling from CorpHQ to PSTN but not the other way around. If there is an issue with LAPD as the error seems to indicate, then I should get the same error in both directions.

Anyway, here are the details for the PSTN CME router, one running on a 2620XM and the other with a replacement using a 2821 (just in case there was something wrong or incompatible with the NM-HDV or DSP's). Both still show the same error.

PSTN-r4#sh ver
Cisco IOS Software, C2600 Software (C2600-ADVENTERPRISEK9-M), Version 12.4(9)T7, RELEASE SOFTWARE (fc3)
System image file is "flash:c2600-adventerprisek9-mz.124-9.T7.bin"

Cisco 2620XM (MPC860P) processor (revision 2.0) with 253952K/8192K bytes of memory.

1 FastEthernet interface
8 Serial interfaces
4 Serial(sync/async) interfaces
2 Channelized T1/PRI ports
32K bytes of NVRAM.
49152K bytes of processor board System flash (Read/Write)

Configuration register is 0x2102

PSTN-r4#
PSTN-r4#sh voice dsp voice

DSP  DSP             DSPWARE CURR  BOOT                         PAK     TX/RX
TYPE NUM CH CODEC    VERSION STATE STATE   RST AI VOICEPORT TS ABORT  PACK COUNT
==== === == ======== ======= ===== ======= === == ========= == ===== ============
C549 010 04 {medium}   8.4.7 IDLE  idle         0 1/1:23    01     0          0/0
C549 010 01 {medium}   8.4.7 IDLE  idle      0  0 1/0:23    01     0          0/0
         02 {medium}   8.4.7 IDLE  idle         0 1/0:23    02     0          0/0
         03 {medium}   8.4.7 IDLE  idle         0 1/0:23    03     0          0/0
C549 011 01 {medium}   8.4.7 IDLE  idle      0  0 1/1:23    02     0          0/0
         02 {medium}   8.4.7 IDLE  idle         0 1/1:23    03     0          0/0
edsp 001 01 g711ulaw  0.1 IDLE  50/0/1.1    
edsp 002 02 g729r8 p  0.1 IDLE  50/0/1.2    
edsp 003 01 g729r8 p  0.1 IDLE  50/0/2.1    
edsp 004 02 g729r8 p  0.1 IDLE  50/0/2.2    

PSTN-r4#

// CUCM MGCP GW configuration:
PRI Protocol Type = PRI NI2
PRI Protocol Type Specific Information = only "Send Calling Name in Facility IE" is checked

// swapped PSTN with 2821 with this config and still has the same error...

Branch2#sh ver
System image file is "flash:c2800nm-adventerprisek9-mz.124-24.T4.bin"

Cisco 2821 (revision 53.51) with 1034240K/14336K bytes of memory.
Processor board ID FHK0848F253
2 Gigabit Ethernet interfaces
4 Serial interfaces
4 Serial(sync/async) interfaces
1 terminal line
2 Channelized/Clear T1/PRI ports
1 Virtual Private Network (VPN) Module
2 Voice FXO interfaces
1 cisco service engine(s)
DRAM configuration is 64 bits wide with parity enabled.
239K bytes of non-volatile configuration memory.
127488K bytes of ATA CompactFlash (Read/Write)

Configuration register is 0x2102

Branch2#sh voice dsp


DSP  DSP                DSPWARE CURR  BOOT                         PAK     TX/RX
TYPE NUM CH CODEC       VERSION STATE STATE   RST AI VOICEPORT TS ABORT  PACK COUNT
==== === == ======== ========== ===== ======= === == ========= == ===== ============
edsp 0001 01 g729r8 p  0.1 IDLE  50/0/1.1    
edsp 0002 02 g729r8 p  0.1 IDLE  50/0/1.2    
edsp 0003 01 g729r8 p  0.1 IDLE  50/0/2.1    
edsp 0004 02 g729r8 p  0.1 IDLE  50/0/2.2    


----------------------------FLEX VOICE CARD 0 ------------------------------
                           *DSP VOICE CHANNELS*

CURR STATE : (busy)inuse (b-out)busy out (bpend)busyout pending
LEGEND     : (bad)bad    (shut)shutdown  (dpend)download pending

DSP   DSP                 DSPWARE CURR  BOOT                         PAK   TX/RX
TYPE  NUM CH CODEC        VERSION STATE STATE   RST AI VOICEPORT TS ABRT PACK COUNT
===== === == ========= ========== ===== ======= === == ========= == ==== ============
                           *DSP SIGNALING CHANNELS*
DSP   DSP                 DSPWARE CURR  BOOT                         PAK   TX/RX
TYPE  NUM CH CODEC        VERSION STATE STATE   RST AI VOICEPORT TS ABRT PACK COUNT
===== === == ========= ========== ===== ======= === == ========= == ==== ============
C5510 001 01 {flex}        24.3.4 alloc idle      0  0 0/0/0     02    0         36/0
C5510 001 02 {flex}        24.3.4 alloc idle      0  0 0/0/1     06    0         36/0
------------------------END OF FLEX VOICE CARD 0 ----------------------------

Branch2#

TIA,

MG

New Member

Invalid information element error in PRI call

I forgot to mention that the CUCM has no Partitions/CSS configured on the DN's.

-MG

Green

Invalid information element error in PRI call

MG,

So the called number 14071111001 is valid in the CUCM side

On the CUCM look at the MGCP endpoint, in the inbound call section set the number of signalling digits to be ALL

Retry

Also I,m used to the UK so can you please make sure that the PRI /ISDN switch type selected is the same as the

config on the routers

They are both using

isdn switch-type primary-5ess

Regards

Alex

Regards, Alex. Please rate useful posts.
New Member

Invalid information element error in PRI call

Hi Alex,

I used "primary-5ess" on both routers and also defined it as the PRI type in CUCM. I also tried setting the Network Locale = US; tried "Called/Calling Party IE number type unknown" = National; also for 5ESS type I changed the PRI Protocol Type Specific Information section to having only "Display IE delivery" box checked. Still with the same error. I also tried "isdn outgoing ie display" and "isdn outgoing ie display codeset_0 shiftcode codeset_6" on  the s1/0:23 interfaces with no success.

Do you have a sample working config I can use to test placing a call between two PRI interfaces? I'm thinking of testing this next week with two 2821's just to rule out the possibility that there might be something causing this with the NM-HDV I'm using. I can test any GW protocol you have that you know works.

Thanks.

-Michael

2535
Views
0
Helpful
10
Replies