Yealink Forums

Full Version: TCP + Call Park DSSKey Failure
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
Hello,

** originally I believed this was just related to the new T-29G, but it appears to be on any phone running v73 **

I am testing out the new T-29G, and ran into an issue when using our existing T-2x config files in combination with TCP as the SIP transport.

Initially, the phone registers and makes a call just fine, but after the following scenario, the phone looses the ability to make any further calls or register with our server.

  1. Call From T-29G to extension
  2. Use Call Park DSS key "700" to park the call
  3. Use Call Park DSS Key "701" to retrieve call
  4. Call to 701 is attempted, but never completes
  5. Account goes unregistered, and BLF's unsubscribe
  6. Only a reboot will bring the account back online *edit Re-saving the account details in the web interface also gets the phone re-registered.


I have attached the pcap and syslog (level 6) gathered from the phone. So far, using the Call Park function seems to be the only thing that causes this. Repeated direct calls\transfers do not have any problems.
Dear Nelson,

Thanks for reporting this issue.
Would you please also send the config.bin and record pcap and syslog(6) in pairs and then send it to support@yealink.com. We will report to RD for further analyze.

Regards
Elaine
I will get this sent out today for you, thanks for the response!
Reference URL's