AudioCodes Mediant 500 MSBR, Руководство пользователя

Страница: 284 / 1248

User's Manual 284 Document #: LTRT-10375
Mediant 500 MSBR
on the user's Skype for Business endpoint. Presence information of Skype for Business
endpoints (such as Skype for Business desktop client) is handled solely by the Skype for
Business Server, without any intervention of the device. However, when third-party (non-
Skype for Business) endpoint devices (e.g., mobile phone or PBX phone) are used by the
Skype for Business users, presence status information can only be reported to the Skype
for Business Server by the device. For example, if John and Alice are Skype for Business
users and John makes or receives a call on a mobile device, Alice is able to see that John
is in a call, even though the call is not on a native Skype for Business endpoint. Once the
device reports the presence status, the Skype for Business Server sends this status
change to the Skype for Business users in the network.
Note:
•
Currently, the device reports the following presence status:
√
"On the Phone" - user is busy (in a call or doesn't want to be disturbed)
√
"Clear" - cancels the "On the Phone" status (returning the user's presence to its
previous state)
•
The feature supports Skype for Business Server 2015 and Lync Server version
5.0.8308.866 and later.
•
The feature is applicable to the SBC application and the Gateway application (Tel-
to-IP calls only).
•
This is a license-based feature and is available only if it is included in the License
Key installed on the device. For ordering the feature, please contact your
AudioCodes sales representative.
The device notifies the Skype for Business Server of a user's presence status, by using
SIP PUBLISH messages. The message transactions between the device and Skype for
Business Server is as follows:
1. The device routes a call between two Skype for Business users and when connected,
sends a PUBLISH message with the Event header set to "presence", Expires header
set to "600", Content-Type header set to "application/pidf+xml", and where the XML
body's "activity" is set to "on-the-phone", as shown in the following example for user
John Doe:
PUBLISH sip:john.doe@sfb.example SIP/2.0
From: <sip:john.doe@sfb.example>;tag=1c537837102
To: <sip:john.doe@sfb.example>
CSeq: 1 PUBLISH
Event:
presence
Expires: 600
Content-Type: application/pidf+xml
Content-Length: 489
<?xml version="1.0" encoding="utf-8"?>
<presence xmlns="urn:ietf:params:xml:ns:pidf"
xmlns:ep="urn:ietf:params:xml:ns:pidf:status:rpid-status"
xmlns:et="urn:ietf:params:xml:ns:pidf:rpid-tuple"
xmlns:ci="urn:ietf:params:xml:ns:pidf:cipid"
entity="sip:john.doe@sfb.example">
<tuple id="0">
<status>
<basic>open</basic>
<ep:activities>
<ep:activity>
on-the-phone </ep:activity>
</ep:activities>
</status>
</tuple>