Re: [VoiceOps] SIP Trunk Failover
On 6/10/22 03:51, Brian Turnbow wrote: On 2022-06-09 14:42, Peter Beckman wrote: Maybe a better question: When providing SIP Trunk Failover as a feature, what do customer accounts use more often -- per TN or everything? Everything. It is rare for the customer to request different failover behaviors for different DIDs. At least that is my experience. Yes we mainly use secondary IP for trunk failover combined with forwarding to secondary tel number if that fails on a per trunk basis. Different DID forwarding is mainly for customers with hosted centrex/pbx type services, where each DID has its own config. When an IP is available from a different ISP on the CPE side, I set up 2 GRE tunnels with keep-alives enabled into our core. From there it is easy to set up static routes for failover. This makes everything transparent to the application layer. I use a short keep-alive interval to reduce the time it takes to failover. We use Juniper in our core and Adtran routers for the CPEs We can also do per TN forwarding/failover for customers without a second internet connection or who only want to forward one number. -- http://help.nyigc.net/ ___ VoiceOps mailing list VoiceOps@voiceops.org https://puck.nether.net/mailman/listinfo/voiceops
Re: [VoiceOps] SIP Trunk Failover
On 2022-06-09 14:42, Peter Beckman wrote: Maybe a better question: When providing SIP Trunk Failover as a feature, what do customer accounts use more often -- per TN or everything? Everything. It is rare for the customer to request different failover behaviors for different DIDs. At least that is my experience. ___ VoiceOps mailing list VoiceOps@voiceops.org https://puck.nether.net/mailman/listinfo/voiceops
Re: [VoiceOps] SIP Trunk Failover
Maybe a better question: When providing SIP Trunk Failover as a feature, what do customer accounts use more often -- per TN or everything? On Thu, 9 Jun 2022, Mike Johnston wrote: I agree with Jay, it is very customer specific. We offer all varieties of failover to meet their needs. Some have multiple sites with us and want the entire trunk to failover to a trunk at an alternate site. This requires the alternate site to be prepared to accept all of the DIDs of the first site, serve the appropriate IVRs, attempt to ring phones (possibly at the first site if they still have connectivity to it), etc. Or they might choose to simply redirect all such DIDs to the main number of the alternate site. Either way, the customer has a lot of control over happens without having to coordinate with me. Sometimes they want it to failover to a phone number, like a cellphone, an answering service, or like before, an alternate location. If the alternate location is not served by me, or maybe they just don't want to configure all of the DIDs of the first site into their alternate site's PBX, then it makes sense to failover to the main number of the alternate site. If the customer were to request different behaviors for different DIDs, then I would do that. For example, a school might want different failover behaviors for the Elementary Office DID, the High School Office DID, and all the other DIDs. That would make sense and I would certainly set that up for them. We have some where the failover is POTS lines in a small hunt group, that we preferably deliver as traditional copper loops. If the customer did not request a failover, then the default will be a busy signal. ___ VoiceOps mailing list VoiceOps@voiceops.org https://puck.nether.net/mailman/listinfo/voiceops --- Peter Beckman Internet Guy beck...@angryox.comhttps://www.angryox.com/ ---___ VoiceOps mailing list VoiceOps@voiceops.org https://puck.nether.net/mailman/listinfo/voiceops
Re: [VoiceOps] SIP Trunk Failover
I agree with Jay, it is very customer specific. We offer all varieties of failover to meet their needs. Some have multiple sites with us and want the entire trunk to failover to a trunk at an alternate site. This requires the alternate site to be prepared to accept all of the DIDs of the first site, serve the appropriate IVRs, attempt to ring phones (possibly at the first site if they still have connectivity to it), etc. Or they might choose to simply redirect all such DIDs to the main number of the alternate site. Either way, the customer has a lot of control over happens without having to coordinate with me. Sometimes they want it to failover to a phone number, like a cellphone, an answering service, or like before, an alternate location. If the alternate location is not served by me, or maybe they just don't want to configure all of the DIDs of the first site into their alternate site's PBX, then it makes sense to failover to the main number of the alternate site. If the customer were to request different behaviors for different DIDs, then I would do that. For example, a school might want different failover behaviors for the Elementary Office DID, the High School Office DID, and all the other DIDs. That would make sense and I would certainly set that up for them. We have some where the failover is POTS lines in a small hunt group, that we preferably deliver as traditional copper loops. If the customer did not request a failover, then the default will be a busy signal. ___ VoiceOps mailing list VoiceOps@voiceops.org https://puck.nether.net/mailman/listinfo/voiceops
Re: [VoiceOps] SIP Trunk Failover
On 6/8/22 19:13, Calvin Ellison wrote: If your SIP trunk provider were to offer failover, would you prefer to configure that failover per DID/TFN or for the entire SIP trunk? Failover might include another number, an IVR, voicemail, a ring group, another SIP trunk, a voice reject, or something else. We offer this and it's very customer specific. In some cases they'll want the entire trunk to reroute to the main number of a backup location, in some cases the whole trunk to an emergency IVR/voicemail, in some cases per-DID to individual cell phones, etc. -- Jay Hennigan - j...@west.net Network Engineering - CCIE #7880 503 897-8550 - WB6RDV ___ VoiceOps mailing list VoiceOps@voiceops.org https://puck.nether.net/mailman/listinfo/voiceops
