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. And see here for current known issues.

New Member

ISDN: Double Callling Party number

Hi all,

I have a strange behaviour on one of our ISDN line (again):

Everything is workin as expectes with one exception. One special external user tries to call

our operator (DN: 00) but the call will fail (its only this user experiencing the problem).

What debug isdn q931 gives us:

Jun 17 11:00:15 172.20.2.20 570949: 275747: Jun 17 11:01:36: ISDN BR0/0/1 Q931: RX <- SETUP pd = 8  callref = 0x01
Jun 17 11:00:15 172.20.2.20 570950:     Bearer Capability i = 0x9090A3
Jun 17 11:00:15 172.20.2.20 570951:             Standard = CCITT
Jun 17 11:00:15 172.20.2.20 570952:             Transfer Capability = 3.1kHz Audio
Jun 17 11:00:15 172.20.2.20 570953:             Transfer Mode = Circuit
Jun 17 11:00:15 172.20.2.20 570954:             Transfer Rate = 64 kbit/s
Jun 17 11:00:15 172.20.2.20 570955:     Channel ID i = 0x89
Jun 17 11:00:15 172.20.2.20 570956:             Exclusive, B1
Jun 17 11:00:15 172.20.2.20 570957:     Progress Ind i = 0x8183 - Origination address is non-ISDN 
Jun 17 11:00:15 172.20.2.20 570958:     Calling Party Number i = 0x2180, 'xxx190093001'     <----------- 1st number
Jun 17 11:00:15 172.20.2.20 570959:             Plan:ISDN, Type:National
Jun 17 11:00:15 172.20.2.20 570960:     Calling Party Number i = 0x2183, 'xxx19000'              <----------- 2nd number ?!?
Jun 17 11:00:15 172.20.2.20 570961:             Plan:ISDN, Type:National
Jun 17 11:00:15 172.20.2.20 570962:     Called Party Number i = 0x81, '00'
Jun 17 11:00:15 172.20.2.20 570963:             Plan:ISDN, Type:Unknown
Jun 17 11:00:15 172.20.2.20 570964: 275748: Jun 17 11:01:36: ISDN BR0/0/1 Q931: TX -> SETUP_ACK pd = 8  callref = 0x81
Jun 17 11:00:15 172.20.2.20 570965:     Channel ID i = 0x89
Jun 17 11:00:15 172.20.2.20 570966:             Exclusive, B1
Jun 17 11:00:18 172.20.2.20 570967: 275749: Jun 17 11:01:40: ISDN BR0/0/1 Q931: TX -> DISCONNECT pd = 8  callref = 0x81
Jun 17 11:00:18 172.20.2.20 570968:     Cause i = 0x809C - Invalid number format (incomplete number)

Here is a part of the config:

interface BRI0/0/0
no ip address
isdn switch-type basic-net3
isdn overlap-receiving T302 4000
isdn point-to-point-setup
isdn incoming-voice voice
isdn static-tei 0
!
interface BRI0/0/1
no ip address
isdn switch-type basic-net3
isdn overlap-receiving T302 4000
isdn point-to-point-setup
isdn incoming-voice voice
isdn static-tei 0
!
interface BRI0/2/0
no ip address
isdn switch-type basic-net3
isdn overlap-receiving T302 4000
isdn point-to-point-setup
isdn incoming-voice voice
isdn static-tei 0
!        
interface BRI0/2/1
no ip address
isdn switch-type basic-net3
isdn overlap-receiving T302 4000
isdn point-to-point-setup
isdn incoming-voice voice
isdn static-tei 0

!

!

dial-peer voice 10 voip
destination-pattern 45002.
session protocol sipv2
session target ipv4:172.21.82.251
dtmf-relay sip-notify
codec g711ulaw
no vad
!        
dial-peer voice 1 pots
description ISDN OUTGOING
translation-profile outgoing OUTGOING
destination-pattern 9.T
progress_ind setup enable 3
progress_ind alert enable 8
port 0/0/0
forward-digits all
!
dial-peer voice 2 pots
description ISDN OUTGOING
translation-profile outgoing OUTGOING
destination-pattern 9.T
progress_ind setup enable 3
progress_ind alert enable 8
port 0/0/1
forward-digits all
!
dial-peer voice 3 pots
description ISDN OUTGOING
translation-profile outgoing OUTGOING
destination-pattern 9.T
progress_ind setup enable 3
progress_ind alert enable 8
port 0/2/0
forward-digits all
!
dial-peer voice 4 pots
description ISDN OUTGOING
translation-profile outgoing OUTGOING
destination-pattern 9.T
progress_ind setup enable 3
progress_ind alert enable 8
port 0/2/1
forward-digits all
!
dial-peer voice 5 pots
translation-profile incoming INCOMING
incoming called-number ..?T
direct-inward-dial
forward-digits all
!
dial-peer voice 20 voip
destination-pattern 2000..T$
voice-class codec 1
session target ipv4:172.21.80.251
dtmf-relay h245-alphanumeric
!
dial-peer voice 21 voip
destination-pattern 46003.T$
voice-class codec 1
session target ipv4:172.21.80.251
dtmf-relay h245-alphanumeric

Has someone seen something similar or even hase a solution how this special call can be accepted?

Many Thanks,

Michael

4 REPLIES
Hall of Fame Super Gold

Re: ISDN: Double Callling Party number

I do not have the exact reference but I think per standard you can have only a calling number.

Consequently, you must complain to telco.

Super Bronze

Re: ISDN: Double Callling Party number

Hi

Are you in Germany?

I recall seeing things like that on a recent install...

It's not obvious from the section of the router config you have posted where 00 should be routed to? Perhaps post back the whole config.

Aaron

Aaron Please remember to rate helpful posts to identify useful responses, and mark 'Answered' if appropriate!
New Member

Re: ISDN: Double Callling Party number

Hi,

first of all thank you for your replies.

The ISDN line where this double calling number is seen is actual in Germany.

It looks like the incoming call comes from an analog line and maybe it uses some kind of overlapping.

Then it would not match the dial-peer voice 5 pots and would not be translated and so the call

could not be forwarded to any destination - but that's just a guess...

The "00" usual will be translated to 20000 and forwarded to a CUCM.

I've attached a snippet from the config with al relevant voice configuration.

Many thanks,

Michael

Super Bronze

Re: ISDN: Double Callling Party number

Hi Michael

As I recall this is 'normal' in Germany. It confused me a little when I found out you could have things like this example, with the 'office' number being diallable, as well as the longer (and randomly chosen by the person configuring the phone system) extension numbers are also diallable.

The two numbers are signalled in presumably so that you have visibility of a 'real' calling number as well as the administrator-created extension numbers...

Office/circuit number : 12319000

Extensions : 12319000100 - 12319000199

At any rate, I expect CME would at worst display the wrong CLI, rather than fail to route the call.

I think it would be worth you doing these two debugs:

debug voip dialpeer all   <------ to verify your inbound DP is being hit

debug voip translation    <------ verify the correct tx pattern is hit

Regards

Aaron

Aaron Please remember to rate helpful posts to identify useful responses, and mark 'Answered' if appropriate!
303
Views
0
Helpful
4
Replies