The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
When a WAN link goes down temporarily or the registrar server is down, local calls cannot be made and no calls can be routed to and from the phones. The Survivability Enhancements feature on the Nano CUBE is used to:
Your software release may not support all the features documented in this module. For the latest caveats and feature information, see Bug Search Tool and the release notes for your platform and software release. To find information about the features documented in this module, and to see a list of the releases in which each feature is supported, see the feature information table.
Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to www.cisco.com/go/cfn. An account on Cisco.com is not required.
The survivability feature addresses the following issues:
When a WAN link or registrar server comes up, it needs to wait till each SIP phone sends the REGISTER message to the server, so that outside phones can reach that phone.
If the phone register timer setting is too large, the outside phone needs to wait that much time to reach that phone, after a link flap.
If the phone register timer setting is too small, it will flood the WAN link.
When the WAN link or registrar server is down, local calls cannot be made.
There are two ways to address these issues:
NanoCUBE does not need to configure credentials, as the phones will trigger registration. Although nanoCUBE receives REGISTER messages for each phone every 5 minutes; for example, it will throttle and send REGISTER messages every 1 hour to the registrar server, avoiding high WAN bandwidth usage. This will address the issues 1, 2, and 3.
In normal operation when the WAN link or registrar server is up, the phone’s primary server URL is the registrar server (E2E) registration.
The OPTIONS ping is used to monitor the registrar server link status. When the detected link is down, NanoCUBE will reply with a 500 message and when the phone receives this message, it will send the REGISTER message to NanoCUBE, which is the secondary server (P2P registration). NanoCUBE will reply with a 200 OK message to P2P registration when the link is down. The dial-peer will keep dynamic registrar session target and the local call will not fail. This will address issue 4.
If you configure the phones to send REGISTER messages every 1 hour (to help alleviate the WAN link), the NanoCUBE uses the credentials configured to respond to registrar server authentication challenge. This addresses issue 3.
When the WAN link or registration server is down (detected by OPTIONS ping), the NanoCUBE keeps the registration database of the SIP phones previously registered successfully, and it does not send REGISTER messages out; NanoCUBE replies with a 200 OK message and dial-peer will keep the dynamic registrar session target. The local call will not fail, addressing issue 4.
When the registrar link is up after link flap, the NanoCUBE sends REGISTER message for each phone that was earlier successfully registered to the registrar server. This is throttled to avoid bulk REGISTER messages flooding WAN link as well as the registrar. This addresses issues 1 and 2.
1.
enable
2.
configure terminal
3.
voice service voip
4.
sip
5.
registration passthrough local-fallback tag
6.
end
1.
enable
2.
configure terminal
3.
dial-peer voice tag voip
4.
voice-class sip registration passthrough local-fallback tag
5.
end
1.
enable
2.
configure terminal
3.
dial-peer voice tag voip
4.
voice-class sip options-keepalive up-interval value down-interval value
5.
end
1.
enable
2.
configure terminal
3.
voice service voip
4.
sip
5.
registrar server expires max value min value
6.
end
1.
enable
2.
configure terminal
3.
voice service voip
4.
sip
5.
registration passthrough rate-limit expires value local-fallback tag
6.
end
1.
enable
2.
configure terminal
3.
dial-peer voice tag voip
4.
corlist incoming dial-peer
5.
corlist outgoing dial-peer
6.
description string
7.
destination-pattern number
8.
session protocol sipv2
9.
session target registrar
10.
voice-class sip registration passthrough local-fallback tag
11.
end
Perform this task to verify the configurations for the survivability enhancements. The show commands can be entered in any order.
1.
enable
2.
show dial-peer voice summary
3.
show sip-ua registration passthrough status
4.
show sip-ua register status
5.
show voip rtp connections
6.
show call active voice compact
Device> enable Device# configure terminal Device(config)# voice service voip Device(conf-voi-serv)# sip Device(conf-serv-sip)# registration passthrough local-fallback 10 Device(config-serv-sip)# end
Device> enable Device# configure terminal Device(config)# dial-peer voice 2 voip Device(config-dial-peer)# voice-class sip registration passthrough local-fallback 10 Device(config-dial-peer)# end
Device> enable Device# configure terminal Device(config)# dial-peer voice 3 voip Device(config-dial-peer)# voice-class sip options-keepalive up-interval 120 down-interval 120 Device(config-dial-peer)# end
Device> enable Device# configure terminal Device(config)# voice service voip Device(conf-voi-serv)# sip Device(conf-serv-sip)# registrar server expires max 300 min 200 Device(conf-serv-sip)# end
Device> enable Device# configure terminal Device(config)# voice service voip Device(conf-voi-serv)# sip Device(conf-serv-sip)# registration passthrough rate-limit expires 3600 local-fallback 3 Device(conf-serv-sip)# end
Device> enable Device# configure terminal Device(config)# dial-peer voice 2 voip Device(config-dial-peer)# corlist incoming FromPhone Device(config-dial-peer)# corlist outgoing FromSP Device(config-dial-peer)# description registration Device(config-dial-peer)# destination-pattern 1111 Device(config-dial-peer)# session protocol sipv2 Device(config-dial-peer)# session target registrar Device(config-dial-peer)# voice-class sip registration passthrough local-fallback 5 Device(config-dial-peer)# end
The following table provides release information about the feature or features described in this module. This table lists only the software release that introduced support for a given feature in a given software release train. Unless noted otherwise, subsequent releases of that software release train also support that feature.
Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to www.cisco.com/go/cfn. An account on Cisco.com is not required.
Feature Name |
Releases |
Feature Information |
---|---|---|
Survivability Enhancements |
15.3(3)M |
When a WAN link goes down temporarily or the registrar server is down, local calls cannot be made and no calls can be routed to and from the phones. The Survivability Enhancements feature on the NanoCUBE is used to: |