[cisco-voip] Server-groups and failover...

[Anthony Holloway]

Kent,

You were probably just missing the profile required.  See here:

https://community.cisco.com/t5/telepresence-and-video/sip-options-ping-and-session-server-group-on-dial-peer/td-p/2994584


On Mon, Nov 18, 2019 at 11:00 PM Kent Roberts <kent at fredf.org> wrote:

> Oh I know what your trying to do, and I have had issues with it as well.
>
>  I have had better luck with with just using several dial-peers, and
> preference them, and use the voice-class sip options keepalive
>
> Then when you look at the dial-peer status you can see them out of
> service, and if you have SNMP enabled, you can see the status when
> integrated by things like Orion…..
>
>
> On Nov 18, 2019, at 9:56 PM, Jonathan Charles <jonvoip at gmail.com> wrote:
>
> 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-voip at 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 <jonvoip at 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 at puck.nether.net
>>> https://puck.nether.net/mailman/listinfo/cisco-voip
>>>
>> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20191119/8749e787/attachment.htm>