Bridged Line Appearance on snom phones.pdf - snom technology AG

Bridged Line Appearance on snom phones.pdf - snom technology AG Bridged Line Appearance on snom phones.pdf - snom technology AG

28.05.2013 Views

snom 360/320 ong>Bridgedong> ong>Lineong> ong>Appearanceong> The ong>Bridgedong> ong>Lineong> ong>Appearanceong> (BLA) feature allows subscribers to share SIP lines and also provides status monitoring of the shared line. The BLA feature is commonly offered in the IP Centrex services and IP-PBX offerings. When a user places an outgoing call using such an appearance, all members belonging to that particular BLA group are notified of this usage, and are blocked from using this line appearance until the line goes back to idle state or if the call is placed on hold. Similarly all members of the BLA group are notified of an incoming call and the call can be picked up on a line appearance associated with the BLA extension. This ong>Bridgedong>/Shared ong>Lineong> ong>Appearanceong> (BLA) feature is also available on snom 360/320. The new feature allows subscribers to share the available SIP lines without running into deadlock situations. For visual indications, LEDs available on the snom phones indicate the status of the shared lines and also allow a BLA group member to pickup incoming calls to the BLA group. When the shared line is occupied by a BLA group member, other members of the group are blocked from using the line until its status goes back to idle thus indicating availability. The following screen shots indicate how ong>Bridgedong> ong>Lineong>s can be configured on snom phones. ong>Lineong> Settings: These settings reflect the basic SIP settings for registering the bridged line. snom technology AG 1

<strong>snom</strong> 360/320 <str<strong>on</strong>g>Bridged</str<strong>on</strong>g> <str<strong>on</strong>g>Line</str<strong>on</strong>g> <str<strong>on</strong>g>Appearance</str<strong>on</strong>g><br />

The <str<strong>on</strong>g>Bridged</str<strong>on</strong>g> <str<strong>on</strong>g>Line</str<strong>on</strong>g> <str<strong>on</strong>g>Appearance</str<strong>on</strong>g> (BLA) feature allows subscribers to share SIP lines and<br />

also provides status m<strong>on</strong>itoring of the shared line. The BLA feature is comm<strong>on</strong>ly offered<br />

in the IP Centrex services and IP-PBX offerings. When a user places an outgoing call<br />

using such an appearance, all members bel<strong>on</strong>ging to that particular BLA group are<br />

notified of this usage, and are blocked from using this line appearance until the line goes<br />

back to idle state or if the call is placed <strong>on</strong> hold. Similarly all members of the BLA group<br />

are notified of an incoming call and the call can be picked up <strong>on</strong> a line appearance<br />

associated with the BLA extensi<strong>on</strong>.<br />

This <str<strong>on</strong>g>Bridged</str<strong>on</strong>g>/Shared <str<strong>on</strong>g>Line</str<strong>on</strong>g> <str<strong>on</strong>g>Appearance</str<strong>on</strong>g> (BLA) feature is also available <strong>on</strong> <strong>snom</strong> 360/320.<br />

The new feature allows subscribers to share the available SIP lines without running into<br />

deadlock situati<strong>on</strong>s. For visual indicati<strong>on</strong>s, LEDs available <strong>on</strong> the <strong>snom</strong> ph<strong>on</strong>es indicate<br />

the status of the shared lines and also allow a BLA group member to pickup incoming<br />

calls to the BLA group. When the shared line is occupied by a BLA group member, other<br />

members of the group are blocked from using the line until its status goes back to idle<br />

thus indicating availability. The following screen shots indicate how <str<strong>on</strong>g>Bridged</str<strong>on</strong>g> <str<strong>on</strong>g>Line</str<strong>on</strong>g>s can<br />

be c<strong>on</strong>figured <strong>on</strong> <strong>snom</strong> ph<strong>on</strong>es.<br />

<str<strong>on</strong>g>Line</str<strong>on</strong>g> Settings:<br />

These settings reflect the basic SIP settings for registering the bridged line.<br />

<strong>snom</strong> <strong>technology</strong> <strong>AG</strong> 1


SIP Settings:<br />

These settings indicate the advanced settings which need to be c<strong>on</strong>figured for a bridged<br />

line.<br />

Note: The “Shared <str<strong>on</strong>g>Line</str<strong>on</strong>g>” setting MUST be turned <strong>on</strong> in order to enable the bridged line<br />

appearance feature for a SIP line.<br />

<strong>snom</strong> <strong>technology</strong> <strong>AG</strong> 2


Functi<strong>on</strong> Key Settings:<br />

BLA members can m<strong>on</strong>itor the status of the bridged line via the Functi<strong>on</strong> keys available<br />

<strong>on</strong> the <strong>snom</strong> ph<strong>on</strong>es. For m<strong>on</strong>itoring the status of a bridged line, the functi<strong>on</strong> key must be<br />

c<strong>on</strong>figured as a “Shared <str<strong>on</strong>g>Line</str<strong>on</strong>g>” type. In additi<strong>on</strong>, the “Number” must be set to the bridged<br />

line resource URI. Once the ph<strong>on</strong>e has registered and subscribed successfully for the<br />

BLA resource, the LED corresp<strong>on</strong>ding to the programmed functi<strong>on</strong> key indicates the<br />

status of the bridged line. LED “<strong>on</strong>” indicates the line is in use, while LED “off”<br />

indicates an idle status.<br />

<strong>snom</strong> <strong>technology</strong> <strong>AG</strong> 3


<str<strong>on</strong>g>Bridged</str<strong>on</strong>g> <str<strong>on</strong>g>Line</str<strong>on</strong>g> Subscripti<strong>on</strong>/Notificati<strong>on</strong>:<br />

When a BLA member registers for the BLA resource, the State Agent sends a BLA<br />

subscripti<strong>on</strong> to the member. The BLA member sends its own status to the notificati<strong>on</strong><br />

agent and also subscribes to the BLA resource itself for m<strong>on</strong>itoring the status of the<br />

shared line. The following SIP trace depicts a BLA resource subscripti<strong>on</strong>:<br />

Received from udp:206.229.26.49:9060 at 3/2/2006 03:39:22:515 (617 bytes):<br />

SUBSCRIBE sip:4087661000@192.168.1.134:2100 SIP/2.0<br />

Via: SIP/2.0/UDP<br />

206.229.26.49:5096;branch=z9hG4bK000010e300000007cee51a330000cee51a33000089016210340341<br />

264<br />

Via: SIP/2.0/UDP 206.229.26.51:5096;branch=z9hG4bK1014378165985263<br />

Record-Route: <br />

From: State_Agent ;tag=511619258984691<br />

To: <br />

Call-ID: 86434-1137229931@206.229.26.51<br />

CSeq: 2 SUBSCRIBE<br />

C<strong>on</strong>tact: State_Agent <br />

event: dialog;sla;include-sessi<strong>on</strong>-descripti<strong>on</strong><br />

expires: 3700<br />

C<strong>on</strong>tent-Length: 0<br />

Sent to udp:206.229.26.49:5096 at 3/2/2006 03:39:22:593 (512 bytes):<br />

SIP/2.0 200 OK<br />

Via: SIP/2.0/UDP<br />

206.229.26.49:5096;branch=z9hG4bK000010e300000007cee51a330000cee51a33000089016210340341<br />

264<br />

Via: SIP/2.0/UDP 206.229.26.51:5096;branch=z9hG4bK1014378165985263<br />

Record-Route: <br />

From: "State_Agent" ;tag=511619258984691<br />

To: ;tag=mxrutohi9v<br />

Call-ID: 86434-1137229931@206.229.26.51<br />

CSeq: 2 SUBSCRIBE<br />

C<strong>on</strong>tact: <br />

Expires: 3700<br />

C<strong>on</strong>tent-Length: 0<br />

Sent to udp:206.229.26.49:9060 at 3/2/2006 03:39:22:734 (759 bytes):<br />

NOTIFY sip:206.229.26.49:9060 SIP/2.0<br />

Via: SIP/2.0/UDP 192.168.1.134:2100;branch=z9hG4bK-2yvh2wkr55ya;rport<br />

Route: <br />

From: ;tag=mxrutohi9v<br />

To: "State_Agent" ;tag=511619258984691<br />

Call-ID: 86434-1137229931@206.229.26.51<br />

CSeq: 1 NOTIFY<br />

Max-Forwards: 70<br />

C<strong>on</strong>tact: ;flow-id=1<br />

Event: dialog;sla;include-sessi<strong>on</strong>-descripti<strong>on</strong><br />

Subscripti<strong>on</strong>-State: active<br />

C<strong>on</strong>tent-Type: applicati<strong>on</strong>/dialog-info+xml<br />

C<strong>on</strong>tent-Length: 156<br />

<strong>snom</strong> <strong>technology</strong> <strong>AG</strong> 4


<br />

Sent to udp:206.229.26.49:9060 at 3/2/2006 03:39:22:843 (582 bytes):<br />

SUBSCRIBE sip:guid_50b73158-1dd2-11b2-88c4-b03162323164+50b73158@206.229.26.49:5096<br />

SIP/2.0<br />

Via: SIP/2.0/UDP 192.168.1.134:2100;branch=z9hG4bK-kgex912w1b3e;rport<br />

From: ;tag=w1bodf2327<br />

To: <br />

Call-ID: cb60e3431bb7-bcfj6sxyjsl6@<strong>snom</strong>360-000413231325<br />

CSeq: 1 SUBSCRIBE<br />

Max-Forwards: 70<br />

C<strong>on</strong>tact: ;flow-id=1<br />

Event: dialog;sla;include-sessi<strong>on</strong>-descripti<strong>on</strong><br />

Accept: applicati<strong>on</strong>/dialog-info+xml<br />

Expires: 3600<br />

C<strong>on</strong>tent-Length: 0<br />

Received from udp:206.229.26.49:9060 at 3/2/2006 03:39:24:171 (536 bytes):<br />

SIP/2.0 200 OK<br />

Via: SIP/2.0/UDP 192.168.1.134:2100;branch=z9hG4bK-<br />

2yvh2wkr55ya;rport=2100;received=195.2.174.186<br />

Record-Route: <br />

From: ;tag=mxrutohi9v<br />

To: "State_Agent" ;tag=511619258984691<br />

Call-ID: 86434-1137229931@206.229.26.51<br />

CSeq: 1 NOTIFY<br />

C<strong>on</strong>tact: <br />

allow-events: dialog;sla;include-sessi<strong>on</strong>-descripti<strong>on</strong><br />

Allow: NOTIFY, SUBSCRIBE<br />

C<strong>on</strong>tent-Length: 0<br />

Received from udp:206.229.26.49:9060 at 3/2/2006 03:39:24:281 (608 bytes):<br />

SIP/2.0 202 Accepted<br />

Via: SIP/2.0/UDP 192.168.1.134:2100;branch=z9hG4bKkgex912w1b3e;rport=2100;received=195.2.174.186<br />

Record-Route: <br />

From: ;tag=w1bodf2327<br />

To: ;tag=1076438320835203<br />

Call-ID: cb60e3431bb7-bcfj6sxyjsl6@<strong>snom</strong>360-000413231325<br />

CSeq: 1 SUBSCRIBE<br />

C<strong>on</strong>tact: <br />

allow-events: dialog;sla;include-sessi<strong>on</strong>-descripti<strong>on</strong><br />

expires: 3600<br />

Allow: NOTIFY, SUBSCRIBE<br />

C<strong>on</strong>tent-Length: 0<br />

Received from udp:206.229.26.49:9060 at 3/2/2006 03:39:24:328 (910 bytes):<br />

<strong>snom</strong> <strong>technology</strong> <strong>AG</strong> 5


NOTIFY sip:4087661000@192.168.1.134:2100 SIP/2.0<br />

Via: SIP/2.0/UDP<br />

206.229.26.49:5096;branch=z9hG4bK000010e300000007cee51a330000cee51a33000089016291335912<br />

297<br />

Via: SIP/2.0/UDP 206.229.26.51:5096;branch=z9hG4bK604580781864957<br />

Record-Route: <br />

From: ;tag=1076438320835203<br />

To: ;tag=w1bodf2327<br />

Call-ID: cb60e3431bb7-bcfj6sxyjsl6@<strong>snom</strong>360-000413231325<br />

CSeq: 2 NOTIFY<br />

C<strong>on</strong>tact: <br />

max-forwards: 70<br />

event: dialog;sla;include-sessi<strong>on</strong>-descripti<strong>on</strong><br />

subscripti<strong>on</strong>-state: active<br />

C<strong>on</strong>tent-Type: applicati<strong>on</strong>/dialog-info+xml<br />

C<strong>on</strong>tent-Length: 00160<br />

<br />

<br />

<br />

Busy Status Indicati<strong>on</strong>:<br />

The following notificati<strong>on</strong> from the state agent indicates a seized bridged line:<br />

Received from udp:206.229.26.49:9060 at 3/2/2006 03:48:41:171 (967 bytes):<br />

NOTIFY sip:4087661000@192.168.1.134:2100 SIP/2.0<br />

Via: SIP/2.0/UDP<br />

206.229.26.49:5096;branch=z9hG4bK000010e300000007cee51a330000cee51a33000089016591296756<br />

223<br />

Via: SIP/2.0/UDP 206.229.26.51:5096;branch=z9hG4bK177044948888427<br />

Record-Route: <br />

From: ;tag=1076438320835203<br />

To: ;tag=w1bodf2327<br />

Call-ID: cb60e3431bb7-bcfj6sxyjsl6@<strong>snom</strong>360-000413231325<br />

CSeq: 5 NOTIFY<br />

C<strong>on</strong>tact: <br />

max-forwards: 70<br />

event: dialog;sla;include-sessi<strong>on</strong>-descripti<strong>on</strong><br />

subscripti<strong>on</strong>-state: active<br />

C<strong>on</strong>tent-Type: applicati<strong>on</strong>/dialog-info+xml<br />

C<strong>on</strong>tent-Length: 00271<br />

<br />

<br />

<br />

trying<br />

<br />

<br />

Sent to udp:206.229.26.49:5096 at 3/2/2006 03:48:41:171 (436 bytes):<br />

SIP/2.0 200 Ok<br />

Via: SIP/2.0/UDP<br />

<strong>snom</strong> <strong>technology</strong> <strong>AG</strong> 6


206.229.26.49:5096;branch=z9hG4bK000010e300000007cee51a330000cee51a33000089016591296756<br />

223<br />

Via: SIP/2.0/UDP 206.229.26.51:5096;branch=z9hG4bK177044948888427<br />

Record-Route: <br />

From: ;tag=1076438320835203<br />

To: ;tag=w1bodf2327<br />

Call-ID: cb60e3431bb7-bcfj6sxyjsl6@<strong>snom</strong>360-000413231325<br />

CSeq: 5 NOTIFY<br />

C<strong>on</strong>tent-Length: 0<br />

Idle Status Indicati<strong>on</strong>:<br />

The following notificati<strong>on</strong> from the state agent indicates an idle bridged line:<br />

Received from udp:206.229.26.49:9060 at 3/2/2006 03:56:01:140 (1204 bytes):<br />

NOTIFY sip:4087661000@192.168.1.134:2100 SIP/2.0<br />

Via: SIP/2.0/UDP<br />

206.229.26.49:5096;branch=z9hG4bK000010e300000007cee51a330000cee51a3300008901689-<br />

1800127106<br />

Via: SIP/2.0/UDP 206.229.26.51:5096;branch=z9hG4bK1766615073805891<br />

Record-Route: <br />

From: ;tag=1076438320835203<br />

To: ;tag=w1bodf2327<br />

Call-ID: cb60e3431bb7-bcfj6sxyjsl6@<strong>snom</strong>360-000413231325<br />

CSeq: 8 NOTIFY<br />

C<strong>on</strong>tact: <br />

max-forwards: 70<br />

event: dialog;sla;include-sessi<strong>on</strong>-descripti<strong>on</strong><br />

subscripti<strong>on</strong>-state: active<br />

C<strong>on</strong>tent-Type: applicati<strong>on</strong>/dialog-info+xml<br />

C<strong>on</strong>tent-Length: 00506<br />

<br />

<br />

<br />

terminated<br />

<br />

<br />

<br />

<br />

<br />

<br />

<br />

Sent to udp:206.229.26.49:5096 at 3/2/2006 03:56:01:234 (438 bytes):<br />

SIP/2.0 200 Ok<br />

Via: SIP/2.0/UDP<br />

206.229.26.49:5096;branch=z9hG4bK000010e300000007cee51a330000cee51a3300008901689-<br />

1800127106<br />

Via: SIP/2.0/UDP 206.229.26.51:5096;branch=z9hG4bK1766615073805891<br />

Record-Route: <br />

From: ;tag=1076438320835203<br />

To: ;tag=w1bodf2327<br />

Call-ID: cb60e3431bb7-bcfj6sxyjsl6@<strong>snom</strong>360-000413231325<br />

CSeq: 8 NOTIFY<br />

C<strong>on</strong>tent-Length: 0<br />

<strong>snom</strong> <strong>technology</strong> <strong>AG</strong> 7

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!