×
INTELLIGENT WORK FORUMS
FOR COMPUTER PROFESSIONALS

Log In

Come Join Us!

Are you a
Computer / IT professional?
Join Tek-Tips Forums!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!
  • Students Click Here

*Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

Posting Guidelines

Promoting, selling, recruiting, coursework and thesis posting is forbidden.

Students Click Here

Jobs

Fallback SIP Trunk, Different Server, Same Company
3

Fallback SIP Trunk, Different Server, Same Company

Fallback SIP Trunk, Different Server, Same Company

(OP)
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

RE: Fallback SIP Trunk, Different Server, Same Company

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.

RE: Fallback SIP Trunk, Different Server, Same Company

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 https://www.fwilke.com/home
Fixed price SIP trunk configuration: https://www.fwilke.com/en/ip-office-sip-trunk-en/
CLI based cale blocking: https://blog.fwilke.com/ip-office-block-calls-from...
SCN fallback over PSTN: https://blog.fwilke.com/ip-office-scn-fallback/

RE: Fallback SIP Trunk, Different Server, Same Company

(OP)
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

RE: Fallback SIP Trunk, Different Server, Same Company

(OP)
derfloh: Appreciate the info.

ACSS

RE: Fallback SIP Trunk, Different Server, Same Company

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

RE: Fallback SIP Trunk, Different Server, Same Company

(OP)
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

RE: Fallback SIP Trunk, Different Server, Same Company

(OP)
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

RE: Fallback SIP Trunk, Different Server, Same Company

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

Red Flag This Post

Please let us know here why this post is inappropriate. Reasons such as off-topic, duplicates, flames, illegal, vulgar, or students posting their homework.

Red Flag Submitted

Thank you for helping keep Tek-Tips Forums free from inappropriate posts.
The Tek-Tips staff will check this out and take appropriate action.

Reply To This Thread

Posting in the Tek-Tips forums is a member-only feature.

Click Here to join Tek-Tips and talk with other members! Already a Member? Login

Close Box

Join Tek-Tips® Today!

Join your peers on the Internet's largest technical computer professional community.
It's easy to join and it's free.

Here's Why Members Love Tek-Tips Forums:

Register now while it's still free!

Already a member? Close this window and log in.

Join Us             Close