outbound call routing - Page 2

Yudistira Aditya Pradana · ‎02-29-2016

Hi All,

I had some headache for a month. i trying to configure outbound call with specific line ISDN, here is my configuration for outbound :

dial-peer cor custom

name 1xx

name 8xx

name 2xx

name 5xx

!

dial-peer cor list Allow1xx

member 1xx

member 2xx

!

dial-peer cor list Allow8xx

member 8xx

member 5xx

!

dial-peer voice 1 pots

corlist outgoing Allow1xx

tone ringback alert-no-PI

translation-profile incoming 2

translation-profile outgoing 1

destination-pattern 9.T

progress_ind setup enable 3

progress_ind alert enable 8

progress_ind progress enable 8

progress_ind connect enable 8

incoming called-number 81..

no digit-strip

direct-inward-dial

port 0/1/0:15

forward-digits all

!

dial-peer voice 3 pots

corlist outgoing Allow8xx

tone ringback alert-no-PI

translation-profile incoming 2

translation-profile outgoing 1

destination-pattern 9.T

progress_ind setup enable 3

progress_ind alert enable 8

progress_ind progress enable 8

progress_ind connect enable 8

incoming called-number 88..

no digit-strip

direct-inward-dial

port 0/2/0:15

forward-digits all

!

i want my 2xx extension outbound call through same ISDN line with 1xx, and then my 5xx through same ISDN line with 8xx.

but with the configuration above, my outbound calls still round robin, i'm already googling but still stuck.

Any body could help me please ?

Yudistira Aditya Pradana · ‎03-03-2016

Hi Vivek.

no, actually what i was want to achieve is all outbound calls from extension 2xx should be translated to 28548100 and outbound calls from 5xx should be translated into 28548800, where the 28548100 number is on port 0/1/0:15 and 28548800 is on port 0/2/0:15.

So that's why i wanted my 2xx extensions outbound call use same line with 1xx and my 5xx same line with 8xx.

Thank you :).

Vivek Batra · ‎03-03-2016

Ok, then translations should look like as;

voice translation-rule 5
Rule 1 /^2..$/ /28548100/

voice translation-rule 6
Rule 1 /^5..$/ /28548800/

- Vivek

Yudistira Aditya Pradana · ‎03-03-2016

Hi Vivek,

So it will look like this :

voice translation-rule 5
Rule 1 /^2..$/ /28548100/

voice translation-rule 6
Rule 1 /^5..$/ /28548800/

voice translation-profile out_2xx
translate calling 5

voice translation-profile out_5xx
translate calling 6

voice-port 0/1/0:15
translation-profile incoming 3
translation-profile outgoing out_2xx <-- Adding Here
cptone ID
timeouts initial 1
timeouts interdigit 2
bearer-cap Speech

voice-port 0/2/0:15
translation-profile incoming 3
translation-profile outgoing out_5xx <--Adding Here
cptone ID
timeouts initial 1
timeouts interdigit 2
bearer-cap Speech
!

And my existing outbound call will running well ? in example my ANI 801 will go out as 28548801 and so on ? Or should be placed on my dial-peer pots ?

Thank you

Vivek Batra · ‎03-03-2016

Hi,

To change the ANI for 2XX and 5XX, translations seem good as long as you are getting 3 digits ANI from CUCM, but I have noticed that you are getting 8 digits ANI from CUCM, Is it? (as configured with answer-address command).

So if you are getting 8 digits ANI, above translation won't not work as it's matching 3 digits ANI. Moreover as I told before, you don't have inbound dial peer (answer-address) command configured for 2XX and 5XX, so we came back on the same point :) I strongly suggest you to check which inbound dial peer is being used for calls from 2XX and 5XX.

And my existing outbound call will running well ? in example my ANI 801 will go out as 28548801 and so on ? Or should be placed on my dial-peer pots ?

With CoR list in place, calls from 801 will hit inbound dial peer 992 and select dial peer 3 for outbound call. Under dial peer 3, you have applied translation profile 1 for outbound calls. Under translation profile 1, you are only translating called number, not calling number. So IMO, what you are trying to achieve won't work with existing configuration. Is it working?

- Vivek

MOHIT SINGH · ‎03-02-2016

Hi Yudistira,

As you are using CUCM so i don't think COR list is the correct way to segregate outbound dial peers based on the calling extension (if this is your only requirement).

You can configure inbound dial peers using "answer-address" and match it using calling party number. For ex; answer-address [1,2]... and answer-address [5,8]...

Add an incoming translation on these inbound dial peers and add prefix to called number for ex "1" for "answer-address [1,2]..." So called number becomes 19T. To send the call out using specific PRI create an outbound dial peer with destination pattern 19T. Now any outbound call with calling number 1XXX or 2XXX will be routed using dial peer with 19T pattern.

Similarly you can configure for 5XXX and 8XXX extension. Users can continue to use prefix "9" from any extension to dial out.

To use "answer-address" you have to make sure "incoming called-number " is not configured on any dial peer as it has higher priority than answer address.

Yudistira Aditya Pradana · ‎03-02-2016

Hi Mohit,

As you see on my attachment, i using DID for incoming and outgoing some numbers, so i think if I configure like what you said, it will erase the DID. is it wrong ? please correct me.

Thank you

MOHIT SINGH · ‎03-02-2016

Hi Vivek

For call routing, first outbound dial peer is selected based on destination pattern then the router checks if the outgoing COR list assigned to the OB dial peer is a subset of the inbound COR list. If it is a subset then call is allowed otherwise the call will fail using that dial peer.

In this case both the DP have same pattern (9.T) that's why for him DP is matched in round robin.

Vivek Batra · ‎03-02-2016

Hi Mohit,

Interesting. I would like to nail it down as I was always in the opinion that once inbound dial peer is selected, all dial peers are grouped together which are subset of inbound COR list and then then called number is matched with the destination-pattern among the subset dial peers.

If what you are saying is true where let say two dial peers are configured with same destination patterns and only one of the outbound dial peer is the subset of COR list assigned to inbound dial peer, first call attempt will route the call, then drop and then route and so on.

To validate the same, I configure the following;

dial-peer cor custom
name emergency
name local

dial-peer cor list 3001
member emergency

dial-peer cor list 3002
member local

dial-peer voice 901 voip
corlist outgoing 3001
destination-pattern 9.T
session protocol sipv2
session target ipv4:192.168.15.10

dial-peer voice 902 voip
corlist outgoing 3002
destination-pattern 9.T
session protocol sipv2
session target ipv4:192.168.15.14

ephone-dn 1
number 3001
corlist incoming 3001

Now if I dial 999 from DN 3001 which is assigned corlist incoming 3001, then always dial peer 901 is selected and call is always sent to 192.168.15.10.

If what you are saying is true and there is a second call attempt from DN 3001 to 999, dial peer 902 should be selected and since COR list assigned to dial peer 902 is not a subset of inbound COR list, call will fail, but that is not the case. Call doesn't fail and always selects dial peer 901.

What do you think?

- Vivek