Influencing Outbound Call based on the Internal Extension Number

[Mazzy Star]

Hi All,

I have my dial-peers in placed and I can influence what Voice Port they can go out to when a certain route pattern is dialed, I used trunk group.

My question is, how can I influence the outbound call based on the Dialling Voip Internal Extension Number?

I tried  creating a dial-pper with answer-address, but the call loops to the PLAR number configured on voice-port.

Config::

trunk group LOCAL-OUT
 max-calls voice 10
 max-retry 2
 description *** LOCAL CALLS ***
 hunt-scheme round-robin

voice-port 0/0/0
 trunk-group LOCAL-OUT 1
 supervisory disconnect dualtone mid-call
 supervisory custom-cptone PHIL
 timeouts call-disconnect 2
 timeouts wait-release 5
 timing hookflash-out 50
 timing guard-out 1000
 connection plar opx immediate 7600
 shutdown
 description *** OUTGOING - LOCAL OUT  ***
 bearer-cap Speech

voice class codec 711
 codec preference 1 g711ulaw
 codec preference 2 g711alaw
 codec preference 3 g729r8
!
!

dial-peer voice 1 pots
 trunkgroup LOCAL-OUT
 incoming called-number .
 no digit-strip
 forward-digits 4
!
dial-peer voice 2 voip
 description incoming dial-peer PSTN to VOIP
 session protocol sipv2
 session target sip-server
 session transport udp
 incoming called-number .
 voice-class codec 711
 voice-class sip dtmf-relay force rtp-nte
 dtmf-relay rtp-nte sip-notify
 no vad
!
dial-peer voice 3 voip
 description *** incoming INTERNAL ***
 destination-pattern [1-7]...$
 session protocol sipv2
 session target dns:cucm.internalserver.com
 incoming called-number .%
 voice-class codec 711
 dtmf-relay rtp-nte sip-notify
 no vad

[Carlo Poggiarelli · Accepted solution]

Hi.

In you are on a CUCM deployment, you can use CSS with different partition  and applying a  prefix before the call is routed to the VG.

Once on the VG, you can strip the prefix within the pots dialpeer.

HTH

Regards

Carlo

[Mazzy Star]

Hi Carlo,

This was a big help. Thank you!

But if I try to simulate that the line is busy by shutting  down the port, the call still goes out to another voice-port with similar Route Pattern.

Ex:

Dial Peer that Matches the Route Pattern with a Prefix 79

dial-peer voice 8103 pots
 port 0/0/0
 description *** outgoing local calls ***
 destination-pattern 79[2-9]......
 forward-digits 7

When the port down, the outgoing call goes to this dial-peer:

dial-peer voice 103 pots
 trunkgroup LOCAL-OUT
 description *** outgoing local calls ***
 destination-pattern [2-9]......
 no digit-strip
 forward-digits 7

What config should I do so it will not go out to the 103 dial-peer?

I tried (from dialpeer 3) changing the Forward-digits 7 to forward-digits-all, but it still goes out to dialpeer 103.

Thanks!

[Carlo Poggiarelli · Accepted solution]

Hi.

On dial-peer 8103 add huntstop command.

HTH

Regards

Carlo

[Mazzy Star]

Hi Carlo,

I tried putting a Huntstop for the DialPeer 8103, but when I ran the "sho dialplan number 795225777"

It still shows that the alternate dialpeer is Dialpeer103.

Thanks!

[Carlo Poggiarelli · Accepted solution]

Hi.

Try show dialplan number 795225777 hunt | i Match

Carlo

[Carlo Poggiarelli]

Hi.

Looking at your diaper I suggest to attach a # to the configured prefix on CUCM.

Than you can modify your dialpeer 8103 as follows:

dial-peer voice 8103 pots
 port 0/0/0
 description *** outgoing local calls ***
 destination-pattern #79[2-9]......
 forward-digits 7

In this case the only possible match would be diaper 8103

HTH

Cheers

Carlo

[Mazzy Star]

Thanks Carlo,

It worked! :) I'll just put a # sign for the prefix, #79.

Now it's only routed to dialpeer8103

router-voice#sh dialplan num #795225777
Macro Exp.: #795225777

VoiceEncapPeer8103

[Carlo Poggiarelli]

You are welcome 

Glad that worked ;)

[Mazzy Star]

Hi Carlo,

I have a dial-peer for IDD calls but I don't know how I can strip the #79 digits if I also need to influence it's outgoing route based on the internal extension. Since International call

dial-peer voice 200 pots
 trunkgroup LOCAL-OUT
 description *** outgoing IDD calls 1 ***
 destination-pattern 00T
 no digit-strip
 forward-digits all

dial-peer voice 8200 pots
 trunkgroup LOCAL-OUT
 description *** outgoing IDD calls 1 ***
 destination-pattern #7900T
 no digit-strip
 forward-digits all

Thanks!

[Carlo Poggiarelli]

Hi.

As I suggested, you need to create different partitions to include on new CSS that need to be assigned to dedicated users.

Than two route pattern for the same destination will exist but within different partitions and one with prefix attached and the other without any prefix.

Than pots dialpeers will strip specified digits if you don't add forward-digits all (as you did on your DP)

So try to remove forward digit keyword and add a different prefix for different destination,.

Eg

For local calls apply #77

For Long distance #78

For international #79

HTH

Regards

Carlo

[Mazzy Star]

Thanks Carlo,

Will try this, this weekend.

:)

[Mazzy Star]

Grazie Carlo! :)

I tested it, and it worked!

dial-peer voice 8400 pots
 trunkgroup LOCAL-OUT
 description *** outgoing ANY LENGTH LOCAL & TOLL  ***
 huntstop
 destination-pattern #8[^0][1-9].+

dial-peer voice 8500 pots
 trunkgroup LOCAL-OUT
 description *** outgoing ANY LENGTH NDD ***
 huntstop
 destination-pattern #80[2-9].+

dial-peer voice 8600 pots
 trunkgroup LOCAL-OUT
 description *** outgoing ANY LENGTH IDD ***
 huntstop
 destination-pattern #800[1-9].+

router-voice#sh dialplan num #80014185224646 | i Peer
VoiceEncapPeer8600

router-voice#sh dialplan num #887000 | i Peer
VoiceEncapPeer8400
router-voice#
router-voice#sh dialplan num #88878888 | i Peer
VoiceEncapPeer8400

router-voice#sh dialplan num #818662788187 | i Peer
VoiceEncapPeer8400
router-voice#sh dialplan num #80324958484 | i Peer
VoiceEncapPeer8500

Thanks so much!

Will just change it the Local, NDD, and IDD on the actual implem

#81

#82

#83

[Mazzy Star]

I tried also putting preference 1 with the huntstop, but it still sees the dial-peer 103

Thanks!