-
Both H.323 and SIP devices do not work with full functionality on Dual Registration. The normal way is to configure the phone as H.323 with a SIP Optim mapping. The other way is to configure the phone as SIP. However, you must prefer one protocol over the other.
-
If you configure the phone as H.323 with a SIP Optim mapping, the H.323 phone works with full functionality. In this scenario, the SIP phone may lack some features.
-
If you configure the phone as SIP, the SIP phone works with full functionality. In this scenario, the H.323 phone may lack some features.
-
If you are migrating from H.323 to SIP and if you want the SIP phone to work with full functionality, then you must reconfigure the phone as SIP. In this scenario, the H.323 phone gets reduced functionality as described elsewhere in this section.
-
If the H.323 phone and the SIP phone are on the same call and if a user presses the drop button on one of the phones, the call is dropped from both the phones.
Note:
Instead of using the drop button, if the user goes on hook from one of the phones, the call remains active on the other phone.
-
When an endpoint is configured using dual registration, some of the Equinox features do not work. To overcome this, you must configure the endpoint as SIP. If multiple SIP devices are required, then you must use Multiple Device Access (MDA) instead of dual registration.
-
When a Dual Registration user places a call using the SIP device, the H.323 device does not display a Bridge soft key. Instead the H.323 device shows soft keys for hold, conference, transfer, and drop. To join the call, the user needs to either press the button next to the call appearance or the OK button on the H.323 phone.
-
When a Dual Registration user makes an outgoing call on the H.323 device, the SIP endpoint shows the Bridge soft key without the hold, conference, transfer, and drop soft keys.
Note:
If the SIP user sets the call on hold or unhold, all the soft keys disappear and the soft key for bridge appears on the screen.
-
No feature activation is supported while the SIP and H.323 endpoints are on the same call.
-
When a paging group receives a call, the H.323 phone goes on speaker and a one-way talk path is established from the called party to the H.323 phone. The speaker on the SIP phone is not activated, but the SIP phone can bridge on to the call. If the caller bridges on to the call from the SIP phone, a two-way talk path is established between the calling party and the SIP phone.
-
If a call is answered by the H.323 phone, the call log on the SIP phone shows a missed call entry.
-
If the H.323 phone bridges on to the existing call, the soft buttons for hold, conf, transfer, and end call appear on the phone. These soft buttons appear on the phone even when the H.323 phone goes off hook.
Note:
You can rejoin the bridge by using the OK button on the hand set.
-
The H.323 telephone can bridge onto the call by selecting the simulated bridge appearance. The system does not support bridging if Exclusion is active. While the dual registered SIP and H.323 endpoints are both bridged onto the same call, the system does not support any feature usage affecting that call.
-
SIP and H.323 endpoints with a dual registered extension do not support the call transfer functionality. However, when you activate this feature from H.323, transfer recall works as expected. Both the endpoints ring after transfer recall timer expires.
-
The following features are not supported on a dual registered extension:
-
Speakerphone paging
-
Automatic exclusion
-
PSA disassociated FAC
