Child pages
  • SIP eval


Contents

Only certain sip-headers can currently (8.7.3) be evaluated. Only the per-part-headers in a multipart-notify are accessible, i.e. the bold ones in the following example:

NOTIFY sip:424711@192.168.47.11:5080 SIP/2.0
From:<sip:presence@monitor>;tag=1590254348-1121378236593
To:<sip:424711@192.168.47.11>
Call-ID:BW1157070953040505019160572572925@192.168.40.30
CSeq:391772509 NOTIFY
Contact:<sip:424711@192.168.47.11:5060>
Require:eventlist
Event:dialog
Subscription-State:active;expires=4999
Max-Forwards:10
Content-
Type:multipart/related;boundary=UniqueBoundary;type=applicati
on/rlmi+xml
Content-Length:1666
--UniqueBoundary
Content-Type:application/rlmi+xml
Content-Length:429
Content-ID:<sczbLo@broadworks>
<?xml version="1.0" encoding="UTF-8"?>
<list xmlns="urn:ietf:params:xml:ns:rlmi" uri="sip:presence@monitor" version="0" fullState="true">
 <resource uri="sip:best_buddy@monitor">
  <name>best buddy</name>
  <instance id="FQJN17kNZT" state="active" cid="vZIKOJ@monitor"/>
 </resource>
</list>
--UniqueBoundary
Content-Type:application/dialog-info+xml
Content-Length:366
Content-ID:<vZIKOJ@monitor>
<?xml version="1.0" encoding="UTF-8"?>
<dialog-info xmlns="urn:ietf:params:xml:ns:dialog-info" version="0" state="full" entity="best_buddy@monitor">
 <dialog id="aHRFSG9R">
  <state>terminated</state>
  <local><identity display="best buddy"> sip:best_buddy@monitor</identity></local>
 </dialog>
</dialog-info>

An evaluation starts with the keyword "Header:" and continues with the header-name, followed by a compare-sign and an header-value to compare against. E.g.:

Header:Content-ID==<vZIKOJ@monitor>

checks if the Content-ID header is set to <vZIKOJ@monitor>

The header-content evaluation is optional, i.e. an expression consisting only of "Header:Content-ID" would check if there is a header named "Content-ID" regardless it's content.