Call Forward All for inbound calls to external numbers

Answered Question
Mar 10th, 2008

Hi there,

We have the problem that we want to forward incoming external calls to a cell phone at sometime. However this does not work at the moment. When chosen call forward all to an external number and one rings the internal extension. This works fine. When somebody dials the DID number one hears ringing but no call is forwarded to the external destination.

Included you will find the script. Furthermore the debug of the successfull call transfer all when dialing the internal number and the debug of the non successfull call transfer all when the DID number is called.

I have this problem too.
0 votes
Correct Answer by Paolo Bevilacqua about 8 years 9 months ago

Hi, should be:

voice translation-profile doorschakel

translate called 4

the reason the "isdn map address" under bri0/1/0 is not working is because it should be like:

isdn map address . plan unknown type unknown

this command has the same effect like the translation-rule, so after it's fixed, you don't need both.

In fact "isdn map address" is simpler.

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (1 ratings)
Loading.
Paolo Bevilacqua Mon, 03/10/2008 - 12:40

Which exact IOS are you using? There's a candidate bug related to to the "invalid IE" you receive when placing the call.

In any case, please upgrade to XW6 and try again.

mamkreutz01 Mon, 03/10/2008 - 12:46

Hi there,

I am using the 12.4<11>XW5 release. Do you thin upgrading to the XW6 could solve this problem ?

mamkreutz01 Mon, 03/10/2008 - 13:13

Hi there,

Ok i did the upgrade to the XW6 release but the problem stays the same. I hear ring but no calls are forwarded to the external number.

Paolo Bevilacqua Mon, 03/10/2008 - 13:53

Hi, can you edit or produce a trace that starts with the incoming call form outside that has to be forwarded?

Previous traces have multiple calls and is not clear what is what.

mamkreutz01 Mon, 03/10/2008 - 13:57

Hi there,

Thanks for the quick reply. Look below for a single trace:

Mar 10 20:56:05.251: %LINK-3-UPDOWN: Interface BRI0/1/0, changed state to up

Mar 10 20:56:05.327: ISDN BR0/1/0 Q931: RX <- SETUP pd = 8 callref = 0x27

Sending Complete

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 = 0x8283 - Origination address is non-ISDN

Calling Party Number i = 0x2183, '455650910'

Plan:ISDN, Type:National

Called Party Number i = 0xA1, '433270325'

Plan:ISDN, Type:National

Mar 10 20:56:05.339: ISDN BR0/1/0 Q931: TX -> CALL_PROC pd = 8 callref = 0xA7

Channel ID i = 0x89

Exclusive, B1

Mar 10 20:56:05.343: ISDN BR0/1/0 Q931: Applying typeplan for sw-type 0x1 is 0x2

0x1, Calling num 0433270323

Mar 10 20:56:05.355: ISDN BR0/1/0 Q931: Applying typeplan for sw-type 0x1 is 0x2

0x1, Called num 0645388001

Mar 10 20:56:05.359: ISDN BR0/1/0 Q931: TX -> SETUP pd = 8 callref = 0x0B

Bearer Capability i = 0x8090A3

Standard = CCITT

Transfer Capability = Speech

Transfer Mode = Circuit

Transfer Rate = 64 kbit/s

Channel ID i = 0x82

Preferred, B2

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

Calling Party Number i = 0x2183, '0433270323'

Plan:ISDN, Type:National

Called Party Number i = 0xA1, '0645388001'

Plan:ISDN, Type:National

Sending Complete

Mar 10 20:56:05.547: ISDN BR0/1/0 Q931: RX <- STATUS pd = 8 callref = 0x8B

Cause i = 0x82E41E - Invalid information element contents

Call State i = 0x01

Mar 10 20:56:05.607: ISDN BR0/1/0 Q931: RX <- STATUS pd = 8 callref = 0x8B

Cause i = 0x82E46C - Invalid information element contents

Call State i = 0x01

Mar 10 20:56:05.647: ISDN BR0/1/0 Q931: RX <- CALL_PROC pd = 8 callref = 0x8B

Channel ID i = 0x8A

Exclusive, B2

Mar 10 20:56:07.975: ISDN BR0/1/0 Q931: RX <- PROGRESS pd = 8 callref = 0x8B

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

Mar 10 20:56:07.979: ISDN BR0/1/0 Q931: TX -> ALERTING pd = 8 callref = 0xA7

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

Mar 10 20:56:08.071: ISDN BR0/1/0 Q931: RX <- STATUS pd = 8 callref = 0x27

Cause i = 0x82E41E - Invalid information element contents

Call State i = 0x07

Mar 10 20:56:12.035: ISDN BR0/1/0 Q931: RX <- DISCONNECT pd = 8 callref = 0x8B

Cause i = 0x8290 - Normal call clearing

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

Mar 10 20:56:42.067: ISDN BR0/1/0 Q931: RX <- RELEASE pd = 8 callref = 0x8B

Cause i = 0x8290 - Normal call clearing

Mar 10 20:56:42.071: ISDN BR0/1/0 Q931: TX -> RELEASE_COMP pd = 8 callref = 0x0

B

Mar 10 20:56:42.091: ISDN BR0/1/0 Q931: TX -> DISCONNECT pd = 8 callref = 0xA7

Cause i = 0x8090 - Normal call clearing

Mar 10 20:56:42.147: ISDN BR0/1/0 Q931: RX <- RELEASE pd = 8 callref = 0x27

Mar 10 20:56:42.147: ISDN BR0/1/0 Q931: TX -> RELEASE_COMP pd = 8 callref = 0xA

7

Mar 10 20:56:52.191: ISDN BR0/1/0 Q931: Ux_DLRelInd: DL_REL_IND received from L2

Mar 10 20:57:03.407: ISDN BR0/1/0 Q931: L3_ShutDown: Shutting down ISDN Layer 3

Mar 10 20:57:03.459: %LINK-3-UPDOWN: Interface BRI0/1/0, changed state to down

Paolo Bevilacqua Mon, 03/10/2008 - 15:07

Hi, this is a bit strange, it appear that the calling side (455650910) is disconnecting first, the forwarded call is placed regularly, altought with two complans from the switch:

1st, setup message from router has progress indication IE (0x1e). That is about the bug I was mentioning before, CSCsi94745, it should be resolved in XW6 anyway

Then, calling number (IE 0x6c) is not in right format, how telco expect the calling number to be, probably without 0?

All in all is very strange. First of all I would like to see the call to be palced without IE complaints from the switch. To do this:

1. try 12.4(11)XJ4, and 2. fix the calling number.

Also, the trace "internalNumber" above I never see a connect message. How you can tell you were talking without connect message ?

mamkreutz01 Mon, 03/10/2008 - 23:09

How do i fix the calling number ? Is there a command in CME for it to do this ? Trace Internal Number the Cell Phone rings we did not pick up the call. In the situation of the CFA when calls are coming in from outside the cell phone never rings.

mamkreutz01 Mon, 03/10/2008 - 23:40

Hi there,

I removed the clid network-number command from the dial-peers. Result stays the same. Below a new trace of that:

Mar 11 06:38:33.029: %LINK-3-UPDOWN: Interface BRI0/1/0, changed state to up

Mar 11 06:38:33.101: ISDN BR0/1/0 Q931: RX <- SETUP pd = 8 callref = 0x2D

Sending Complete

Bearer Capability i = 0x8090A3

Standard = CCITT

Transfer Capability = Speech

Transfer Mode = Circuit

Transfer Rate = 64 kbit/s

Channel ID i = 0x8A

Exclusive, B2

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

Calling Party Number i = 0x2183, '455650910'

Plan:ISDN, Type:National

Called Party Number i = 0xA1, '433270325'

Plan:ISDN, Type:National

Mar 11 06:38:33.109: ISDN BR0/1/0 Q931: TX -> CALL_PROC pd = 8 callref = 0xAD

Channel ID i = 0x8A

Exclusive, B2

Mar 11 06:38:33.117: ISDN BR0/1/0 Q931: Applying typeplan for sw-type 0x1 is 0x2

0x1, Calling num 260

Mar 11 06:38:33.129: ISDN BR0/1/0 Q931: Applying typeplan for sw-type 0x1 is 0x2

0x1, Called num 0611395292

Mar 11 06:38:33.129: ISDN BR0/1/0 Q931: TX -> SETUP pd = 8 callref = 0x10

Bearer Capability i = 0x8090A3

Standard = CCITT

Transfer Capability = Speech

Transfer Mode = Circuit

Transfer Rate = 64 kbit/s

Channel ID i = 0x81

Preferred, B1

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

Calling Party Number i = 0x2183, '260'

Plan:ISDN, Type:National

Called Party Number i = 0xA1, '0611395292'

Plan:ISDN, Type:National

Sending Complete

Mar 11 06:38:33.281: ISDN BR0/1/0 Q931: RX <- STATUS pd = 8 callref = 0x90

Cause i = 0x82E41E - Invalid information element contents

Call State i = 0x01

Mar 11 06:38:33.341: ISDN BR0/1/0 Q931: RX <- STATUS pd = 8 callref = 0x90

Cause i = 0x82E46C - Invalid information element contents

Call State i = 0x01

Mar 11 06:38:33.377: ISDN BR0/1/0 Q931: RX <- CALL_PROC pd = 8 callref = 0x90

Channel ID i = 0x89

Exclusive, B1

Mar 11 06:38:37.749: ISDN BR0/1/0 Q931: RX <- PROGRESS pd = 8 callref = 0x90

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

Mar 11 06:38:37.753: ISDN BR0/1/0 Q931: TX -> ALERTING pd = 8 callref = 0xAD

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

Mar 11 06:38:37.821: ISDN BR0/1/0 Q931: RX <- STATUS pd = 8 callref = 0x2D

Cause i = 0x82E41E - Invalid information element contents

Call State i = 0x07

Mar 11 06:39:12.493: ISDN BR0/1/0 Q931: RX <- RELEASE pd = 8 callref = 0x2D

Cause i = 0x8A90 - Normal call clearing

Mar 11 06:39:12.497: ISDN BR0/1/0 Q931: TX -> RELEASE_COMP pd = 8 callref = 0xA

D

Mar 11 06:39:12.517: ISDN BR0/1/0 Q931: TX -> DISCONNECT pd = 8 callref = 0x10

Cause i = 0x8090 - Normal call clearing

Mar 11 06:39:12.761: ISDN BR0/1/0 Q931: RX <- RELEASE_COMP pd = 8 callref = 0x9

0

Cause i = 0x8090 - Normal call clearing

Paolo Bevilacqua Tue, 03/11/2008 - 03:27

Both 260 and the number that begins with 0 are causing invalid IE. perhaps telco wants the number without 0 or a different type/plan.

I will look for a way to not send the PI IE in setup, there should but I don't remember now.

mamkreutz01 Tue, 03/11/2008 - 03:40

Hi there,

Thanks for your quick reply. Yes if there is a way to get this working i would be very thankfull. It is a standard function should work, most customers of ours also want it.

Paolo Bevilacqua Tue, 03/11/2008 - 04:23

The thing is that is your telco switch that behave strangely, this works in all installations I've seen.

Anyway, try under bri:

no isdn outgoing ie pi

no isdn outgoing ie caller-number

The objective is to place a call without receiving status messages from switch.

mamkreutz01 Tue, 03/11/2008 - 04:46

Hi there,

Problem stays the same. Look for output below:

Mar 11 11:45:19.596: %LINK-3-UPDOWN: Interface BRI0/1/0, changed state to up

Mar 11 11:45:19.716: ISDN BR0/1/0 Q931: RX <- SETUP pd = 8 callref = 0x4F

Sending Complete

Bearer Capability i = 0x8090A3

Standard = CCITT

Transfer Capability = Speech

Transfer Mode = Circuit

Transfer Rate = 64 kbit/s

Channel ID i = 0x89

Exclusive, B1

Calling Party Number i = 0x2183, '650831293'

Plan:ISDN, Type:National

Called Party Number i = 0xA1, '433270325'

Plan:ISDN, Type:National

Mar 11 11:45:19.728: ISDN BR0/1/0 Q931: TX -> CALL_PROC pd = 8 callref = 0xCF

Channel ID i = 0x89

Exclusive, B1

Mar 11 11:45:19.732: ISDN BR0/1/0 Q931: Applying typeplan for sw-type 0x1 is 0x2

0x1, Calling num 260

Mar 11 11:45:19.744: ISDN BR0/1/0 Q931: Applying typeplan for sw-type 0x1 is 0x2

0x1, Called num 0611395292

Mar 11 11:45:19.748: ISDN BR0/1/0 Q931: TX -> SETUP pd = 8 callref = 0x2C

Bearer Capability i = 0x8090A3

Standard = CCITT

Transfer Capability = Speech

Transfer Mode = Circuit

Transfer Rate = 64 kbit/s

Channel ID i = 0x82

Preferred, B2

Called Party Number i = 0xA1, '0611395292'

Plan:ISDN, Type:National

Sending Complete

Mar 11 11:45:19.948: ISDN BR0/1/0 Q931: RX <- CALL_PROC pd = 8 callref = 0xAC

Channel ID i = 0x8A

Exclusive, B2

Mar 11 11:45:23.920: ISDN BR0/1/0 Q931: RX <- PROGRESS pd = 8 callref = 0xAC

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

Mar 11 11:45:23.924: ISDN BR0/1/0 Q931: TX -> ALERTING pd = 8 callref = 0xCF

Mar 11 11:45:55.820: ISDN BR0/1/0 Q931: RX <- RELEASE pd = 8 callref = 0x4F

Cause i = 0x8090 - Normal call clearing

Mar 11 11:45:55.824: ISDN BR0/1/0 Q931: TX -> RELEASE_COMP pd = 8 callref = 0xC

F

Mar 11 11:45:55.844: ISDN BR0/1/0 Q931: TX -> DISCONNECT pd = 8 callref = 0x2C

Cause i = 0x8090 - Normal call clearing

Mar 11 11:45:56.048: ISDN BR0/1/0 Q931: RX <- RELEASE_COMP pd = 8 callref = 0xA

C

Cause i = 0x8090 - Normal call clearing

Mar 11 11:46:06.188: ISDN BR0/1/0 Q931: Ux_DLRelInd: DL_REL_IND received from L2

mamkreutz01 Tue, 03/11/2008 - 04:48

The difference we have seen is that when a call forward functions to an external number that there is the entry:

Plan: Unknown Type: Unknown

When it is not functioning like above there is an entry in the trace:

Plan : ISDN Type: National

Maybe this helps ?

Paolo Bevilacqua Tue, 03/11/2008 - 05:04

Yes, try forcing type/plans unknown/unknown with a translation-profile for called number at either DP or voice-port level.

rule 1 // // type any unknown plan any unknown

Telco is definitely misbheaving by clearing the call without indicating an exact reason for that.

mamkreutz01 Tue, 03/11/2008 - 06:52

Hi there,

When we put in this rule at the voice port or at the DP then the to be forwarded call is directly disconnected. So no normal call clearing then.

Paolo Bevilacqua Tue, 03/11/2008 - 07:24

Send the trace again. Also send the trace when forward is successful from an internal phone.

Make sure there is a connect and you can talki for the latter, because the first trace you sent, did not showed connect.

Paolo Bevilacqua Tue, 03/11/2008 - 09:07

Hi, the forward from external is still palced isdn/national:

Mar 11 15:50:20.355: ISDN BR0/1/0 Q931: TX -> SETUP pd = 8 callref = 0x4F

Bearer Capability i = 0x8090A3

Standard = CCITT

Transfer Capability = Speech

Transfer Mode = Circuit

Transfer Rate = 64 kbit/s

Channel ID i = 0x82

Preferred, B2

Called Party Number i = 0xA1, '00611395292'

Plan:ISDN, Type:National

Sending Complete

How did you configured the voice translation-rule ? You need to tie it to a voice translation-profile that in turne is applied as outgoing at voice-port or DP level.

mamkreutz01 Tue, 03/11/2008 - 09:24

Hi there,

Look below for the configuration of the DP:

voice translation-rule 4

rule 1 // // type any unknown plan any unknown

voice translation-profile doorschakel

translate calling 4

voice-port 0/1/0

compand-type a-law

cptone NL

I tried to put here at the voice port the rule translation-profile outgoing doorschakel but then the external caller recieves no ring tone at all.

Furthermore i put it in the DP below:

dial-peer voice 10 pots

description Uitgaand lokaal

destination-pattern 0[1-9]T

port 0/1/0

forward-digits all

When i put the outgoing translation-profile here then i do not get a ring tone when calling from external.

Maybe a problem with the BRI configuration ?

Look below:

interface BRI0/1/0

description Nummer 043-3270323

no ip address

isdn switch-type basic-net3

isdn overlap-receiving

isdn point-to-point-setup

isdn incoming-voice voice

isdn map address type plan unknown type unknown

isdn sending-complete

no isdn outgoing ie progress-indicator

no isdn outgoing ie caller-number

isdn static-tei 0

Thanks in advance for your reply.

Correct Answer
Paolo Bevilacqua Tue, 03/11/2008 - 09:36

Hi, should be:

voice translation-profile doorschakel

translate called 4

the reason the "isdn map address" under bri0/1/0 is not working is because it should be like:

isdn map address . plan unknown type unknown

this command has the same effect like the translation-rule, so after it's fixed, you don't need both.

In fact "isdn map address" is simpler.

mamkreutz01 Tue, 03/11/2008 - 10:17

Hi there,

Thank you very very much. After applying the rule you mentioned everything is working fine now.

Your help is greatly appreciated.

Actions

This Discussion