outbound call routing

[Yudistira Aditya Pradana]

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 ?

[MOHIT SINGH]

Hi Yudistra,

Both dial peers have same pattern "9.T" so one of them will be matched randomly despite of COR list configuration. What I will suggest is you configure an inbound translation on ephone DNs to add a prefix to called number based on extension and configure outbound dial peer pattern to match the prefix. This way you can segregate selection of outbound dial peer

[Vivek Batra]

Hi Mohit,

Both dial peers have same pattern "9.T" so one of them will be matched randomly despite of COR list configuration.

IMO, it is not a correct behavior. COR list configuration will prevent matching outbound dial peer based on corlist assigned to inbound dial peer, hence having same destination pattern should not be an issue here. With corlist configuration in place, only those outbound dial peers are checked which is allowed as per corlist configuration and then destination-pattern is matched.

Hi Yudistira,

Can you please share show run.

- Vivek

[Yudistira Aditya Pradana]

Hi Mohit and Vivek

Thank you for your reply, yes i set 9.T as destination pattern because i want to keep users consistency call outbound, if i making different pattern it will confused users and also my management will rejected the options.

I attached the show run by the way.

Thank you.

[Vivek Batra]

Hi,

I can not see any ephone or SIP phone configuration, your call control is CME or CUCM?

- Vivek

[Yudistira Aditya Pradana]

Hi Vivek,

I use CUCM as my call control, and connecting by H.323 Gateway.

Thank you.

[Vivek Batra]

Hi Yudistira,

Let us try to fix it for one extension range. As you mentioned before, you would like the extensions 5XX to use dial-peer voice 3 pots for outbound call.

Since you have applied corlist incoming Allow8XX to dial-peer voice 992, it should select the outbound dial peer 3 pots as the same corlist is applied to dial peer 3 in outbound direction. For calls made from 5XX, if respective outbound dial peer is not being used, call may be hitting incorrect dial peer.

Please make a test call from 5XX and get the output of debug voice ccapi inout and share the same.

Also note that there are many other dial peers (seems analog ports) which can also handle the calls made to 9.T pattern and since no corlist is assigned to those dial peers, any inbound call from CUCM can use those outbound dial peers irrespective of the corlist assigned to inbound dial peers.

- Vivek

[Yudistira Aditya Pradana]

Hi Vivek,

I'm Already debug voice ccapi inout, but no result on my router, it's weird for me. As you see i have 3 pots for outboound calls, 1, 2, and 3. which pots number 2 is for 3xx number. but like i mentioned early the outbound calls from 2xx and 5xx just round robin at pots 1 and 3. never through pots 2. Any suggestions ?

Thank you.

[Vivek Batra]

but like i mentioned early the outbound calls from 2xx and 5xx just round robin at pots 1 and 3. never through pots 2. Any suggestions ?

You have answer-address command in three DP's viz 990, 991 and 992. These three dial peers seem to match ANI of 1xx, 3xx and 8xx respectively as per answer-address command configured. Hence I don't know which inbound dial peer is being used for calls with ANI of 2xx and 5xx.

I suggest your should review your configuration and explicitly document the following for us to assist you further;

1. Calls from 1XX

Inbound dial peer - ?

Outbound dial peer - ?

2. Calls from 2XX

Inbound dial peer - ?

Outbound dial peer - ?

3. Calls from 3XX

Inbound dial peer - ?

Outbound dial peer - ?

4. Calls from 5XX

Inbound dial peer - ?

Outbound dial peer - ?

5. Calls from 8XX

Inbound dial peer - ?

Outbound dial peer - ?

- Vivek

[Yudistira Aditya Pradana]

Hi Vivek,

Maybe this will help :

1. Calls from 1XX

Inbound dial peer 990 voip

Outbound dial peer 1 pots

2. Calls from 2XX

Inbound dial peer 990 voip

Outbound dial peer 1 pots

3. Calls from 3XX

Inbound dial peer 991 voip

Outbound dial peer 2 pots

4. Calls from 5XX

Inbound dial peer 992 voip

Outbound dial peer 3 pots

5. Calls from 8XX

Inbound dial peer 992 voip

Outbound dial peer 3 pots

In my opinion since 2xx as member Allow1xx and 5xx member Allow8xx it will create also as answer-address dial-peer 990 and 993. is it right ?

when someone calling 28548844 it will be directed into extension 844 and so on. But 2xx and 5xx no have DID numbers, I just want to create outbound calls for those extension.

FYI, FXO line is for my backup line.

Thank you.

[Vivek Batra]

Hi,

Your configuration for calls from 1XX, 3XX and 8XX looks good because of answer-address configuration, however it doesn't work we will have to see debug voice ccapi inout logs to verify whether calls are hitting desired dial peer or not.

In my opinion since 2xx as member Allow1xx and 5xx member Allow8xx it will create also as answer-address dial-peer 990 and 993. is it right ?

I didn't exactly get your point but you should note that you need to explicitly define 'answer-address' command to match the calls from 2XX and 5XX since inbound dial peer is matched before checking CoR configuration.

You can have following two additional dial peers to take care of 2XX and 5XX calls;

dial-peer voice 993 voip
 corlist incoming Allow1xx
 answer-address 285482..
 voice-class codec 1
 dtmf-relay h245-alphanumeric
 ip qos dscp cs5 media
 ip qos dscp cs4 signaling
 no vad
!
dial-peer voice 994 voip
 corlist incoming Allow8xx
 answer-address 285485..
 voice-class codec 1
 dtmf-relay h245-alphanumeric
 ip qos dscp cs5 media
 ip qos dscp cs4 signaling
 no vad

FYI, FXO line is for my backup line.

Please note that if you don't apply CoR list to FXO dial peers, it will be selected by any inbound dial peer. You need to carefully apply CoR list to FXO dial peer as well and add 'preference' command so that these dial peers are used as backup only.

- Vivek

[Yudistira Aditya Pradana]

Hi VIvek,

You can have following two additional dial peers to take care of 2XX and 5XX calls;

Is it related with outbound call for 2xx and 5xx, because 258548xxx is my ISDN from telco there is only 2585481xx , 2585483xx and 2585488xx so i can't create 2585482xx and 2585485xx.

I'm sorry if my questions making you confused. Because this is my first time configure voice gateway.

Please note that if you don't apply CoR list to FXO dial peers, it will be selected by any inbound dial peer. You need to carefully apply CoR list to FXO dial peer as well and add 'preference' command so that these dial peers are used as backup only.

I'll do.

Thank you.

[Vivek Batra]

Hi,

Ya, seems some sort of confusion but I will try to nail it down as much as possible for me :)

So we are talking about outbound calls only from CUCM to gateway, correct?

Now if you have extensions only in the range of 1XX, 3XX and 8XX, then your configuration looks good as per following;

1. Calls from 1XX

Inbound dial peer 990 voip

Outbound dial peer 1 pots

2. Calls from 3XX

Inbound dial peer 991 voip

Outbound dial peer 2 pots

3. Calls from 8XX

Inbound dial peer 992 voip

Outbound dial peer 3 pots

Inbound dial peers with 'answer-address' and corlist is already configured and outbound dial peers are also configured with respective corlist. If intended outbound dial peer is not being selected, please share the output of debug voice ccapi inout so that we can check where the issue is.

- Vivek

[Yudistira Aditya Pradana]

Hi Vivek,

Could I configure like this :

voice translation-rule 5
Rule 1 /\(2..\/ /28548100\1/

voice translation-rule 6
Rule 1 /\(5..\/ /28548800\1/

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
!

Without disrupted existing inbound and outbound calls for 1xx, 3xx, and 8xx ?

Thank you for guiding me so far.

[Vivek Batra]

Hi,

When you apply translations to voice port, this has nothing to do with CoR since voice-port is selected at the end of call routing logic, so I really don't know what you are trying to achieve here.

But I can tell you from configuration that when port 0/1/0:15 will be selected for outbound call, it will translate the ANI with 2XX to 285481002XX. Similarly for port 0/2/0:15, ANI with 5XX will be translated to 285488005XX. That is what you want to achieve?

- Vivek