cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
891
Views
0
Helpful
4
Replies

Force call out a specific dial-peer

sean6605
Level 1
Level 1

Good Afternoon,

I hope I can get some help in the right direction for this.

I have a voice gateway that has two PBXs connected to it

PBX-A is SIP so a voip dial peer

PBX-B is TDM so I'm using a POTS dial peer with the ISDN connection

The extensions all in both PBXs start with 58xx, but none of them overlap.

Extension-A is 5831 in PBX-A

Extension-B is 5832 in PBX-B

When extension-A calls Extension-B sometimes I get routed back to myself in PBX-A and I get a busy because there is not extension 5832 in PBX-B

I wanted to know if there is such a way to setup the voice gateway so that it knows that any 58XX call coming in from VOIP gets forced down the ISDN trunk and any 58 call coming in on the ISDN trunk gets forced down the VOIP connection

my dial peers are

dial-peer voice 5800 voip
 description LOCAL EXTENSION DIALLING TO VOIP
 destination-pattern 58..
 session protocol sipv2
 session target ipv4:10.10.10.10:5060
 codec g711ulaw

dial-peer voice 95800 pots
 description LOCAL EXTENSION DIALLING TO ISDN TRUNK
 destination-pattern 58..
 port 0/0/3:23
 prefix 58

can this be done.

Can the gateway know that it received the call on VOIP so it should got out ISDN and vice versa?

Thank you in advance for any help

 

 

1 Accepted Solution

Accepted Solutions

Dennis Mink
VIP Alumni
VIP Alumni

one option would be to to add an additional dial peer, that gets matched when a call from PBX-B hits the gateway inbound:

 

 

dial-peer voice 1111 voip

    answer-address 58..

    translation-profile incoming add123

 

this dial peer basically matches based on calling number, so it will only get hit when coming from PBX-B, the translation will then add 123 to the called number, this means that dialpeer 95800 gets hit.

 

 

dial-peer voice 95800 pots
 description LOCAL EXTENSION DIALLING TO ISDN TRUNK
 destination-pattern 12358..
 port 0/0/3:23
 prefix 58

 

 

 

the following translation will add 123 to any called number (just as an example):

voice translation-rule 1
 rule 1 /\(.*\)/ /123\1/

 

voice translation-profile add123
 translate called 1

 

I am sure there are more ways to achieve this, and more elegant, but give this a shot.

 

Hope this helps

Please remember to rate useful posts, by clicking on the stars below.

View solution in original post

4 Replies 4

Dennis Mink
VIP Alumni
VIP Alumni

one option would be to to add an additional dial peer, that gets matched when a call from PBX-B hits the gateway inbound:

 

 

dial-peer voice 1111 voip

    answer-address 58..

    translation-profile incoming add123

 

this dial peer basically matches based on calling number, so it will only get hit when coming from PBX-B, the translation will then add 123 to the called number, this means that dialpeer 95800 gets hit.

 

 

dial-peer voice 95800 pots
 description LOCAL EXTENSION DIALLING TO ISDN TRUNK
 destination-pattern 12358..
 port 0/0/3:23
 prefix 58

 

 

 

the following translation will add 123 to any called number (just as an example):

voice translation-rule 1
 rule 1 /\(.*\)/ /123\1/

 

voice translation-profile add123
 translate called 1

 

I am sure there are more ways to achieve this, and more elegant, but give this a shot.

 

Hope this helps

Please remember to rate useful posts, by clicking on the stars below.

Dennis,

Thank you so much, I will try this first thing in the morning my time (EST).

I was thinking about that but I could not figure out how to get the 123 in front of the digits, as there is no prefix command on the VoIP dial-peer. but with the translation-profile that resolves that issue.

As soon as I can get access in the morning I'll let you know what happens.

Many Thanks

Dennis,

Again Thank you for your suggestion.

That worked like a charm

 

good man, HTH

Please remember to rate useful posts, by clicking on the stars below.