Pennytel, Buzz problem
Hi all,
I have a problem with pennytel, and I assume, but could you confirm, that its _only_ me? Firstly, I have not had this problem before and I have not changed any settings. The other thing is that if I register directly with pennytel (ie. no voxalot), I have a PAP2, then calls are fine. However, when I dial through voxalot, my end is silent and the receiving end hears a loud buzz. I have tried changing codecs, but all behave the same. I have also tried in the registered state and not registered state, both behave the same also. If it is a problem on my end, I'm not sure what to try next. I can make calls through other providers without any problem, I've been using sipme at the moment. Do you have any suggestions? Its frustrating, because I can make calls when not using voxalot, so it doesn't seem my end is the problem, but I get the feeling I'm the only one with this problem .. :( Cheers, Nathan. * I am register to the voxalot .au server |
Hi Nathan,
Can you try something. 1. Keep the preferred server as-is within VoXaLot 2. Change ATA to point to voxalot.com 3. Re-test and report back Thanks |
Another interesting thing I just noticed ... not sure if it is related (probably not).
If I dial directly to the FWD echo test throught voxalot -- the test is cut off just before the voice telling you that you are about to start the echo test finishes. HOWever, if I make the same call through voxalot-sipme (ie. voxalot sends to sipme sends to FWD) I get no such problem. Hmm, seems strange, I'm slowly running out of things to try... Nathan. |
What are your VoXaLot Codecs (on the web-page) for the FWD trunk?
FWD only accept g711 (in VoXaLot speak ulaw or alaw). |
Hi Martin,
Thank you! Your suggestion worked -- no more buzz!!! Preferred server is .au, but the PAP2 points to .com. Cheers, Nathan. ** should I leave the settings like this? |
Hi again,
Sorry, I think I confused you with directly to FWD, I mean through voxalot-sipbroker (*393613). I sill seem to be getting this problem, but the pennytel one is fixed -- thank you again. Cheers, Nathan. |
Quote:
As for FWD I am curious what NAT settings (if any) you have? Maybe you can PM or email me some screen dumps? |
Quote:
|
Quote:
Nothing has changed on the .au server in many weeks. For our own sanity checks, I just re-started the relevant .au processes. There should be no need to use .com as the code base is identical. Please report back. BTW - Is it just PenyyTel that is causing you grief? |
Quote:
Hi Martin, Thanks for your help. I still get the same problem when I change back to registering with '.au' (ie. silent on my end, buzz on receiving end). When I changed back again to '.com' it worked again. It seems to be _only_ pennytel, because I had been making calls via sipme when registered to '.au' with no problems. Let me know if there are anyother tests I can run on my end. Cheers, Nathan. |
Quote:
But, if I dial through sipme, there is no problem. For you info -- in case it's my setup --, I have setup a dial plan in voxalot to send numbers directly to sipme (ie. I dial #3*393613 -- #3 tells it to go to sipme). I use the FWD stun (stun.fwdnet.net). My wireless router handles NAT (Dlink DI-624+), I forward some ports in the 'virtual server' (5060/1) for the ATA, but other than that I have no special settings except to enable the NAT Keep Alive on the PAP2. It's funny, because I don't think I have had this problem before -- I have used the echo test several times without any problems. And, it works via sipme. It's not a big issue, but I'll keep trying on my end to see if I can fix it, unfortunately I don't know anyone on FWD to test call (other than echo). Are there any other specific NAT settings that may help figure out what's wrong? Cheers, Nathan. |
Quote:
i have not yet tried .com, but just thought i would let you know Martin. btw, to answer your question, yea it does appear that the issue is only occuring with Pennytel as Koala works completely fine out voxalot.com.au thanks for looking into this for us. |
Quote:
Nathan. |
Hi,
The Belgiums also noticed problems with their DIDs going to FWD: http://forum.sipbroker.com/showthrea...=2210#post2210 What happens when you dial *266300 instead? |
Quote:
Thanks, Nathan. |
Your problem is more than likely Codec then. While the monkies are playing check what Codec is being used.
Compare that against FWD. Last time I checked they only supportted g711 |
Quote:
Checked the codec - it is g711u via SIPME -- works via webcallback-SIPBroker -- works but not when I simply dial *393613 For all these three methods, the call settings that come up on the PAP2 are similar. Do you think it's at my end? I'm not particularly worried about it, but I am curious as to why this is happening. Thanks for the suggestions, Nathan. |
Hi Martin, is there any testing you want me to do? As I am still unable to make Pennytel calls through voxalot :(
Let me know if there is anything I can do to help. |
All times are GMT. The time now is 04:57 AM. |
Powered by vBulletin® Version 3.7.2
Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.