The issue was found and described early in jira: XTRN -229 problem#1. It could be easily reproduced by set up 3 Polycom phones: say 200 (transferee), 201(transferor) and 202 (target) with the latest fw 3.2.2.0477. The sipXconfig parameter 'allowtransferOnProceeding' had been set to 2 for each phone to avoid transferor phone get locked in VM (problem #2 reported in xtrn -229).
Let 200 call 201, and 201 will transfer the phone call to 202. Before the target (202) answers the phone, 201 finishes the transfer task by pressing the soft key 'trnsfer' again. The target rings OK but if the call is left unanswered (or the target's 'Reject' softkey is pressed) the transferee (200) gets fast busy, instead of voicemail. Wireshark trace shows the target phone sent the correct message "486 busy" to the server and transferee, but for some reason transferee can not be directed to the voice mail but hear the fast busy tone. Suspect it is a call server busy message handling issue. Ke Liu [email protected] Telephone (613) 763 6367 / ESN 393 6367 ------------------------------------------------------------------------ -----------
_______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev sipXecs IP PBX -- http://www.sipfoundry.org/
