SIP Options probers
SIP Options probers allows to configure send SIP OPTIONS requests to remote gateways. This feature is usable to remote gateway monitoring.
Attributes
- Id
Unique id.
- Name
Name of this SIP Option prober configuration
- Enabled
Disabled probers will be ignored.
- Pop
Point of presence for SIP OPTIONS requests.
- Node
Node which will send SIP OPTIONS requests.
- Transport protocol
SIP transport protocol which will be used for send request.
- Sip Schema
URI scheme used in the OPTIONS request. Possible values:
sip,sips.- External ID
Optional identifier used to reference this SIP Options Prober from an external system.
- RURI Domain
R-URI domain of outgoing SIP OPTIONS request
- RURI Username
R-URI username of outgoing SIP OPTIONS request
- From URI
From URI of outgoing SIP OPTIONS request
- To URI
To URI of outgoing SIP OPTIONS request
- Auth username
Authorization username.
- Auth password
Authorization password.
- Route Set
A route set is a collection of ordered SIP or SIPS URI which represent a list of proxies that must be traversed when sending an OPTIONS request. Each entry must be enclosed in angle brackets, e.g.
<sip:sip-proxy.example.com;lr>. Route Set will be added to SIP request asRouteheaders. See RFC 3261, Section 12.2.1.1.Empty routeset:
OPTIONS sent via proxy:
Two proxies in routeset:
Loose routing (
lrparameter)Include the
lrparameter in each Route URI to enable loose routing (RFC 3261, Section 16.12). Withoutlr, strict routing (RFC 2543 behaviour) is used: the proxy replaces the Request-URI with its own address and appends the original Request-URI to the end of the Route list, which can cause interoperability issues with modern SIP stacks.- Contact uri
Contact header. Should be in a SIP-URI format.
- Interval
Requests sending interval in seconds
- Sip Interface Name
Name of signalling interface from sems.conf that will be used to build outgoing OPTIONS request.
- Append headers
Custom headers to append to outgoing request.