Administrator’s Guide for SIP-T58V/T58A/T56A/CP960 IP Phones
334
t.X.group_pickup_code”) takes precedence over that configured on a phone basis (configured by the para-
meter “features.pickup.group_pickup_code”).
Permitted
Values
String within 32 characters
Default Blank
Web UI Account->Advanced->Group Call Pickup Code
[1]
X is the account ID. For T58V/T58A/T56A, X=1-16; for CP960, X=1.
Dialog Info Call Pickup
While some SIP servers implement directed call pickup using a directed call pickup code, others also support imple-
ment this feature through SIP signals.
Note
In this way, you do not need to configure the directed call pickup code.
If you enable the phone to implement directed call pickup through SIP signals, the phone picks up an incoming call via
a SIP INVITE message with a Replaces header. The value of Replaces is derived from a NOTIFY message with dialog-info
event. This feature applies only to directed call pick-up attempts initiated against monitored BLF resources. It means
you can pick up an incoming call by tapping a BLF/BLF List key.
Example of the dialog-info carried in NOTIFY message:
<?xml version="1.0"?>
<dialog-info xmlns="urn:ietf:params:xml:ns:dialog-info" version="6" state="partial" entity-
y="sip:1011@10.2.1.48:5060">
<dialog id="65603" call-id="0_1756536024@10.10.20.34" local-tag="3408640225" remote-tag="3779921438"
direction="recipient">
<state>early</state>
<local>
<identity>sip:1011@10.2.1.48:5060</identity>
<target uri="sip:1011@10.2.1.48:5060"/>
</local>
<remote>
<identity>sip:1058@10.2.1.48:5060</identity>
<target uri="sip:1058@10.2.1.48:5060"/>
</remote>
</dialog>
</dialog-info>
Example of the Replaces carried in INVITE message:
Via: SIP/2.0/UDP 10.10.20.18:5060;branch=z9hG4bK2026058891