Avaya Support Forums  

Go Back   Avaya Support Forums > IP Telephony and Convergence

Reply
 
Thread Tools Search this Thread Display Modes
  #1  
Old 01-15-2015, 11:15 AM
estigh estigh is offline
Member
 
Join Date: Jan 2015
Posts: 3
estigh has 10 reputation points
Default Incoming routes for multiple SIP Lines

I have an IPO 8.1 V2. I have configured 3 separate SIP lines and they register and work well for outgoing and incoming calls. I created 3 different incoming routes one for each line,
SIP Line 19->VM:Menu1
SIP Line 20->Extn123
SIP Line 21->Extn100

I assigned each incoming route to its corresponding SIP line but when I call each one they all show as incoming only from line 19 and so the calls only get routed to Menu1.

Thanks
Reply With Quote
  #2  
Old 01-15-2015, 11:45 AM
zakabog zakabog is offline
Genius
 
Join Date: Aug 2014
Posts: 300
zakabog has 25 to 49 reputation pointszakabog has 25 to 49 reputation pointszakabog has 25 to 49 reputation points
Default

You have 3 SIP trunks built to 3 separate carriers or you have one SIP trunk with 3 DIDs? How do you have your SIP URIs configured?
Reply With Quote
  #3  
Old 01-15-2015, 12:18 PM
estigh estigh is offline
Member
 
Join Date: Jan 2015
Posts: 3
estigh has 10 reputation points
Default

I have 3 SIP trunks to the same carrier but each with its own DID.
SIP URI is set to * for each line, I have also tried using the DID with the same result.
As a side note, if I set the DID (instead of blank) on incoming route for line 19 calls to the other lines fail but work for line 19.
Reply With Quote
  #4  
Old 01-15-2015, 12:36 PM
zakabog zakabog is offline
Genius
 
Join Date: Aug 2014
Posts: 300
zakabog has 25 to 49 reputation pointszakabog has 25 to 49 reputation pointszakabog has 25 to 49 reputation points
Default

SIP doesn't work like POTS lines where you have one line per number. In your case, you have one SIP trunk, 3 concurrent channels, and 3 DIDs. You can have any number of DIDs and any number of channels over that one trunk. If your incoming URI for all 3 lines is * then the calls will all be presented to the first one, since * will match every number that is presented to the PBX and since you don't have a more explicitly defined URI it'll always use that. If you want each number to be it's own separate incoming and outgoing group ID then setup one URI per DID and use the individual DIDs, not *. Or what I normally do, leave * and define the incoming call routes for trunk group 19 with the individual DIDs and delete the other URIs.
Reply With Quote
  #5  
Old 01-16-2015, 09:10 AM
estigh estigh is offline
Member
 
Join Date: Jan 2015
Posts: 3
estigh has 10 reputation points
Default

Thanks zakabog for your help, I resolved the issue by creating 3 SIP trunks to the provider and left the URI as *, as you mentioned it was matching the first line (19) and ignoring the other incoming routes, so I added 3 different incoming routes for line 19 and specified the DID in each route, that solved the issue, thanks again.
Reply With Quote
Reply

Tags
incoming call, sip trunks

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT -7. The time now is 10:51 PM.

This Forum is provided solely for the use and convenience of Avaya customers and partners. Use of the Forum is subject to the Terms and Use and Privacy Statement found at www.avaya.com. No other use is permitted. The Forum including all content posted is “AS IS” and Avaya expressly disclaims all warranties and/or guarantees as to its accuracy, reliability, usefulness, quality or non-infringement of intellectual property. Avaya reserves the right to remove any content posted on the Forum at any time and for whatever reason.

Avaya will not be liable for any content posted on this Forum, including, without limitation, any errors or omissions or for any losses or damages of any kind incurred as a result of use or reliance on any content, regardless of its origin.

You expressly understand and agree that you assume all risks associated with use or reliance on this content.