Help with call transfers.

[sssputnik]

Our new 3CX system is working very well. However we have an issue with call transfers.
I believe the issue may be down to mapping of SIP fields? (We are using a VoIP provider only).

We are using Yealink phones with latest firmware. (T20 and T26 models) Latest 3CX version.

If an external call comes in:
If I do a Blind Transfer, (<TRAN>EXT<TRAN>) the caller ID comes through fine.
If I do an announced transfer, (<TRAN>EXT# talk to extension <TRAN>) it doesn’t. Instead the EXT I am transferring FROM shows on the destination phone.

I'd like the end recipients handset to show to original caller ID always, not just when a blind transfer happens.

Any assistance on fields to look at etc, Reinvite etc seem to have no influence.

Regards,
Simon.

 

[sssputnik]

Logs of a call. ????'s to hide calling number.

Please post all call logs in code and /code tags, this time it has been done for you - MFM

10:38:45.415  [CM503008]: Call(2243): Call is terminated
10:38:38.728  [CM503008]: Call(2244): Call is terminated
10:38:38.712  [CM505003]: Provider:[Amcom IPSystems] Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [] PBX contact: [sip:[email protected]:5060]
10:38:36.149  [CM503007]: Call(2244): Device joined: sip:[email protected]:5062
10:38:36.149  [CM503007]: Call(2244): Device joined: sip:[email protected]:5062
10:38:33.384  [CM505001]: Ext.1275: Device info: Device Identified: [Man: Yealink;Mod: T20;Rev: General] Capabilities:[reinvite, no-replaces, unable-no-sdp, no-recvonly] UserAgent: [Yealink SIP-T20P 9.43.0.50] PBX contact: [sip:[email protected]:5060]
10:38:33.384  [CM503002]: Call(2244): Alerting sip:[email protected]:5062
10:38:33.024  [CM503025]: Call(2244): Calling Ext:Ext.1275@[Dev:sip:[email protected]:5062]
10:38:32.977  [CM503004]: Call(2244): Route 1: Ext:Ext.1275@[Dev:sip:[email protected]:5062]
10:38:32.977  [CM503010]: Making route(s) to <sip:[email protected]>
10:38:32.977  [CM505001]: Ext.1269: Device info: Device Identified: [Man: Yealink;Mod: T26;Rev: General] Capabilities:[reinvite, no-replaces, unable-no-sdp, no-recvonly] UserAgent: [Yealink SIP-T26P 6.43.0.50] PBX contact: [sip:[email protected]:5060]
10:38:32.962  [CM503001]: Call(2244): Incoming call from Ext.1269 to <sip:[email protected]>
10:38:26.055  [CM503007]: Call(2243): Device joined: sip:[email protected]:5062
10:38:26.055  [CM503007]: Call(2243): Device joined: sip:[email protected]:5060
10:38:24.680  [CM505001]: Ext.1269: Device info: Device Identified: [Man: Yealink;Mod: T26;Rev: General] Capabilities:[reinvite, no-replaces, unable-no-sdp, no-recvonly] UserAgent: [Yealink SIP-T26P 6.43.0.50] PBX contact: [sip:[email protected]:5060]
10:38:24.680  [CM503002]: Call(2243): Alerting sip:[email protected]:5062
10:38:24.243  [CM503025]: Call(2243): Calling Ext:Ext.1269@[Dev:sip:[email protected]:5062]
10:38:24.196  [CM503004]: Call(2243): Route 1: Ext:Ext.1269@[Dev:sip:[email protected]:5062]
10:38:24.196  [CM503010]: Making route(s) to <sip:[email protected]:5060>
10:38:24.196  [CM505003]: Provider:[Amcom IPSystems] Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [] PBX contact: [sip:[email protected]:5060]
10:38:24.180  [CM503001]: Call(2243): Incoming call from ??????????@(Ln.10002@Amcom IPSystems) to <sip:[email protected]:5060>
10:38:24.180  [CM503012]: Inbound office hours rule (Simon Shaw) for 10002 forwards to DN:1269

 

[StefanW]

at the moment you will be not able to fix it. The Reffer or screen refresh is not more read by the phone.
V9 addresses this issue with many phones with changing the call take over to re-invites with replaces. this should work then also for phones what dont understand it before.

 

[sssputnik]

OK thanks Stefan. Looking forward to the new version.