Category:HowTo:Extension Monitoring:RFC4662

From Snom User Wiki

Jump to: navigation, search

Contents

Terminology

  1. Ext 1: Monitoring Extension
  2. PBX: SIP Back-To- Back User Agent (B2BUA) (Event List Subscription according to RFC 4662 is required)
  3. Ext 2...Ext n: Monitored Extensions

Configuration

snom3x0 phone

  1. Navigate to the "SIP" Tab of the "Identity" Web User Interface page of the monitoring phone (Ext 1 = 484)
  2. Change the following settings:
    1. Extension Monitoring Call Pickup List= ON
    2. Extension Monitoring Call Pickup List URI <-- Extension to be used for Event List Supscription, e.g . 484
  3. Save the settings. A reboot is required.

PBX

The following example uses PBXnSIP:

  1. Navigate to the account settings page of the extension used for "Event List Subscription", e.g. Ext 1 = 484:
    • Example
  2. Add those extensions you want to monitor, e.g. Ext 2 = 485 Ext 3 = 486
  3. Save the settings.

SIP Flow (Subscription)

After rebooting the monitoring phone the following subscription process will be initiated:

1) The phone sends a SUBSCRIBE message with SIP header "Supported: eventlist" for Ext 1 to the PBX:

Sent to ...:

SUBSCRIBE sip:Ext 1;user=phone SIP/2.0
Via: ...
From: <sip:Ext 1>;tag=dba25pdrdg
To: <sip:Ext 1;user=phone>
Call-ID: ...
CSeq: 1 SUBSCRIBE
Max-Forwards: 70
Contact: ...
Event: dialog
Accept: application/dialog-info+xml,multipart/related
Supported: eventlist
User-Agent: snom370/7.1.33
Expires: 3600
Content-Length: 0

2) The PBX confirms the SUBSCRIBE message with SIP header Require: eventlist and changes the expiration time to 182 seconds:

Received from ...:

SIP/2.0 200 Ok
Via: ...
From: <sip:Ext 1>;tag=dba25pdrdg
To: <sip:Ext 1;...
Call-ID: ...
CSeq: 1 SUBSCRIBE
Contact: ...
Require: eventlist
Expires: 182
Content-Length: 0

3) Immediately a NOTIFY is sent by the PBX containing the monitored extensions in the XML multipart header separated by "break" limiters.

Received from ...:

NOTIFY sip:Ext 1:...
Via: ...
From: <sip:Ext 1;...
To: <sip:Ext 1>;...
Call-ID: ...
CSeq: 17165 NOTIFY
Max-Forwards: 70
Contact: ...
Event: dialog
Subscription-State: active;expires=195
Content-Type: multipart/related;boundary=break;type="application/dialog-info+xml"
Content-Length: 675

--break
Content-Type: application/dialog-info+xml
<?xml version="1.0"?>
<dialog-info 
  xmlns="urn:ietf:params:xml:ns:dialog-info"
  version="1"
  state="full" 
  entity="sip:Ext 2">
  <dialog>
   <local>
    <identity
     display="Ext 2 (1st monitored extension)">sip:Ext 2
    </identity>
    <target uri="sip:Ext 2"/>
   </local>
  </dialog>
 </dialog-info>
 --break
 Content-Type: application/dialog-info+xml
 <?xml version="1.0"?>
 <dialog-info
  xmlns="urn:ietf:params:xml:ns:dialog-info"
  version="2"
  state="full"
  entity="sip:Ext 3">
  <dialog>
   <local>
    <identity
     display="Ext 3(2nd monitored extension)">sip:Ext 3
    </identity>
    <target uri="sip:Ext 3"/>
   </local></dialog>
  </dialog-info>
--break--

4) The phone accepts the multipart message:

Sent to ...:

SIP/2.0 200 Ok
Via: ...
From: <sip:Ext 1;...
To: <sip:Ext 1>;tag=dba25pdrdg
Call-ID: ...
CSeq: 17165 NOTIFY
Content-Length: 0

Status

In firmware version Image:Fw-version-7.gif the status of the outgoing subscription can be monitored in the "Status --> Subscriptions" Web User Interface page

Result

"Dialog" state changes of the monitored extensions (Ext 2 = 485, Ext 3 = 486) cause the PBX to send individual SIP NOTIFY messages to Ext 1 = 484 in order to trigger the Calls Screen to show the call activity.

This category currently contains no pages or media.

Personal tools
Interoperability