Overview of SIP DECT 15
If your system uses SIPN, you cannot use a DECT handset to configure
Call Forward or Hunting or to configure Call Restrictions. If the system
uses a twinned configuration, you can use the twinned desk phone to
configure Call Forward for the Primary DN with the existing keys or with
Flexible Feature Codes (FFC).
On SIPL configurations, you can activate FFC features such as Call
Forward, Make Set Busy, Ring Again, Call Park, which are available for
SIP Line users.
CallPilot and Message Waiting Indication support
DECT handsets subscribed on SIP DECT can use CallPilot.
You can configure Call Forward No Answer for the Primary DN of the
UEXT so that the unanswered calls on the corresponding DECT handset
or IP phone (in the case of a twinned configuration) are forwarded to
CallPilot. Calls can also be forwarded to CallPilot as busy treatment for
the Primary DN.
A user can call the CallPilot system from a DECT handset and log on to
the voice mailbox with the corresponding DN and password. The user can
then use the voice menus of the system as usual.
The system can send MWI to the DECT handset through the SIP Trunk.
If your system uses SIPL, enter the MWI primary DN of the SIP DECT
user. For SIPN configurations, configure additional DNs (to which CallPilot
sends MWI) for the voice mailbox corresponding to the UEXT Primary DN.
The additional DN configured in CallPilot is the external DN of the DECT
handset, which is the Target DN on the UEXT corresponding to the DECT
handset.
CS 1000 supports only the Unsolicited MWI NOTIFY model. An external
SIP UA cannot SUBSCRIBE to MWI NOTIFY messages and cannot
request the current status of MWI for the DN from the system (by sending
SUBSCRIBE messages). Instead, a SIP UA must be ready to receive MWI
NOTIFY messages from the system even if it did not SUBSCRIBE, and it
must update MWI according to those messages only.
For SIPN configurations, due to the Unsolicited MWI NOTIFY model used
in SIPN, the DECT handset relies on the MWI notifications sent by CS
1000. Therefore, the MWI based on the existing mechanism can be in the
incorrect state on the DECT handset if the handset was turned off and
on. The MWI can be in the incorrect state if the handset leaves and then
reenters the coverage area of the SIP DECT. In this situation, the MWI on
the DECT handset returns to the correct state when the next MWI state
change occurs in the CallPilot system.
Nortel Communication Server 1000
SIP DECT Fundamentals
NN43120-123 02.02 30 March 2010
Copyright © 2008-2010 Nortel Networks. All Rights Reserved.
.