Call XFR Failed

[Chaz]

I am getting this once we added a couple new phones. Our call comes into the Digital Receptionist, then when pressing 1 or 2 to go to 201 or 202, it pauses then says, "call transfer failed"

09/10/2019 3:42:48 PM - Call to T:Extn:201@[Dev:sip:[email protected]:5060] from L:15.1[Line:10000<<CHAULK,CHAZ ] failed, cause: Cause: 400 Bad Request/INVITE from 192.168.1.45:5060

Thanks

Chaz

 

[Evolute IT]

I am getting this once we added a couple new phones. Our call comes into the Digital Receptionist, then when pressing 1 or 2 to go to 201 or 202, it pauses then says, "call transfer failed"

09/10/2019 3:42:48 PM - Call to T:Extn:201@[Dev:sip:[email protected]:5060] from L:15.1[Line:10000<<CHAULK,CHAZ ] failed, cause: Cause: 400 Bad Request/INVITE from 192.168.1.45:5060

Thanks

Chaz

Have you checked codecs? Are you using SBC, VPN or local phones?

What are the phones? And are you using the supported template & firmware?

This looks like the phone refuses the call for some reason.

 

[Chaz]

We are using the Fanvil X6, which we just got yesterday. Everything worked great on the Yealink phones. Both Fanvil phones are local. One of the Yealinks we have across the VPN works great.

 

[Evolute IT]

We are using the Fanvil X6, which we just got yesterday. Everything worked great on the Yealink phones. Both Fanvil phones are local. One of the Yealinks we have across the VPN works great.

Did you factory reset the phones and followed the guide at https://www.3cx.com/sip-phones/fanvil-x3-x5/ ?

Note that the X6 is only supported on HW version 1.2. Also, make sure you're using the supported firmware and template.

 

[Chaz]

The phones are on 1.10. That was done by my 3CX, not manually thru the phone.

System Information

Model:	X6
Hardware:	V1.3
Software:	1.10.8
Uptime:	00 : 34 : 58
MEMInfo:	ROM: 22.8/ 128(M) RAM: 61.2/97(M)

 

[Chaz]

Call comes in now and flashes my DN, but then hangs up when I try to answer it. APP is fine.

 

[Chaz]

Seems like it fails only on my cell number. Calling from another cell or landline, the calls go through.

 

[Chaz]

Ok. I dialed in *67 and it worked. So something is up my cell phone on 3CX.

 

[Evolute IT]

SIP trunk or gateway?

I would contact the provider and try to see if something is different when you call with your cellphone!

 

[JohnS_3CX]

Hi @Chaz

Care to provide some basic information like described here? https://www.3cx.com/community/threads/information-to-provide-when-requesting-help.67558/

 

[Chaz]

Some information about you system that is almost always useful is the following:

• 3CX Version, Enterprise latest s/w version.
• Server OS, Windows server 2008 R2
• Is the 3CX Server Hosted and where?
• IP Phone Make/Model/Firmware Yealink T29G
• Provisioning Method: Local
• Trunk Provider SIPTRUNK.COM
• Has the Firewall Checker passed:YES
• Are custom Phone Templates being used: YES

 

[JohnS_3CX]

Hi Chaz,

There's a number of variables that may be affecting you at the moment:

1. Please note that your OS is not supported or tested on our PBX version so consider upgrading your OS soon https://www.3cx.com/docs/manual/ or even using our Debian ISO which will not cost you anything compared to buying a new Windows license.

2. You did not state the exact PBX edition or phone firmware versions, so these are still unknown

3. You are using custom templates which have likely become outdated or may have changes affecting the transfers.

I recommend to remove the custom templates, and reprovision the phones using our:

• Latest 3CX supported firmware
• Latest 3CX default templates
• Latest 3CX PBX Edition 16.0.2.910

You need to minimize the number of factors that can cause the failures before troubleshooting further, to avoid chasing your own shadow. Please note that custom templates don't get updated when you receive 3CX updates and new firmware so they may break compatibility (ie the transfers dont work). If it works using our defaults and latest versions of PBX/Template/FW then you can at least isolate the issue somewhat. You can save your custom templates elsewhere and then compare what changes you made that may have caused the issue.