Page 92 of 910 Features
553-3001-365 Standard 4.00 August 2005
Server loses the call’s information or the SIP Gateway’s Signaling Server
reboots, the Converged Desktop call is impacted.
Note: A Converged Desktop consists of a telephone and multimedia
PC Client (PCC) software.
The following are scenario examples.
Example 1: The IP Phone’s TLAN subnet fails and the IP Phone reregisters
with the same or a different TPS.
In this case, both the voice and multimedia sessions survive: if a SIP call is
established with the other party in the SIP domain, the call is not released as
the IP Phone reregisters. The multimedia applications still work: the presence
is updated on PCC after the telephone reregisters.
If the unregistered converged IP Phone releases the call during the TLAN
subnet failure, then the Presence status is updated on PCC as the idle
converged IP Phone reregisters.
Example 2: The IP Phone’s Signaling Server fails and the IP Phone
reregisters with the same or a different TPS (active converged IP Phone and
SIP Gateway are on different Signaling Servers in the same node).
In this case, both the voice and multimedia sessions survive; the scenario is
the same as the TLAN subnet failure in Example 1.
Example 3: The IP Phone’s ELAN subnet fails and the IP Phone reregisters
with the same or a different TPS.
The voice session survives. If the ELAN subnet comes back up before the
IP Phone changes the call state (that is, releases the call), then the multimedia
session is not impacted.
If the IP Phone releases the call when the ELAN subnet is still down, the PCC
status update happens when the idle converged IP Phone reregisters with the
system.
If the call is released by the supervisory timer, the status is updated on PCC
after the ELAN subnet comes back up and the Converged Desktop’s AML