Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

SBCE with two IP Office, how to route incoming calls

Status
Not open for further replies.

Loremtz

Technical User
Jun 11, 2013
96
MX
Hi experts!
I need your help, I created an integration between an Avaya SBCE with two IP Offices. I created the dial plan for the IPOs and the outgoing calls are working through a SIP trunk, but I don't find how to route the incoming calls, example: when the outside user call to 552000 DN's to site A, the call is successful, but if that same user try to reach to DN 554000 in the site B the call is routed through the first IPO.
I know that is just an adjust in a dial plan but I can't found how to do it

Thanks in advance
 
You need to create 2 routing profiles and one URI Group for each to decide which DDIs to route where.


"Trying is the first step to failure..." - Homer
 
I like to separate the session flows clearly by setting up two IPs on the LAN side (A1) and two on the WAN side (B1).

IP Office remote service Fixed price SIP trunk configuration: CLI based cale blocking: SCN fallback over PSTN:
 
Thanks @janni78, this URI group needs to be applied in the Flow between IPO-A1 or B1-PublicService?
 
Please, If someone has an example creating DID's for Incoming calls in SBC where a SIP Trunk exist and there is necesary to route to two or more IPOs
 
If I remember correctly you set the URI Group on the trunk side, but it's somewhat described in the help how it handles this.

"Trying is the first step to failure..." - Homer
 
I'm basing this deployment in reference docs from Avaya, SBC with multitenance, there say that I need to take two vlan and configure it in the A1 interface. In your experience, is this the best way to do it? Is posible just to use the same interface A1 without vlans?
 
I did it once with a trunk and a remote worker flow. I had some problems to divide the two flows with different URI groups. After using two internal and two external IPs (without additional VLAN) everything started to work smooth.

IP Office remote service Fixed price SIP trunk configuration: CLI based cale blocking: SCN fallback over PSTN:
 
As I understand it you wanna share one SIP trunk with 2 IP Offices.

I didn't setup different VLANs, I just used different TCP ports on the SBC for each IP Office on the internal interface.

"Trying is the first step to failure..." - Homer
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top