Copyright 2010-2017 Obihai Technology, Inc.
93
Note that the block of BLF keys reserved for a group does not necessarily come from a continuous range of feature keys
- the keys can be any combination of line keys, side car keys, and programmable keys.
SIP for BLF
For each BLF extension that does not belong to any group, the OBi1000 subscribes to the dialog event package for each
extension in the context of the SP service specified in the
Service
parameter of the corresponding feature key. For
extensions belonging to the same group, the OBi only maintains one subscription to the group-name and none for the
individual extensions in the group. In the subscribe request, the OBi indicates (in an Accept header) support for the
following content-types in NOTIFY message bodies to be returned by the server
-
application/multipart/related
-
application/rlmi+xml
-
application/dialog-info+xml
For floating key assignment, the OBi expects the NOTIFY message body to include a resource list (Content-Type:
application/rlmi+xml) that is compatible with RFC4662. Here is an example with two extensions specified in the
resource list:
<?xml version="1.0" encoding="UTF-8"?>
<list xmlns="urn:ietf:params:xml:ns:rlmi" uri="sip:[email protected]"
version="0" fullState="true">
<resource uri="sip:[email protected]">
<name>Obihai User2 </name>
<instance id="DNAbROacM9" state="active" cid="7jTC13@broadworks"/>
</resource>
<resource uri="sip:[email protected]">
<name>Test User</name>
<instance id="MT8FRckGPc" state="active" cid="cJ489p@broadworks"/>
</resource>
</list>
To notify the call states of a monitored extension, the OBi expects the NOTIFY message body to include a dialog-info
XML (Content-Type: dialog-info+xml) that is compatible with RFC4235. Here is an example:
<?xml version="1.0" encoding="UTF-8"?>
<dialog-info xmlns="urn:ietf:params:xml:ns:dialog-info" version="1"
state="full" entity="sip:[email protected]">
<dialog id="Y2FsbGhhbGYtNjI4MjM4NzU6MA==" direction="recipient">
<state>proceeding</state>
<local>
<identity display="ObihaiUser2 ObihaiUser2">
sip:[email protected]
</identity>
<identity display="ObihaiUser2 ObihaiUser2">
tel:+12404982562;ext=2562
</identity>
</local>
<remote>
<identity display="ObihaiUser1 ObihaiUser1">
sip:[email protected];user=phone
</identity>
</remote>
</dialog></dialog-info>
When the soft-switch is capable of notifying call park status for the monitored extension, it is expected the status is
reported inside a dialog-info XML as well. Here is an example:
<?xml version="1.0" encoding="UTF-8"?>
<dialog-info xmlns="urn:ietf:params:xml:ns:dialog-info"
xmlns:sa="urn:ietf:params:xml:ns:sa-dialog-info"
xmlns:bw="http://schema.broadsoft.com/callpark"
version="3" state="partial"
entity="sip:[email protected]">
<dialog id="Y2FsbGhhbGYtMzM6MA==">
<state>confirmed</state>
<bw:callpark>
<bw:parked>
<identity display="Alice south">
sip:[email protected];user=phone