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

Maximum Called Number digits through E1 PRI

Hi,

I need to dial a 25 digit number out of the E1 PRI terminated at 2851 VG (IOS:12.4(13r)T). First problem is CCM is only sending only 24 digits to the Voice gateway and secondly VG after receiving the 24 digits is not dialing out the entire string of digits. Here is the output of # debug isdn q931 .

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

Apr 22 11:35:27.138: ISDN Se0/0/0:15 Q931: Applying typeplan for sw-type 0x12 is 0x0 0x0, Calling num 4409502

Apr 22 11:35:27.142: ISDN Se0/0/0:15 Q931: Applying typeplan for sw-type 0x12 is 0x0 0x0, Called num 8092890120020008704

23837

Apr 22 11:35:27.142: ISDN Se0/0/0:15 Q931: TX -> SETUP pd = 8 callref = 0x1B1B

Bearer Capability i = 0x8090A3

Standard = CCITT

Transfer Capability = Speech

Transfer Mode = Circuit

Transfer Rate = 64 kbit/s

Channel ID i = 0xA9839B

Exclusive, Channel 27

Progress Ind i = 0x8183 - Origination address is non-ISDN

IRL_2851-02#

Calling Party Number i = 0x0081, '4409502'

Plan:Unknown, Type:Unknown

Called Party Number i = 0x80, '80928901200200087042'

Plan:Unknown, Type:Unknown

Apr 22 11:35:27.166: ISDN Se0/0/0:15 Q931: RX <- SETUP_ACK pd = 8 callref = 0x9B1B

Channel ID i = 0xA9839B

Exclusive, Channel 27

Apr 22 11:35:27.166: ISDN Se0/0/0:15 Q931: TX -> INFORMATION pd = 8 callref = 0x1B1B

Sending Complete

Called Party Number i = 0x80, '3837'

Plan:Unknown, Type:Unknown

Apr 22 11:35:27.178: ISDN Se0/0/0:15 Q931: RX <- CALL_PROC pd = 8 callref = 0x9B1B

Channel ID i = 0xA9839B

Exclusive, Channel 27

IRL_2851-02#

Apr 22 11:35:27.214: ISDN Se0/0/0:15 Q931: RX <- DISCONNECT pd = 8 callref = 0x9B1B

Cause i = 0x8A9C - Invalid number format (incomplete number)

Apr 22 11:35:27.218: ISDN Se0/0/0:15 Q931: TX -> RELEASE pd = 8 callref = 0x1B1B

Apr 22 11:35:27.226: ISDN Se0/0/0:15 Q931: RX <- RELEASE_COMP pd = 8 callref = 0x9B1B

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

Any thoughts on above will be appreciated .

7 REPLIES
Hall of Fame Super Gold

Re: Maximum Called Number digits through E1 PRI

Hi, you need "isdn number called enbloc XX" to send more than 20 digits.

Hope this helps, please rate post if it does!

Community Member

Re: Maximum Called Number digits through E1 PRI

Hello,

Thanks for the update from your side, I have given this command under the serial interface and it seems to be passing the entire digit string to the CO but the problem seems to be from CCM side also as I am only getting a 24 digit string on Gateway whereas I am dialing 25 digit string. Initially I was not able to dial a 25 digit string from an IP phone also but I have created a Trans Pattern 12 --> 8092 due to which now I have to dial 23 digits only. The String I am dialing from IP Phone is 12890120020008704238378 which gets translated to 8092890120020008704238378 (12 translated to 8902) but the digits which i receive at VG are 809289012002000870423837 (last digit truncated). The debug isdn q931 i am getting now is :

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

Apr 22 14:10:32.283: ISDN Se0/0/0:15 Q931: Applying typeplan for sw-type 0x12 is 0x0 0x0, Calling num 4409502

Apr 22 14:10:32.287: ISDN Se0/0/0:15 Q931: Applying typeplan for sw-type 0x12 is 0x0 0x0, Called num 8092890120020008704

23837

Apr 22 14:10:32.287: ISDN Se0/0/0:15 Q931: TX -> SETUP pd = 8 callref = 0x1C55

Bearer Capability i = 0x8090A3

Standard = CCITT

Transfer Capability = Speech

Transfer Mode = Circuit

Transfer Rate = 64 kbit/s

Channel ID i = 0xA98399

Exclusive, Channel 25

Progress Ind i = 0x8183 - Origination address is non-ISDN

IRL_2851-02#

Calling Party Number i = 0x0081, '4409502'

Plan:Unknown, Type:Unknown

Called Party Number i = 0x80, '809289012002000870423837'

Plan:Unknown, Type:Unknown

Apr 22 14:10:32.303: ISDN Se0/0/0:15 Q931: RX <- STATUS pd = 8 callref = 0x9C55

Cause i = 0x82E470 - Invalid information element contents

Call State i = 0x01

Apr 22 14:10:32.311: ISDN Se0/0/0:15 Q931: RX <- SETUP_ACK pd = 8 callref = 0x9C55

Channel ID i = 0xA98399

Exclusive, Channel 25

IRL_2851-02#

Apr 22 14:10:47.315: ISDN Se0/0/0:15 Q931: RX <- DISCONNECT pd = 8 callref = 0x9C55

Cause i = 0x829C - Invalid number format (incomplete number)

Apr 22 14:10:47.319: ISDN Se0/0/0:15 Q931: TX -> RELEASE pd = 8 callref = 0x1C55

Apr 22 14:10:47.327: ISDN Se0/0/0:15 Q931: RX <- RELEASE_COMP pd = 8 callref = 0x9C55

IRL_2851-02#

Apr 22 14:10:50.135: ISDN Se0/0/0:15 Q931: RX <- DISCONNECT pd = 8 callref = 0x9C4E

Cause i = 0x8090 - Normal call clearing

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

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

Re: Maximum Called Number digits through E1 PRI

Hi,

I came across this BUG "CSCdv66773" which affects CCM 3.0 and 3.1.

Symptoms:

CallManager currently will not accept more than 24 dialed digits when placing

a call. This can be an issue if using some patterns where an account or

authorization code must be dialed in conjuntion with an international call that

is 15 digits in length.

Condition:

Problem is observed in Cisco CallManager 3.2 and 3.3 software releases.

Workaround:

Rearchitect your dialplan so that you never have more than 24 digits

in the dial string.

Additionally -

CM continues to accept digits after max supported digits reached

CallManager is only capable of accepting a certain number of digits (24 as of CallManager 3.1(2c)) however if a route pattern allows for more than the max digits, CallManager will continue to accept these digits from the user, but will discard them. CallManager should play reorder tone when the maximum digits is reached.

My suggestion would be to do digit manipulation on the VG instead of the CallManager.

-> Sushil

Re: Maximum Called Number digits through E1 PRI

Hi,

I came across this BUG "CSCdv66773" which affects CCM 3.0 and 3.1.

Symptoms:

CallManager currently will not accept more than 24 dialed digits when placing

a call. This can be an issue if using some patterns where an account or

authorization code must be dialed in conjuntion with an international call that

is 15 digits in length.

Condition:

Problem is observed in Cisco CallManager 3.2 and 3.3 software releases.

Workaround:

Rearchitect your dialplan so that you never have more than 24 digits

in the dial string.

Additionally -

CM continues to accept digits after max supported digits reached

CallManager is only capable of accepting a certain number of digits (24 as of CallManager 3.1(2c)) however if a route pattern allows for more than the max digits, CallManager will continue to accept these digits from the user, but will discard them. CallManager should play reorder tone when the maximum digits is reached.

This issue is resolved in UCM 4.0 and onwards.

Do let us know the UCM version you are running. Since if you are running UCM 4.0 or later the issue might be soething else.

However try and see if you can do the following -

My suggestion would be to do digit manipulation on the VG instead of the CallManager.

-> Sushil

Community Member

Re: Maximum Called Number digits through E1 PRI

Hello Sushil,

While working on the issue I also came across this bug but as I am currently running 4.1(3) it should not be a problem. I also used digit manipulation on the gateway and now i am prefixing a 4 digit string. Also in the q931 logs i can see the entire 25 digit string going out of the gateway but from the CO side I am receiving "Invalid IE Contents". I think I will have to work with the service provider and check what digits they are receiving at their end.

Thank You very much both of you for your timely and important suggestions .

-Sunil

Community Member

Re: Maximum Called Number digits through E1 PRI

from looking at your cause code I found this

"82E470"

82- the public network near the local user (local telco switch)

E4

The remote equipment receives a message that includes invalid information in the information element.

This cause indicates that the equipment receives an information element that is implemented, but one or more of the fields in the information element are coded differently.

This issue occurs due to a D-channel error.

I would work with your service provider

Re: Maximum Called Number digits through E1 PRI

remove digit strip from the callmanager to send all 25 numbers to the VG.

670
Views
4
Helpful
7
Replies
CreatePlease to create content