Hi Paul:

Can you elaborate on how this works? Why do you have to enable DID?

dial-peer voice 1 pots

description - dummy dial peer to enable Direct inward dial

incoming called-number .

direct-inward-dial

port 0/0/0

!

Thanks,

Diego

There was a slight type on the config - it should read like this :

dial-peer voice 1 pots

description - dummy dial peer to enable Direct inward dial

incoming called-number .

direct-inward-dial

port 0/0/0:15 <---- PRI D channel

!

ISDN was designed to allow single stage dialing , meaning that a caller would dia a number, and the entire called number is passed to the called party and it should ring at this phone without any operator intervention.

To allow the voice gateway router to take the called number (otherwise known as the DNIS) from the Q931 setup message and match it on other dial peers, you need the POTS dial peer command 'direct-inward-dial'. With this command configured on a POTS dial peer, when a call comes in through the particular voice port , IOS will work through the list of dial peers. It will come to dial peer 1 , and since it has 'incoming called-number .', and the call came in on port 0/0/0:15, it will match on this dial peer. The DID command will then take the DNIS and this can be matched on other VOIP or POTS dial peers. Without the DID command, the caller woul just hear a secondary dial tone and they would need to enter the called number again as DTMF tones.

Hi,

Actually, no "port" command is not necessary for the incoming pots DP dedicated to direct-inward-dial.

I think this explains what is happening to me at the moment. I have a PRI PSTN trunk where I can see the DNIS info on the Q931 messages but yet I can't get the incoming calls to match any DNs. The callers get a dial-tone and then a fast-busy. Will creating this dummy dial-peer with the direct-inward-dial command fix this system system-wide or do I need to use it somewhere else?

Thanks,

Diego

You configure as above and that's it.

Had you reported the symptom of getting dialtone in the other thread, I could have suggested that before.

Yes, you are right I should have mentioned it. I didn't realize that was such an important clue at the time.

Rgds,

Diego

Hi Paul,

I am trying the following

dial-peer voice 70 pots

description - dummy dial peer to enable Direct inward dial

incoming called-number .

direct-inward-dial

port 0/3/0:23

!

When I enter this all incoming calls get the dreaded three increasing pitch tones. Without the command I receive the secondary dial-tone that you mentioned. Any ideas?

Thanks,

Diego

Actually, nevermind. I got it. Seems I need that dial-peer AND a translation profile on my PRI voiceport. Looks like I am good to go.

Thanks,

Diego

the thre tones suggest the router is looking at the incoming DNIS , failing to match on a dial peer and sending a clearing code of 1 - invalid/unassigned number.

Run 'debug isdn q931' and make a test call. Log this, and paste you current config here so we can check.

I got it working but maybe you could be so kind as to clear something up for me. I decided that it would be best to setup a simple translation scheme that trans DIDs to extension numbers on inbound calls and sends out the main office phone number as the calling number when any extension dials the PSTN. Something like this:

Inbound

4085551111 -> 201 (main PSTN to reception)

4085552222 -> 202

4085553333 -> 203

Outbound

201 -> 4085551111

202 -> 4085551111

203 -> 4085551111

What I did to accomplish this was to add a "incoming called" translation profile to my PRI (voice-port 0/3/0:23) and then an "outbound calling" to each of my dial-peer that match outbound calls.

My question is why did I have to apply the inbound to a voice-port but yet the outbound to the dial-peer? I tried to add the outgoing to the voice-port but it did not work. Why the difference?

Thanks,

Diego