TB30s SIP Administrator Guide v1.3 Page 160 of 259
B) Content Retrieval
A successful profile enrollment leads to an initial SIP notification, and may
result in subsequent change notifications. Each of these notifications can
contain a profile data with the following restrictions:
The NOTIFY content is set according to the MIME type “application/service-
user-profile+xml”. All service variables are described in a XML document.
Inside the XML <service> node, each service variable is configured with a
dedicated <variable> node. The <variable> node provides service variable
name and current value.
For example:
NOTIFY sip:2205@10.0.0.55:5060;user=phone SIP/2.0
Via: SIP/2.0/UDP 10.0.0.5:5060;branch=z9hG4bK-b7d60ea12c0761993d006bb99033562e
from: <sip:2205@10.0.0.5:5060>;tag=e9c388b8d46
to: <sip:2205@10.0.0.5:5060>;tag=c0a80101-2834
Call-ID: 4fb8-c0a80101-d-2@10.0.0.55
CSeq: 2 NOTIFY
Contact: <sip:script@10.0.0.5:5060;transport=UDP>
Max-Forwards: 70
Subscription-state: active
Content-Length: 274
Event: ua-profile;profile-type=user
Content-type: application/service-user-profile+xml
<?xml version="1.0" encoding="UTF-8"?>
<service>
<variable name="cfu_on" value="1" />
<variable name="dnd" value="0" />
</service>
Following services are defined for TB30 at this point:
Indicates whether the CPE that initiated the supervision
is ready on the supervised Hunt Group. Applicable only
when a Hunting Group virtual line is supervised.
0 means not ready.
1 means ready.
When TB30 receives the SIP NOTIFY message, indicating successful profile
enrollment, it makes it effective immediately and displays service status to
the user.
The duration of the subscription is 3600 by default.