Collapse AllExpand All

14.2.5.13. Busy override, emergency intrusion and emergency disconnect for SIP (UFIP) subscribers Previous topic Parent topic Child topic Next topic

Busy override, emergency intrusion and emergency disconnect are implemented for SIP (UFIP) subscriber in version V8R1 with specific SIP interface restrictions/limitations:
Busy override, emergency intrusion and emergency disconnect against SIP subscriber:
  1. The Display at SIP level will not be updated
    • At CP level the SIP subscriber is considered busy if at least one transaction is busy when override, emergency intrusion or emergency disconnect are invoked (activation of “second call” feature at device level has to be taken into account).
    Busy override, emergency intrusion and emergency disconnect invoked from a SIP subscriber:
    • Currently, only WL3/WL4 (UFIP) devices support the feature.
    • The system supports the feature for any kind of SIP (UFIP) device but at device level the interface must be implemented to support specific menu options for busy override, emergency intrusion and emergency disconnect
    • The features can be invoked from any SIP (UFIP) by dialing specific WABE codes (KNOVR, EOVR, RELEASE) followed by the station number.
    Feature activation via AMO commands:
    CHANGE-FEASU:TYPE=A,CM=OVR&EMOVR&EMRLS;
    CHANGE-ZAND:TYPE=ALLDATA,OVRMST=YES;
    SDAT attributes for intruding station:
    CHANGE-SDAT:STNO=13203,TYPE=ATTRIBUT,AATTR=EOVR&KNOVR;
    ADD-WABE:*56,,,KNOVR,N,,,,,,,,;
    ADD-WABE:*57,,,EOVR,N,,,,,,,,;
    ADD-WABE:*58,,,RELEASE,N,,,,,,,,;
    For more details please consult the feature description documentation.
    In case of WL3/WL4 (UFIP) device, the feature activation and the activation codes must also be configured in phone WBM.