0

uaCSTA enabled after autoprovision - outbound call failure

Russell Bach

May 10, 2020 05:11

None

Follow

First time user of Yeastar IP PBX and am  setting up new S20 with Fanvil X5U and X6U handsets. Early on used default autoprovisioning fanvil  template after configuration wizard added sip trunk and added one extension to one handset. Changed inbound diversion from IVR to extension.  Tested inbound calls and outbound calls. These worked fine. Then updated S20 FW to 30.13.0.30 - reset desktop phone and re-autoprovisioned with default fanvil template. Outbound routing was default. Outbound calls gave "Internal error" Please hangup" on desk phone. Phone device log showed "Line not found".

Consulted support docs

https://support.yeastar.com/hc/en-us/articles/360011004693-Common-Causes-for-SIP-Outbound-Call-Failures

but nothing there that I could use to correct situation.

To debug reset PBX and desk phone  ran thru PBX configuration wizard and this time manually registered handset to PBX and calls outbound worked. Compared Xml phone configurations between working and non working setup and noticed that uaCSTA was not enabled in the working setp.

read further about setting up uaCSTA for Fanvil phones

https://help.yeastar.com/en/linkus_client/topic/how-to-enable-uacsta-feature-of-fanvil-ip-phones.html

seemed to be provisioned with the correct settings.

I gather uaCSTA would be necessary if  the Linkus client is used. In previous PBX GUI's there appeared to be a uaCSTA setting to enable/disable in General/Sip/Advanced - this doesn't seem to be there now? Currently have disabled uaCSTA on the desk phone menu.

Should I be able to use the uaCSTA enabled line to call out after autoprovisioning with default template? (seemed to work when I was on previous FW)?

Thanks for advice.

• Facebook
• Twitter
• LinkedIn

13 comments

• 0
  
  Larry Neblett May 10, 2020 11:38

  Hmmmm, I am not sure. 

   

  I looked at the latest release notes and saw this:

  SIP Relevant

  • For Yeastar S50, S100, and S300, added support for uaCSTA feature (PBX > General > SIP > Advanced > SIP > Enable uaCSTA connection).

    If the user wants to control the desk phone on Linkus Desktop Client by uaCSTA, you need to enable uaCSTA.

  If I understand you correctly, that the feature was there prior to the latest update, but is no longer to be found, then it seems that YS may have deprecated the function in the S20. If this is true, then this is pretty bad form on Yeastar's part to remove a feature with no explanation. 

  I do not know this to be the case, and can only suggest that a ticket be submitted. I would be interested in the outcome as I just sold a system Friday using S20 and Fanvil X6 and X4. 

   

• 0
  
  Larry Neblett May 10, 2020 13:00

  I subsequently downgraded an S20 to release 30.12.0.7 which was from December and I see nothing in the PBX that relates to uaCSTA. 

   

  What firmware was it that you saw the feature?

• 0
  
  Pixy Tse May 11, 2020 02:04

  Hi There,

  It's a hot issue for the new version, try to the solution:

  https://yeastar.zendesk.com/hc/en-us/articles/360047391594 

   

• 0
  
  Russell Bach May 11, 2020 07:37

  Can confirm that the newly available FW for Fanvil X5U and X6U (2.0.3) allows outgoing calls when using the  Yeastar  S20  (30.13.0.30) - thank you for addressing the issue promptly and pushing Fanvil for a FW upgrade. Making the download links available made the rectification easy.

• 0
  
  Pixy Tse May 11, 2020 10:47

  Yes, the Fanvil firmwares are tested.

• 0
  
  Russell Bach May 18, 2020 01:09

  Latest FW 30.13.0.34 14th May 2020 - has ability to change uaCSTA status via PBX rather than have to disable via Fanvil Phones. 

  Also the annoying "Upgrade failed" has been removed every time auto provisioning was done automatically ( every hr?) 

  Release notes 30.13.0.34

  Auto Provisioning

  • For Fanvil phones: Added support for enabling and disabling uaCSTA function.

  • Fixed the Auto Provisioning issue on Fanvil phones: Upgrading the phone firmware via Auto Provisioning would fail.

   

   

   

• 0
  
  Pixy Tse May 18, 2020 03:26

  Hi Ocular, yes it also fixes the issue of  "Upgrade failed". Or do you still experience the issue after upgrade?

• 0
  
  Russell Bach May 24, 2020 01:45

  Gone ahead and upgraded Yeastar FW to  30.13.0.34 , But Fanvil X5U and Fanvil X6U FW 2.0.3 - still experiencing "Upgrade Failed" after intitial autoprovisioning and about every hr after "downloading"

  Tested Fanvil X5U and Fanvil X6U ver 1 HW handsets

  From Phone webGUI - Auto provision Tab

  Static provisioning server- tftp://192.168.1.150

  Configuration File name 0c383e43fb85.cfg

  Protocol Type TFTP

  Update Interval 1Hr

  Update Mode Disabled (Tried changing upgrade mode to update at time interval- but still failed message on auto provisioning.

  If I force a "Auto Provision Now" --> Downloading --> Upgrade failed

  Not good form to have "Upgrade Failed" flash across the screen for 5 secs every Hr on clients 10 phones!

  Is there a way to progress this?

• 0
  
  Pixy Tse May 25, 2020 09:10

  Hi Ocular,

   

  Could you help get the logs of Fanvil Export log immediately after the issue happens again?

  Send it to helpdesk@yeastar.com. We would like to help check.

• 0
  
  Russell Bach May 31, 2020 22:31

  forwarded the device log from fanvil handset - log was left running for 24hrs after firmware upgrade. looks as though it cant find the fanvil.xml file and causes "upgrade failed" when auotprovisioning?

• 0
  
  Russell Bach June 01, 2020 07:19

  It would appear that if a contact is entered into the PBX phonebook the the problem is solved and the default contact update interval on the Fanvil is 720 mins.

  So 'Upgrade failed" occurs if the PBX contact list is empty. Looking at the logs it looks like the update process looks for a Fanvil.xml that isnt there. The solution appears to be - add  a contact to the Yeastar phonebook and the fanvil.xml file can then be found.

• 0
  
  Pixy Tse June 01, 2020 08:35

  Hi Ocular,

   

  Thanks for the update. After adding the contact like this? would it make sense?

   

  

• 0
  
  Pixy Tse June 04, 2020 12:36

  Russell Bach

  Try to refer to the solution about the Upgrade Failed issue: https://support.yeastar.com/hc/en-us/articles/360048870874