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

DID used instead of Two Stage Dialing, why?

I'm a bit puzzled by this behaviour. I'm trying to understand why DID is used  instead of two stage dialing.

Here's the setup. I have two voice gateways which are connected over E1  line. The two test phones are registered at the routers. CUCME version 8.5 is  used. The dial peers I have on the routers, where the called party is registered has the following dial peers:

dial-peer voice 7 pots
destination-pattern 0[2-9]......
port 0/2/0:15
!        
dial-peer voice 10 pots
destination-pattern 00[2-9].........
port 0/2/0:15
forward-digits 11
!
dial-peer voice 9011 pots
destination-pattern 000T
port 0/2/0:15
prefix 00

The caling number is 555444, so understandably the dial-peer 7 is selected:

Router# show call active voice brief

Telephony call-legs: 2

SIP call-legs: 0

H323 call-legs: 0

Call agent controlled call-legs: 0

SCCP call-legs: 0

Multicast call-legs: 0

Total call-legs: 2

11F1 : 59 13:30:54.311 UTC Tue Jul 23 2013.1 +16280 pid:7 Answer 5554444 active

dur 00:00:06 tx:339/56952 rx:347/55520

Tele 0/2/0:15 (59) [0/2/0.1] tx:6940/6940/0ms g711ulaw noise:-68 acom:6  i/0:-58/-79 dBm

11F1 : 60 13:31:09.321 UTC Tue Jul 23 2013.1 +1270 pid:20001 Originate 5552001 active

dur 00:00:06 tx:206/35432 rx:207/35604

Tele 50/0/1 (60) [50/0/1.0] tx:4120/4120/0ms g711ulaw noise:0 acom:0  i/0:0/0 dBm

Telephony call-legs: 2

SIP call-legs: 0

H323 call-legs: 0

Call agent controlled call-legs: 0

SCCP call-legs: 0

Multicast call-legs: 0

Total call-legs: 2

I understand why dial-7 was selected, but still... why at the calling site I don't hear another dial tone, and the call succeeds? By default DID is disabled on a POTS dial-peer, and that's exactly what I see here:

Router#show dial-peer voice 7

VoiceEncapPeer7

        peer type = voice, system default peer = FALSE, information type = voice,

        description = `',

        tag = 7, destination-pattern = `0[2-9]......',

        voice reg type = 0, corresponding tag = 0,

        allow watch = FALSE

        answer-address = `', preference=0,

        CLID Restriction = None

        CLID Network Number = `'

        CLID Second Number sent

        CLID Override RDNIS = disabled,

        rtp-ssrc mux = system

        source carrier-id = `', target carrier-id = `',

        source trunk-group-label = `',  target trunk-group-label = `',

        numbering Type = `unknown'

        group = 7, Admin state is up, Operation state is up,

        Outbound state is up,

        incoming called-number = `', connections/maximum = 1/unlimited,

        DTMF Relay = disabled,

        URI classes:

            Destination =

        huntstop = disabled,

        in bound application associated: 'DEFAULT'

        out bound application associated: ''

        dnis-map =

        permission :both

        incoming COR list:maximum capability

        outgoing COR list:minimum requirement

        Translation profile (Incoming):

        Translation profile (Outgoing):

        incoming call blocking:

        translation-profile = `'

        disconnect-cause = `no-service'

        advertise 0x40 capacity_update_timer 25 addrFamily 4 oldAddrFamily 4

        mailbox selection policy: none

        type = pots, prefix = `',

        forward-digits default

        session-target = `', voice-port = `0/2/0:15',

        direct-inward-dial = disabled,

        digit_strip = enabled,

        register E.164 number with H323 GK and/or SIP Registrar = TRUE

        fax rate = system,   payload size =  20 bytes

        supported-language = ''

        preemption level = `routine'

        bandwidth:

            maximum = 64 KBits/sec, minimum = 64 KBits/sec

        voice class called-number:

            inbound = `', outbound = `'

        dial tone generation after remote onhook = enabled

        mobility=0, snr=, snr_noan=, snr_delay=0, snr_timeout=0

        snr calling-number local=disabled, snr ring-stop=disabled, snr answer-too-soon timer=0

        Time elapsed since last clearing of voice call statistics never

        Connect Time = 4962, Charged Units = 0,

        Successful Calls = 0, Failed Calls = 0, Incomplete Calls = 0

        Accepted Calls = 4, Refused Calls = 0,

        Last Disconnect Cause is "10  ",

        Last Disconnect Text is "normal call clearing (16)",

        Last Setup Time = 7165078.

        Last Disconnect Time = 6903984.

And when I delete all dial-peers, the default dial-peer is used. But again, the same result, still not two stage dialing.

So I'm puzzled, why DID is used instead of two stage dialing?

1 ACCEPTED SOLUTION

Accepted Solutions
Hall of Fame Super Gold

Re: DID used instead of Two Stage Dialing, why?

In recent IOS, two stage dialing on isdn is disabled by default for security reasons.

You can re-enable it at your own risk:

http://www.cisco.com/en/US/tech/tk652/tk90/technologies_tech_note09186a0080b3e123.shtml

10 REPLIES
Green

DID used instead of Two Stage Dialing, why?

Boyan

Can you share

show dial-peer voice 20001

I think because the phones are registering with this gateway like CME DID will be used as it will always find a matching dial peer.

20001 will be created by the CME when the phone registers you do not build these yourself.

Regards,
Alex.
Please rate useful posts.

Regards, Alex. Please rate useful posts.
New Member

DID used instead of Two Stage Dialing, why?

Hi Alex,

Here, the output:

Router#show dial-peer voice 20001  

VoiceEncapPeer20001

        peer type = voice, system default peer = FALSE, information type = voice,

        description = `',

        tag = 20001, destination-pattern = `5552001$',

        voice reg type = 0, corresponding tag = 0,

        allow watch = FALSE

        answer-address = `', preference=0,

        CLID Restriction = None

        CLID Network Number = `'

        CLID Second Number sent

        CLID Override RDNIS = disabled,

        rtp-ssrc mux = system

        source carrier-id = `', target carrier-id = `',

        source trunk-group-label = `',  target trunk-group-label = `',

        numbering Type = `unknown'

        group = 20001, Admin state is up, Operation state is up,

        incoming called-number = `', connections/maximum = 0/unlimited,

        DTMF Relay = disabled,

        URI classes:

            Destination =

        huntstop = enabled,

        in bound application associated: 'DEFAULT'

        out bound application associated: ''

        dnis-map =

        permission :both

        incoming COR list:maximum capability

        outgoing COR list:minimum requirement

        Translation profile (Incoming):

        Translation profile (Outgoing):

        incoming call blocking:

        translation-profile = `'

        disconnect-cause = `no-service'

        advertise 0x40 capacity_update_timer 25 addrFamily 4 oldAddrFamily 4

        mailbox selection policy: none

        type = pots, prefix = `',

        forward-digits 0

        session-target = `', voice-port = `50/0/1',

        direct-inward-dial = disabled,

        digit_strip = enabled,

        register E.164 number with H323 GK and/or SIP Registrar = TRUE

        fax rate = system,   payload size =  20 bytes

        supported-language = ''

        preemption level = `routine'

        bandwidth:

            maximum = 64 KBits/sec, minimum = 64 KBits/sec

        voice class called-number:

            inbound = `', outbound = `'

        dial tone generation after remote onhook = enabled

        mobility=0, snr=, snr_noan=, snr_delay=0, snr_timeout=0

        snr calling-number local=disabled, snr ring-stop=disabled, snr answer-too-soon timer=0

        Time elapsed since last clearing of voice call statistics never

        Connect Time = 93127, Charged Units = 0,

        Successful Calls = 9, Failed Calls = 0, Incomplete Calls = 0

        Accepted Calls = 13, Refused Calls = 1,

        Last Disconnect Cause is "10  ",

        Last Disconnect Text is "normal call clearing (16)",

        Last Setup Time = 7166579.

        Last Disconnect Time = 7201064.

Indeed, the dial-peer 20001 is created by the CME. For that particular call, this is the outbound dial-peer. But again, DID is also disabled. I'm wandering, isn't DID only used for the inbound dial-peer? My understanding of DID is, that it only matters as an inbound parameter... maybe I'm wrong....

Green

DID used instead of Two Stage Dialing, why?

Boyan,

Can you add a dial peer to test

This should match only incoming calls from the PRI

!

dial-peer voice 1000 pots

description *** FOR INCOMING DIAL PEER MATCHING ***

incoming called-number .

port 0/2/0:15

!

I have intenionally left out the "direct-inward-dial" to see if this will force 2 stage dialling

Give it a try

Regards,
Alex.
Please rate useful posts.

Regards, Alex. Please rate useful posts.
New Member

DID used instead of Two Stage Dialing, why?

Hi Alex,

I did that, and below is the result when I establish a call. Yes, dial-peer 1000 is selected, but no two stage dialing.

Telephony call-legs: 2

SIP call-legs: 0

H323 call-legs: 0

Call agent controlled call-legs: 0

SCCP call-legs: 0

Multicast call-legs: 0

Total call-legs: 2

11F3 : 63 13:16:24.743 UTC Wed Jul 24 2013.1 +1610 pid:1000 Answer 5554444 active

dur 00:00:08 tx:433/72744 rx:439/70240

Tele 0/2/0:15 (63) [0/2/0.1] tx:8770/8770/0ms g711ulaw noise:-68 acom:6  i/0:-67/-79 dBm

11F3 : 64 13:16:24.753 UTC Wed Jul 24 2013.1 +1590 pid:20002 Originate 5552002 active

dur 00:00:08 tx:221/38012 rx:221/38012

Tele 50/0/2 (64) [50/0/2.0] tx:4420/4420/0ms g711ulaw noise:0 acom:0  i/0:0/0 dBm

New Member

DID used instead of Two Stage Dialing, why?

E1 Pri uses DID, not two stage dialing.

Under dial-peer voice pots at both side,add:

direct-inward-dial

isdn overlap-receiving

above command allow CME to receice DID  and q931 setup message forward dnis digit by digit

New Member

DID used instead of Two Stage Dialing, why?

Hi Lan,

When I add direct-inward-dial on the receiving dial-peer I get the same result. That's what I'm trying to understand, what's the difference?

"E1 Pri uses DID, not two stage dialing." - I didn't know that. By any chance, do you have a reference document on that?

isdn overlap-receiving - this command is only possible under the ISDN L3 logical interface, in my case its Serial 0/2/0:15.

I tired it, and the only effect I notice on the calling party is that I get longer delay. But still, no two stage dialing.

Another effect I noticed is when isdn overlap-receiving is configured under Serial0/2/0:15 and direct-inward-dialing is configured under the incomming dial-peer. Then, I don't see any delay. So my only guess is, that the DID configuration takes presedence....

I'm still confused....

Regards,

Boyan

Hall of Fame Super Gold

Re: DID used instead of Two Stage Dialing, why?

In recent IOS, two stage dialing on isdn is disabled by default for security reasons.

You can re-enable it at your own risk:

http://www.cisco.com/en/US/tech/tk652/tk90/technologies_tech_note09186a0080b3e123.shtml

New Member

DID used instead of Two Stage Dialing, why?

Amazing Paolo! That's exactly what I was looking for. Thank you! You rock.

It's a test setup and I'm aware of all the risks involved with Two Stage Dialing. Yet again, thank you. I just tried it

Hall of Fame Super Gold

Re: DID used instead of Two Stage Dialing, why?

Thank you for the nice rating and good luck!

Green

DID used instead of Two Stage Dialing, why?

Paolo,

Thanks for this update.

Great info ++5

Regards,
Alex.
Please rate useful posts.

Regards, Alex. Please rate useful posts.
941
Views
15
Helpful
10
Replies
CreatePlease to create content