In this router we actually tried something different (and gave up on this implementation thus I think the dial-peer groups maybe not being effective here for redundancy, and we’d just not fixed it, it’s been a couple of years – it may have been the options ping either not working or marking the whole peer out of service despite other available targets).
I also like to complicate things as you can see below: dial-peer voice 200 voip description PSTN ITSP SIP Trunk translation-profile outgoing ITSP-PSTN-Out session protocol sipv2 session transport udp session server-group 200 destination dpg 400 destination e164-pattern-map 2200 incoming called e164-pattern-map 200 voice-class codec 200 voice-class sip profiles 200 voice-class sip options-keepalive dtmf-relay rtp-nte sip-kpml no vad dial-peer voice 400 voip description Production UCM Dial Peer translation-profile outgoing Windstream-PSTN-In session protocol sipv2 session target dns:prodall.cmgroup.srv.domain session transport tcp destination dpg 200 destination e164-pattern-map 400 voice-class codec 400 voice-class sip options-keepalive dtmf-relay rtp-nte sip-kpml no vad dial-peer voice 500 voip description Non-Working Number 404 Code Fallthrough service non_working_number out-bound destination-pattern +.*T session target loopback:rtp voice class dpg 400 description Production UCM Dial Peer Group dial-peer 400 dial-peer 500 preference 1 ! voice class dpg 200 description ITSP SIP Dial Peer Group dial-peer 200 ! voice class server-group 200 ipv4 10.250.0.5 ipv4 10.250.0.6 preference 1 description ITSP Server Group ! From: Johnson, Tim <johns...@cmich.edu> Sent: Tuesday, November 19, 2019 8:23 AM To: Pawlowski, Adam <aj...@buffalo.edu>; 'Jonathan Charles' <jonv...@gmail.com>; Anthony Holloway <avholloway+cisco-v...@gmail.com> Cc: cisco-voip@puck.nether.net Subject: RE: [cisco-voip] Server-groups and failover... What’s your dial peer configuration look like? Curious if you have ‘huntstop’ configured. From: cisco-voip <cisco-voip-boun...@puck.nether.net<mailto:cisco-voip-boun...@puck.nether.net>> On Behalf Of Pawlowski, Adam Sent: Tuesday, November 19, 2019 8:07 AM To: 'Jonathan Charles' <jonv...@gmail.com<mailto:jonv...@gmail.com>>; Anthony Holloway <avholloway+cisco-v...@gmail.com<mailto:avholloway+cisco-v...@gmail.com>> Cc: cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net> Subject: Re: [cisco-voip] Server-groups and failover... I think I had to make some adjustments to our timers as well to get this to work before network timeout or similar: sip-ua retry invite 2 timers trying 100 ! I know I also goofed this up between dial peer group and server group, one of the two will retry within the group, the other sure doesn’t. From: cisco-voip <cisco-voip-boun...@puck.nether.net<mailto:cisco-voip-boun...@puck.nether.net>> On Behalf Of Jonathan Charles Sent: Monday, November 18, 2019 11:56 PM To: Anthony Holloway <avholloway+cisco-v...@gmail.com<mailto:avholloway+cisco-v...@gmail.com>> Cc: cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net> Subject: Re: [cisco-voip] Server-groups and failover... I pasted the wrong part of the script (to manually change it)... Here is the actual config: voice class server-group 1 ipv4 172.31.120.43 ipv4 172.31.125.43 preference 2 description Verizon SIP ! Jonathan On Mon, Nov 18, 2019 at 10:22 PM Anthony Holloway <avholloway+cisco-v...@gmail.com<mailto:avholloway%2bcisco-v...@gmail.com>> wrote: First off, I'm wondering why it says "no ipv4" in front of your two addresses. That might be your problem right there. Secondly, I'd recommend putting an explicit preference on your entries, it's just better for everyone, and you don't get a credit back from Cisco for saving on a few ascii characters by implicitly using the default. Plus, if the default is 0, which it is, then your next preference should be technically 1. But then having nothing and 1 seems silly, because if pref 1 is actually pref 2, then well, might as well call them pref nothing and pref 8. I digress. You might not have failed over, because you might not have provided the system with the correction conditions to failover...E.g., you didn't wait long enough. No seriously, by default SIP failover occurs after 30 seconds. Unless, did you lower the retry count under sip-ua? Or did you enable SIP options? If you enabled SIP options, have your confirmed that it's turned on correctly? Can you share the output of the following commands: show run | section sip-ua|sip.options-keepalive show dial-peer voice summary Feel free to redact what you need to, in terms of IPs or usernames/passwords. I am only looking for the features and settings for retries and keepalives. On Mon, Nov 18, 2019 at 9:26 PM Jonathan Charles <jonv...@gmail.com<mailto:jonv...@gmail.com>> wrote: Using session server groups on outbound dial-peers and it does not appear to be failing over: voice class server-group 1 no ipv4 172.31.125.43 preference 2 no ipv4 172.31.120.43 description Verizon SIP ! We had the 172.31.20.43 go down (no response to invites) and we did NOT failover to the second (.125.43)... What is needed to force a failover to the next configured SBC? Jonathan _______________________________________________ cisco-voip mailing list cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net> https://puck.nether.net/mailman/listinfo/cisco-voip
_______________________________________________ cisco-voip mailing list cisco-voip@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-voip
