10-29-2015 11:18 PM - edited 03-12-2019 10:20 AM
This document covers the overview of SIP OPTIONS Ping feature overview and the steps for enabling the features.
The SIP OPTIONS Ping feature can be enabled on the SIP Profile associated with a SIP trunk to dynamically track the state of the trunk's destination(s). When this feature is enabled, each node running the trunk's SIP daemon will periodically send an OPTIONS Request to each of the trunk's destination IP addresses to determine its reachability and will send calls only to reachable nodes.
A destination address is considered to be "out of service" if it fails to respond to an OPTIONS Request, if it sends a Service Unavailable (503) response or Request Timeout (408) response, or if a TCP connection cannot be established.
The overall trunk state is considered to be "in service" when at least one node receives a response (other than a 408 or 503) from a least one destination address. SIP trunk nodes can send OPTIONS Requests to the trunk's configured destination IP addresses or to the resolved IP addresses of the trunk's DNS SRV entry.
Here are the steps to enable OPTIONS Ping feature.
Go to Device -> Device Settings -> SIP Profile and create a SIP Profile with SIP OPTIONS Ping Enabled Checked and enter appropriate values for the corresponding parameters.
[+5] for sharing info.
regds,
aman
Thank you Aman.
Regards
Lavanya
If i disable sip option ping on sip trunk I could not receive calls from outside sometimes. ?
What could be problem. When sip option enabled it its working fine.
I have only one CUCM node (version: 8.6.2.20000-2)
You should probably check the traces on the other side from where you are getting calls and figure out what is going wrong....
- Vivek
Please verify the contents of the initial post. When looking at the CUBE Configuration Guides https://www.cisco.com/c/en/us/td/docs/ios-xml/ios/voice/cube_sip/configuration/15-mt/cube-sip-15-mt-book/voi-out-of-dialog.html
it says:
=====
The table below describes error codes option ping responses considered unsuccessful and the dial-peer is busied out for following scenarios:
Error Code |
Description |
---|---|
503 |
service unavailable |
505 |
sip version not supported |
no response |
i.e. request timeout |
All other error codes, including 400 are considered a valid response and the dial peer is not busied out.
=====
Does the CUBE handle SIP Options ping differently then the CUCM? Because the initial post and the configuration guide don't allign
ok once we enable the option ping option where in cucm it shows the status of sip turnk ?
would appreciate if someone points it out
@Wonxie It shows on the SIP trunk page.
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: