Unicorn 3101 User Manual
Copyright © 2008
Hanlong Technology Co., Ltd Page 10 of 29
number.
Examples:
a) If the target IP address is 192.168.0.160, the dialing convention is
*47 or Voice Prompt with option 47, then 192*168*0*160.
followed by pressing the “#” key if it is configured as a send key or wait 4 seconds. In this
case,the default destination port 5060 is used if no port is specified
.
b) If the target IP address/port is 192.168.1.20:5062, then the dialing convention would be:
*47 or Voice Prompt with option 47, then 192*168*0*160*5062
followed by pressing the
“#” key, if it is configured as a send key or wait for 4 seconds.
NOTE:
When completing direct IP call, the “
Use Random Port
” should set to “NO”.
5.2.6
Blind Transfer
Assuming that call party A and party B are talking to each other on the phone. Party A
wants to transfer party B to party C:
Party A presses FLASH (on the analog phone, or Hook Flash for old model phones) to
get a dial tone.
Then party A dials *87 then dials party C’s number, and then # (or wait for 4 seconds)
Party A can hangs up the phone.
Note: Call features have to be activated during web configuration by selecting YES to
“Enable Call Features”. These features need to be supported by your
SIP gatekeeper/proxy server in order to work.
Party A can hold on to the phone and wait for one of the three following events:
1. A quick confirmation tone (temporarily using the call waiting indication tone) followed
by a dial tone.This indicates the transfer is successful (transferee has received a 200
OK signal from transfer target). At this point, party A can either hang up or make
another call.
2. A quick busy tone followed by a restored call (on supported SIP
gatekeeper platforms only). This means the transferee has received a 4xx
response signal for the INVITE and will try to recover the call. The busy tone is just to
indicate to the transferor that the transfer has failed.
3. Busy tone keeps playing. This means the Unicorn 3101 has failed to receive the
second NOTIFY signal from the transferee and decided to time out.
Note:
this does not indicate the transfer has been successful, nor does it indicate the
transfer has failed. When transferee uses a device that does not support the second
NOTIFY signal, this will be the case. In poor or unstable network scenarios, this could also
happen, although the transfer may have been completed successfully.
