Solved: CME - Forwarding an incoming call to an external dest (ISDN)

SebastianV · ‎08-13-2009

Greetings,

I am having trouble forwarding an incoming (ISDN BRI) call to an external (same ISDN BRI) destination. Any help is greatly appreciated.

I have an extension 794 on an IP Phone. It will act as an attendant phone. It will be used to forward to a group of phones by extension 100 (using overlays). When everybody is gone, the extension will have a CFWDALL to an external destination.

1) Incoming ISDN calls to the IP phone work.

2) Outgoing calls from the IP phone to ISDN work.

3) Another IP phone calling the IP phone with an external CFWDALL destination works.

4) Incoming call being forwarded to the external destination via CFWDALL doesn't work.

The cause code is:

Cause i = 0x82E46C - Invalid information element contents

I suspect that the Telco doesn't like my outbound calling number (which is the same as the inbound calling number). However, I would have expected a cause code of:

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

I thought I'd have handled the calling number issue with my translation profile 111 below....

paolo bevilacqua · ‎08-13-2009

Your CO is indeed a bit strange, as it doesn't disconnect immediately.

However, try

interface bri 0/0

isdn map address . type unknown plan unknown

Then, you should use isdn tei-negotiation preserve, configure trunk-group if using both BRIs, I also think you don't need to use 0 for a PBX in the Netherlands, due to the fact that all numbers begin with 0 or 1.

View solution in original post

SebastianV · ‎08-13-2009

The shortened config:

isdn switch-type basic-net3

isdn tei-negotiation first-call

!

voice service voip

allow-connections h323 to h323

no supplementary-service h450.2

no supplementary-service h450.3

h323

!

voice translation-rule 110

rule 1 /^.*/ /294233794/

!

voice translation-rule 111

rule 1 /^1../ /0294233794/

rule 2 /^737/ /0294234737/

rule 3 /^794/ /0294233794/

!

voice translation-profile 110

translate calling 110

!

voice translation-profile 111

translate calling 111

!

voice translation-profile outgoing

!

translation-rule 1

Rule 1 ^.% 00 national national

Rule 2 ^.% 000 international international

!

interface BRI0/0

no ip address

isdn switch-type basic-net3

isdn tei-negotiation first-call

isdn point-to-point-setup

isdn incoming-voice voice

isdn static-tei 0

!

interface BRI0/1

no ip address

shutdown

isdn switch-type basic-net3

isdn tei-negotiation first-call

isdn point-to-point-setup

isdn incoming-voice voice

isdn static-tei 0

!

voice-port 0/0

translation-profile outgoing algemeen

translate calling 1

compand-type a-law

cptone NL

bearer-cap 3100Hz

!

voice-port 0/1

translation-profile outgoing algemeen

translate calling 1

compand-type a-law

cptone NL

bearer-cap 3100Hz

!

ccm-manager music-on-hold

!

dial-peer cor custom

!

dial-peer voice 10 pots

translation-profile outgoing algemeen

destination-pattern 0.T

incoming called-number .

direct-inward-dial

port 0/0

!

num-exp 29423473. 73.

num-exp 29423379. 79.

num-exp 29423426. 26.

!

telephony-service

load 7960-7940 P00307020200

max-ephones 30

max-dn 100

ip source-address 192.168.254.252 port 2000

auto assign 1 to 10

calling-number local

timeouts interdigit 3

time-format 24

date-format dd-mm-yy

create cnf-files version-stamp 7960 Apr 01 2009 03:38:08

max-conferences 4 gain -6

call-forward pattern .T

web admin system name ccmadministrator password c1sc0

dn-webedit

time-webedit

transfer-system full-consult

transfer-pattern .T

login timeout 10 clear 01:10

!

ephone-dn 1

number 101

name 101

translation-profile outgoing 111

!

ephone-dn 2

number 102

name 102

translation-profile outgoing 111

!

ephone-dn 3

number 103

name 103

translation-profile outgoing 111

!

ephone-dn 4

number 104

name 104

translation-profile outgoing 111

!

ephone-dn 5

number 794

name 105

call-forward all 00622222222

translation-profile outgoing 111

!

ephone-dn 6

number 106

name 106

translation-profile outgoing 111

!

ephone-dn 7

number 107

name 107

translation-profile outgoing 111

!

ephone-dn 8

number 108

!

ephone-dn 9

number 109

name 109

translation-profile outgoing 111

!

ephone-dn 10

number 737

name 737

call-forward all 00650271110

translation-profile outgoing 111

!

ephone-dn 11

number 262

name 262

translation-profile outgoing 111

!

ephone-dn 12

translation-profile outgoing 111

!

ephone-dn 98 dual-line

number 100

huntstop channel

no huntstop

!

ephone-dn 99 dual-line

number 100

preference 1

huntstop channel

!

ephone 1

mac-address 000D.28D7.6D2C

type 7940

button 1o1,98,99

!

ephone 2

mac-address 000D.28F3.58D0

type 7940

button 1o2,98,99

!

ephone 3

mac-address 000C.85BE.6388

type 7940

button 1o3,98,99

!

ephone 4

mac-address 000C.8546.561B

type 7940

button 1o4,98,99

!

ephone 5

mac-address 000D.28D7.56E4

type 7940

button 1:5

!

ephone 6

mac-address 000D.28D7.6D2B

type 7940

button 1o6,98,99

!

ephone 7

mac-address 000D.28F3.5C4C

type 7940

button 1o7,98,99

!

ephone 8

mac-address 000D.28D7.6D23

type 7940

button 1o98,99

!

ephone 9

mac-address 0008.E31B.840E

type 7940

button 1o9,98,99

!

ephone 10

mac-address 000D.28F3.5932

type 7940

button 1:10

!

ephone 11

mac-address 0018.1924.2CD0

type ata

button 1:11

!

ephone 12

mac-address 1819.242C.D001

type ata

button 1:8

!

paolo bevilacqua · ‎08-13-2009

You configuration is a bit messed up, unreferenced voice-translation rule, mixed with deprecated translation-rules, etc.

In general, apply translation-rule on the voice-port or trunk-group only, so you don't need them on a bunch of DPs and ephone-dn.

However, post output of "debug isdn q931" for the failed forwarded call. Do not enable any other debug. Most likely, the problem is with numbering type/plan, that being copied from the incoming call, becomes incorrect.

SebastianV · ‎08-13-2009

Sorry for the mess. I have been trying too much on this router and should indeed clean up.

My mobile calling the landline (incoming): 622208999

The main number at the office: 294233794

The external destination: 00523620666

The debug:

Jul 1 19:51:46.668: %ISDN-6-LAYER2DOWN: Layer 2 for Interface BR0/0, TEI 0 changed to down

Jul 1 19:51:46.672: ISDN BR0/0 Q931: Ux_DLRelInd: DL_REL_IND received from L2

Jul 1 19:51:49.028: ISDN BR0/0 Q931: RX <- SETUP pd = 8 callref = 0x06

Sending Complete

Bearer Capability i = 0x8090A3

Standard = CCITT

Transfer Capability = Speech

Transfer Mode = Circuit

Transfer Rate = 64 kbit/s

Channel ID i = 0x89

Calling Party Number i = 0x2183, '622208999'

Plan:ISDN, Type:National

Calling Party Number i = 0x2183, '622208999'

Plan:ISDN, Type:National

Called Party Number i = 0xA1, '294233794'

Plan:ISDN, Type:National

Jul 1 19:51:49.084: %ISDN-6-LAYER2UP: Layer 2 for Interface BR0/0, TEI 0 changed to up

Jul 1 19:51:49.092: ISDN BR0/0 Q931: Applying typeplan for sw-type 0x1 is 0x2 0x1, Calling num 00622208999

Jul 1 19:51:49.104: ISDN BR0/0 Q931: Applying typeplan for sw-type 0x1 is 0x2 0x1, Called num 0523620666

Jul 1 19:51:49.104: ISDN BR0/0 Q931: TX -> CALL_PROC pd = 8 callref = 0x86

Channel ID i = 0x89

Jul 1 19:51:49.124: ISDN BR0/0 Q931: TX -> SETUP pd = 8 callref = 0x59

Bearer Capability i = 0x9090A3

Standard = CCITT

Transfer Capability = 3.1kHz Audio

Transfer Mode = Circuit

Transfer Rate = 64 kbit/s

Channel ID i = 0x82

Calling Party Number i = 0x2183, '00622208999'

Plan:ISDN, Type:National

Called Party Number i = 0xA1, '0523620666'

Plan:ISDN, Type:National

Sending Complete

Jul 1 19:51:49.316: ISDN BR0/0 Q931: RX <- STATUS pd = 8 callref = 0xD9

Cause i = 0x82E46C - Invalid information element contents

Call State i = 0x01

Jul 1 19:51:49.404: ISDN BR0/0 Q931: RX <- CALL_PROC pd = 8 callref = 0xD9

Channel ID i = 0x8A

Jul 1 19:51:50.492: ISDN BR0/0 Q931: RX <- PROGRESS pd = 8 callref = 0xD9

Progress Ind i = 0x8282 - Destination address is non-ISDN

Jul 1 19:51:50.516: ISDN BR0/0 Q931: TX -> PROGRESS pd = 8 callref = 0x86

Progress Ind i = 0x8282 - Destination address is non-ISDN

Jul 1 19:51:54.644: ISDN BR0/0 Q931: RX <- DISCONNECT pd = 8 callref = 0xD9

Cause i = 0x8290 - Normal call clearing

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

Jul 1 19:52:16.452: ISDN BR0/0 Q931: RX <- RELEASE pd = 8 callref = 0x06

Cause i = 0x84EF - Protocol error; unspecified

Jul 1 19:52:16.460: ISDN BR0/0 Q931: TX -> RELEASE_COMP pd = 8 callref = 0x86

Jul 1 19:52:16.496: ISDN BR0/0 Q931: TX -> RELEASE pd = 8 callref = 0x59

Cause i = 0x84EF - Protocol error; unspecified

Jul 1 19:52:16.564: ISDN BR0/0 Q931: RX <- RELEASE_COMP pd = 8 callref = 0xD9

SebastianV · ‎08-13-2009

Would you also normally use separate dial peers for incoming and outgoing calls? If I'd define a separate dial peer for incoming calls, could I delete the num-exp commands?

paolo bevilacqua · ‎08-13-2009

Your CO is indeed a bit strange, as it doesn't disconnect immediately.

However, try

interface bri 0/0

isdn map address . type unknown plan unknown

Then, you should use isdn tei-negotiation preserve, configure trunk-group if using both BRIs, I also think you don't need to use 0 for a PBX in the Netherlands, due to the fact that all numbers begin with 0 or 1.

SebastianV · ‎08-13-2009

It works! Really appreciated your help. I will now start cleaning up the config first. In your opinion, do I need the rules 110 and 111?

Regarding the isdn tei-negotiation preserve part, we do have the problem (in The Netherlands and Belgium) that the Telco does energy saving, for which I was advised to use tei-negotiation first-call. Would that pose a problem?

paolo bevilacqua · ‎08-13-2009

You use rules only when something doesn't work or numbers do not show up right. For example, add 00 to international calls as in translation-rule you have.

ISDN BRI disactivate layer 1 in all the world except north america. In your case tei negotiation doesn't apply as you have static tei. Go ahead, enable second BRI in a trunk-group, and remove 0 for external calls, your user will like that, as they will be able to dial just like being home.

Please remember to rate useful posts with the scrollbox below.

SebastianV · ‎08-13-2009

Thanks, 2nd BRI is not present, so it's just the 2 voice ports. I'll clean up the rest.

edit: oh crap, you got me there ;)

paolo bevilacqua · ‎08-13-2009

1 voice-port for BRI, even if it supports two calls :)

Thanks for the nice rating and good luck.