Oh, I'm sorry about that. The phone we are testing with right now is on version 2.72.0.25
Thanks for all your help.
(03-19-2014 02:41 PM)Yealink Support Wrote: [ -> ]Sorry. Please press OK button and you can see the firmware of your T28. Please tell me the version of your T28 now. Is it a custom version?
(03-14-2014 09:58 PM)newins Wrote: [ -> ]A bit more information. It seems to work fine using RFC283 but the phone has to be muted. Otherwise it will send double digits.
It should be a strange SIP message in this issue. Can you send me the
pcap trace file for debug?
How to Get the Correct Syslog, Config.bin and Trace
Here is the pcap file. He said he had to try it about 10 times to get the issue to happen this time. I think it was the 9th or 10th call it happened on.
(03-20-2014 02:19 PM)Yealink Support Wrote: [ -> ] (03-14-2014 09:58 PM)newins Wrote: [ -> ]A bit more information. It seems to work fine using RFC283 but the phone has to be muted. Otherwise it will send double digits.
It should be a strange SIP message in this issue. Can you send me the pcap trace file for debug?
How to Get the Correct Syslog, Config.bin and Trace
Sorry. We can't get enough information for your pcap file.
1. So your issue happens randomly. Does this issue happen in some regular server?
2. Do you test with other DTMF type and DTMF Payload Type(96~127)? We do use the standand of RFC2833.
Thank you for all of your help on this. Seems like the customer was only having the problem with one particular number.
I know it is off topic but I have sent several emails to sales@yealink.com and have not heard anything. Our company sells Yealink as the primary handset, is there anyway we could get access to the Zero Touch provisioning? This would be a tremendous help for us.
Thanks!
(03-24-2014 10:52 AM)Yealink Support Wrote: [ -> ]Sorry. We can't get enough information for your pcap file.
1. So your issue happens randomly. Does this issue happen in some regular server?
2. Do you test with other DTMF type and DTMF Payload Type(96~127)? We do use the standand of RFC2833.
We do support Zero Touch Provsioning. You can enable "Zero Active" via webpage or auto provisioning.
-----------------------------------------------------------------
#!version:1.0.0.1
#######################################################################################
## Zero Touch ##
#######################################################################################
#Enable or disable the Zero Touch feature; 0-Disabled (default), 1-Enabled;
zero_touch.enable =
#Configure the waiting time (in seconds) before canceling the Zero Touch. It ranges from 0 to 100, the default value is 5.
zero_touch.wait_time =
-----------------------------------------------------------------
Right now we don't have access to the Zero Touch portal. Is there someone that I need to speak to to ask for access to the portal?
Right now we don't have access to Zero Touch but could use it greatly. We have several handsets we are about to deploy and could use this very much.
Thank you for your help.
(05-03-2014 04:58 PM)Yealink Support Wrote: [ -> ]We do support Zero Touch Provsioning. You can enable "Zero Active" via webpage or auto provisioning.
-----------------------------------------------------------------
#!version:1.0.0.1
#######################################################################################
## Zero Touch ##
#######################################################################################
#Enable or disable the Zero Touch feature; 0-Disabled (default), 1-Enabled;
zero_touch.enable =
#Configure the waiting time (in seconds) before canceling the Zero Touch. It ranges from 0 to 100, the default value is 5.
zero_touch.wait_time =
-----------------------------------------------------------------