Cisco Linksys SPA9000 User Manual
Page 114
4-24
Linksys SPA9000 Administrator Guide
Document Version 3.01
Chapter 4 Configuring SPA9000 Features
Managing Call Forwarding
Max-Forwards: 70
Contact: “User-A”
Content-Type: application/dialog-info+xml
entity=”sip:[email protected]:6060”>
2.
The SPA9000 grants the line seize request by replying 202 (because no one else is using that line
key):
SIP/2.0 202 Accepted
To: “User-A”
From: “User-A”
Call-ID: [email protected]
CSeq: 6583 NOTIFY
Via: SIP/2.0/UDP 192.168.0.4:5061;branch=z9hG4bK-55f99f8e
Server: Sipura/SPA2100-3.1.5(a)
Content-Length: 0
3.
The SPA9000 notifies other client stations sharing the line key on the shared extension:
NOTIFY sip:[email protected]:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.0.1:6060;branch=z9hG4bK-1cae6e99
From: PBX Line 1
To:
Call-ID: 3ecb02c9-250f41cd@localhost
CSeq: 56195 NOTIFYMax-Forwards: 70Event: dialog
Content-Length: 397
Content-Type: application/dialog-info+xml
entity=”[email protected]:6060”>
When a client station sends the initial NOTIFY to the SPA9000, all the line key resources allocated to
this station, if any, are released immediately to avoid locking up of line keys because of client reboot.
The same is done when the registration of the client station expires.
Note that the SPA9000 assumes all partial-state dialog-info and contains only one dialog.