Dialing long numbers over ISDN BRI

Answered Question
Feb 8th, 2007
User Badges:

[Reposting this since it hasn't shown up in 4 hours... hope it doesn't create a double post]


Does ISDN (I'm using basic-net3 switchtype) or CCME have a limitation of 20 digits on called-number digit strings passed to the CO/exchange?


I have a problem where my telco (Telstra) requires me to dial a convoluted sequence of digits to enable call-forward for particular numbers in my indial range. It looks as though CCME is only forwarding the first 20 digits to the BRI.


For simplicity to start with, I've been trying to get call-forward immediate to work, which has the following number sequence (i.e. this must be sent to CO):


* 21 callfwd-dest * * * numtobeforwarded #


where in the example below, I want to forward number 90001030 to 0400100200.


Here's the Q.931 debug:


Feb 9 01:09:40.622: ISDN BR0/0/0 Q931: Applying typeplan for sw-type 0x1 is 0x0 0x0, Calling num 90001030

Feb 9 01:09:40.626: ISDN BR0/0/0 Q931: Applying typeplan for sw-type 0x1 is 0x0 0x0, Called num *210400100200***90001030#

Feb 9 01:09:40.626: ISDN BR0/0/0 Q931: TX -> SETUP pd = 8 callref = 0x39

Bearer Capability i = 0x8090A3

Standard = CCITT

Transfer Capability = Speech

Transfer Mode = Circuit

Transfer Rate = 64 kbit/s

Channel ID i = 0x89

Exclusive, B1

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

Calling Party Number i = 0x0080, '90001030'

Plan:Unknown, Type:Unknown

Called Party Number i = 0x80, '*210400100200***9000'

Plan:Unknown, Type:Unknown

Feb 9 01:09:40.798: ISDN BR0/0/0 Q931: RX <- STATUS pd = 8 callref = 0xB9

Cause i = 0x82E470 - Invalid information element contents

Call State i = 0x01

Feb 9 01:09:40.818: ISDN BR0/0/0 Q931: RX <- SETUP_ACK pd = 8 callref = 0xB9

Channel ID i = 0x89

Exclusive, B1

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

Feb 9 01:09:40.822: ISDN BR0/0/0 Q931: TX -> INFORMATION pd = 8 callref = 0x39

Sending Complete

Called Party Number i = 0x80, '0840#'

Plan:Unknown, Type:Unknown

Feb 9 01:09:40.882: ISDN BR0/0/0 Q931: RX <- CALL_PROC pd = 8 callref = 0xB9

Feb 9 01:09:40.906: ISDN BR0/0/0 Q931: RX <- DISCONNECT pd = 8 callref = 0xB9

Cause i = 0x8281 - Unallocated/unassigned number

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

Feb 9 01:09:44.230: ISDN BR0/0/0 Q931: TX -> RELEASE pd = 8 callref = 0x39

Feb 9 01:09:44.282: ISDN BR0/0/0 Q931: RX <- RELEASE_COMP pd = 8 callref = 0xB9


As you can see the called-party number is being truncated after the 20th digit (unless this is just a limitation of the debug output).


It's not appropriate for me to do call forwarding within CCME itself, because I want this to take effect if the CCME box fails, so it needs to be enacted by the CO. (and also since CCME doesn't appear to support partial reroute/call deflection, every time it forwards a call, 2 BRI channels are hogged.)


Does anyone have any advice on this? Am I shagged?

Correct Answer by paolo bevilacqua about 10 years 5 months ago

Rarely you are shagged using cisco gear.

Please configure " isdn number called enbloc " to overcome the limit of 20 digits that you've experienced.

Remember to rate useful posts.

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (1 ratings)
Loading.
Correct Answer
paolo bevilacqua Thu, 02/08/2007 - 23:49
User Badges:
  • Super Gold, 25000 points or more
  • Hall of Fame,

    Founding Member

Rarely you are shagged using cisco gear.

Please configure " isdn number called enbloc " to overcome the limit of 20 digits that you've experienced.

Remember to rate useful posts.

b.henshaw Fri, 02/09/2007 - 00:03
User Badges:

This is exactly what I needed - thanks.


The call-forward is still broken, but I can now take this up with the telco.

Actions

This Discussion