(09-14-2020 09:31 PM)tjwesto Wrote: (09-14-2020 08:53 PM)complex1 Wrote: (09-14-2020 05:56 PM)tjwesto Wrote: I've got 4 x W56H handsets with a W60B at home connected to the Sipgate VoIP service.
When someone calls me and I answer, the caller hears an audible "beep" followed a split second later by two more "beeps" and then we can hear each other. This means that during the first couple of seconds the caller cannot hear me. This is also true when I don't answer and the call diverts to the Sipgate voicemail service. Again, the caller hears those beeps at the start of the playback of my message.
Not too sure what's happening here and whether this issue relates to the Yealink phones or the Sipgate service.
In terms of configuration the W60B sits behind my router which has NAT enabled, but I've forwarded the SIP and NAT ports.
It seems strange that the caller can hear these audible tones before we can hear each other.
Any suggestions would be gratefully received.
Thanks in advance.
Tim
Hi Tim,
I think the problem is with Sipgate as the caller also hears the 3 beeps when the call is forwarded to voicemail.
I assume that the W60B not forward the call to voicemail, but the provider Sipgate does.
Hi Frank,
I have also thought that the issue might be on the Sipgate side. As another test I did set the account to switch immediately to voicemail without ringing. In this scenario the caller doesn't hear any beeps.
Not sure if that provides anymore clues? So basically the beeps are only heard when I answer a call or voicemail switches in after 30 secs of ringing. I'm not familiar with how switching to voicemail occurs, but I presume that is a Sipgate function as opposed to the W60B.
Their support tech. initially suggested that some NAT translation errors might cause problems but I've now port forwarded to rule that out and the symptoms remain identical. The fact that audible beeps/tones are generated suggest they must be generated by some hardware in the path I presume?
Cheers
Tim
Hello again Frank!
Sipgate have just emailed me to confirm that multiple users are seeing (or hearing!) the same issue. Consequently, they are investigating their network to track it down.
Thanks for your input.
Cheers
Tim
