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!

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

Fallback SIP Trunk, Different Server, Same Company 3

Status
Not open for further replies.
dsm600rr

dsm600rr

IS-IT--Management
Joined
Nov 17, 2015
Messages
1,448
Location
US
Hello all,

I have a Two SIP Trunks Configured in my IPO, that the carrier (NexVortex) provided should one server go out of service

SIP Line 17
SIP Line 18

They are both configured exactly the same however point to two different "ITSP Domain Names" and "ITSP Proxy Address"

Being the Line Group ID's (Incoming/Outgoing Group) are the same (17), calls pick and choose which trunk they are going in/out on. I am assuming this is not ideal.

So, I would like SIP Trunk 17 to be the Main Trunk and Line 18 to be the fallback should line 17 go out of service. Is this possible?

Another thing I noticed in SSA under the Lines Status - "SIP Device Features", Line 17 has the field blank, Line 18 has "UPDATE (Incoming and Outgoing)" - Any idea what this means?

It seems on outbound that would be accomplished setting the main Line 17 ARS "Out of Service Route" to a new ARS Table for Line 18 and changing its Line Group ID to 18.

How could I accomplish this for Incoming Calls?

Perhaps I am completely wrong on all ideas. Suggestions? Basically both trunks are NexVortex, looking at 2 different servers.

I noticed the issue when I set up a conference call and 1/2 the callers were on line 17 and half were on line 18 on the same conference bridge.

Thank you.

ACSS
 
Sort by date Sort by votes
Keep line 18's INCOMING line group as 17, so Incoming Call Routes do not need to be duplicated

Change Line 18's OUTGOING line group to 18. Create a new ARS that uses Line Group 18. Use this new ARS as the Alternate Route for 17's ARS table.
 
Upvote 0 Downvote
UPDATE is a SIP feature and has nothing to do with fallback.

It is used to update the number during the call.

So if A calls B. B answers and transfers the call to C. Then it's possible that a SIP UPDATE message is sent to A containing the number of C.

IP Office remote service Fixed price SIP trunk configuration: CLI based cale blocking: SCN fallback over PSTN:
 
Upvote 0 Downvote
TouchToneTommy: Thank you. So it does not matter incoming calls are bouncing between the trucks? Seems to be random, sometimes the call is on 17 and other calls come in on 18.

ACSS
 
Upvote 0 Downvote
derfloh: Appreciate the info.

ACSS
 
Upvote 0 Downvote
If your incoming calls come in on both lines then the provider might use load balancing rather than failover for your SIP trunks.

But if you keep the incoming line ID the same (like TTT said) then you are good to go.

Just make sure that you do the ARS thing he mentioned otherwise outgoing will not work if the first trunk is down.

Joe
FHandw, ACSS (SME)

Remembering intrigrant 2019
 
Upvote 0 Downvote
TouchToneTommy: Just to clarify, On the main ARS, the Fail-over should be set as the "Alternate Route" and not the "Out of Service Route"?

If so, should I leave the "Alternate Route Priority Level" at the default "3" and the "Alternate Route Wait Time" at "30"

Also, in SSA on Line 18, the "Registration" tab will randomly disappear, and re-appear after a re-boot. Thoughts?

Thank you.

ACSS
 
Upvote 0 Downvote
For some reason when I Force Line 17 Out of Service and test an outbound call I get "Waiting for Line"

I get "Waiting for Line" with the Failover on the main ARS at both "Out of Service Route" or "Alternate Route"

If I leave both trunks as Incoming/Outgoing on 17 and force trunk 17 out of service it uses trunk 18 and works.

Is there any issues with leaving both Line 17 and Line 18 set both at Incoming/Outgoing Groups 17 and just let the calls come in/out as they choose rather than set one as a "Failover"?


ACSS
 
Upvote 0 Downvote
make sure that you set the wait time in the initial ARS to OFF otherwise it will wait until that timer expires and you get that annoying "Waiting for Line" message.

Joe
FHandw, ACSS (SME)

Remembering intrigrant 2019
 
Upvote 0 Downvote
Status
Not open for further replies.

Similar threads

rsv23
  • Locked
  • Question Question
SIP Trunk Routing
Replies
3
Views
661
rsv23
rsv23
L
  • Question Question
Mobile Twinning and SIP Trunk Usage
Replies
5
Views
334
Lectronics Inc
L
phoneDTC
  • Locked
  • Question Question
SIP Trunk Question
Replies
5
Views
880
phoneDTC
phoneDTC
pontim
  • Question Question
Sip Trunk Between Ip Office and OpenScape Business X8
Replies
4
Views
211
pontim
pontim
claudiotele
  • Locked
  • Question Question
Sip Trunk over TLS not working
Replies
7
Views
862
Mo. Abdullah
Mo. Abdullah

Part and Inventory Search

Sponsor

Back
Top