18. Call back
This chapter is concerning the call back on OpenTouch. It summarises the configuration mandatory to
provide the service. It gives the restrictions and the limitations. It helps to launch traces.
For a complete description please refer to the technical documentation.
The scope of this chapter is the Call Completion between two ICM users or ICM and OXE users (not
concerning 2 OXE users)
18.1 Glossary
CBR : Call Back Request,
CCBS : Call Completion on Busy Subscriber,
CCNR : Call Completion on No Reply.
18.2 Limits
Only CCBS and CCNR are available for ICM users
Only CCBS is available between OXE and ICM users
18.3 Configuration
The configuration is described in the technical documentation, here is a short summary :
Parameter “one line busy” per user (consider the user busy if one device is busy)
Barring profiles (call completion enabler)
Max number of lines for a MyIC Phone (important if consider the user busy if one device is busy is
not selected)
Presentation timer for CCNR
Duration of call completion subscription
In case of call between OXE and ICE, with a complex topology with hybrid link, the timer T389 (in the
trunk category of hybrid link) must be increased to 100 at least.
If the timer is too low the ringing on MyIC phone will be too short, during the call back (crms00338963).
18.4 Components
Call back request when the caller is an ICM user
The calling is routed to a voice application (handled by Lark component) when the called is busy or after a
timeout when the called does not answer. The call back is requested in DTMF.
Phone set -> SIP Server (XS) -> Fox -> Lark -> Chameleon (Event Server) -> RTSM
RTSM and Fox are components of chameleon.
Automatic call back execution when the caller is an ICM user
When the called is available, the automatic call back is executed.
SIP Server -> Lark -> Fox -> SIP Server (XS)
18.5 Logs
The most important are the sipserver and extensible services logs. chameleon logs may also be useful.
To Next Page
Loading...
