On Tue, 2008-07-29 at 15:38 -0400, Becker, Jesse wrote: > Using SipX 3.10 we have found that when someone transfers a caller to > another phone the recipients phones displays the caller ID of the > phone that made the transfer. It doesn’t seem to refresh once the > originating party gets connected to the final destination. > > > > Example: > > A vendor calls our Helpdesk and asks for our CIO. The helpdesk does a > blind transfer to the CIO. The CIO answers expecting it to be a > Helpdesk technician, however, it is a vendor doing a cold call. > > > > Is there a way to get the calling party information to refresh once > the transfer has been completed? Is this a setting of the phone or is > this the expected behavior of SipXECS.
This is mostly an artifact of how SIP works, but there is a step you can take that helps. What your users are doing is a consultative transfer - they place the caller on hold, make a new call to the target, and then switch the caller to that new call. Doing it this way, the new target (your CIO) sees the caller that created the call to them - the Help Desk. If you train your users to use blind transfer, the caller will be send directly to the target (with no opportunity to tell them the call is coming), but the caller id displayed at the target will be the real original caller. There may be things you can do to program the phone to make this easier; I don't know. -- Scott Lawrence tel:+1.781.229.0533;ext=162 or sip:[EMAIL PROTECTED] sipXecs project coordinator - SIPfoundry http://www.sipfoundry.org/sipXecs CTO, Voice Solutions - Bluesocket Inc. http://www.bluesocket.com/ http://www.pingtel.com/ _______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users
