SIP User's Manual 364 Document #: LTRT-68806
Mediant 2000 & TP-1610 & TP-260/UNI
îš„ The hold and retrieve functionalities are implemented by REINVITE messages. The IP
address 0.0.0.0 as the connection IP address or the string ‘a=inactive’ in the received
Re-INVITE SDP cause the gateway to enter Hold state and to play held tone
(configured in the gateway) to the PBX/PSTN. If the string ‘a=sendonly’ is received in
the SDP message, the gateway stops sending RTP packets, but continues to listen to
the incoming RTP packets. Usually, the remote party plays, in this scenario, Music on
Hold (MOH) and the gateway forwards the MOH to the held party.
7.12.2 Call Transfer
There are two types of call transfers:
îš„ Consultation Transfer:
The common way to perform a consultation transfer is as follows:
In the transfer scenario there are three parties: Party A = transferring, Party B =
transferred, Party C = transferred to.
• A Calls B.
• B answers.
• A presses the hook-flash and puts B on-hold (party B hears a hold tone).
• A dials C.
• After A completes dialing C, A can perform the transfer by on-hooking the A
phone.
• After the transfer is complete, B and C parties are engaged in a call.
The transfer can be initiated at any of the following stages of the call between A and
C:
• Just after completing dialing C phone number - transfer from setup.
• While hearing Ringback – transfer from alert.
• While speaking to C - transfer from active.
îš„ Blind Transfer:
Blind transfer is performed after we have a call between A and B, and party A decides
to immediately transfer the call to C without speaking with C. The result of the transfer
is a call between B and C (just like consultation transfer only skipping the consultation
stage).
Note the following SIP issue:
îš„ The gateway doesn't initiate call transfer, it only responds to call transfer requests.
To Next Page
Loading...
Need help?
General