
Chapter 4 Configuring SPA9000 Features
Managing Call Forwarding
Contact:
Content-Type: application/dialog-info+xml <?xml version=”1.0”?>
<dialog id=”201” direction=”initiator”> <local>
<identity
<param
</local>
<state>trying</state>
</dialog>
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:
From:
CSeq: 6583 NOTIFY
Via: SIP/2.0/UDP
Server:
3.The SPA9000 notifies other client stations sharing the line key on the shared extension:
NOTIFY sip:5041@192.168.0.6:5060 SIP/2.0
Via: SIP/2.0/UDP
From: PBX Line 1 <sip:37683101@matrix.sipura.com>;tag=5080117180da6835o2
To: <sip:5041@192.168.0.6:5060>
CSeq: 56195
<?xml version=”1.0”?>
<local>
<identity
<param
</local>
<state>trying</state>
</dialog>
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
| Linksys SPA9000 Administrator Guide |
Document Version 3.01 |