Printable View
On some of my calls I am getting horrible static. I know it is digital, but it sounds like back in POTS days when water was in the line or a wire was loose. I just called my DID and I couldn't even make out the voice.
Edit: It happens on the ring-in, so when you call my DID you can hear the "static" even before someone answers.
Edit 2: It doesn't happen every time. Sometimes it is inbound and sometimes outbound. Kind of strange.
Local Sip port for FXS2 showed 5062. FXS1 shows 5079. Should I change them both?
Nope, they should be different ports for the different lines.Quote:
Originally Posted by Vumes
Try it now though, we just enabled both ports on our end so they should work.
My sip ports are
port1=5079
port2=5062
Been this way all along with no problems till yesterday's registration dropping out..
So far so good. Anyone else wanting to help test this...here is the info:
----
1) Login to ATA with admin password. Temporary: Ajw5q1FexW8u8XuL
2) Disable provisioning temporarily by removing the Config Server Path under Advanced Settings.
3) Under FSX Port 1, change your server to central02.voipwelcome.com
4) Under FSX Port 2, change your server to central02.voipwelcome.com AND add a B to the end of your username/auth username. Example: 2816172000 would change to 2816172000B
5) Reboot and see if you can find any issues.
After Testing/Reverting to Normal:
If you need to revert, just re-enable provisioning by changing Config Server Path back to provision.dev.voipo.com and rebooting. It should reconfigure as it was before.
----
Those are the default Local sip port settings for HT502 provisioned by VoiPo. I got mined changed to the HT502 factory default per belowQuote:
Originally Posted by burris
Port1=5060
Port2=5062
I've had my ports changed in the past and so long as they weren't the same, they workedQuote:
Originally Posted by myvoip07
What is everyone seeing so far?
There are dozens of you on it, so hopefully the bulk of you being quiet is a good thing :)
Tim, on FXS2 should my proxy server be central02 as well, or leave it as sip, or blank?
Should be central02.Quote:
Originally Posted by Vumes
Quote:
Originally Posted by Vumes
central02.voipwelcome.com
ah Tim beat me to it :).
________
Geo/chevrolet tracker
Ok, thats what I thought. I still have a no go. Want to take a look at my device? If it doesn't work out, i'll just revert back, but just wondering why it won't work out.
Everything looks OK except for the horrible static on my incoming calls. Maybe it is something with my DID or something.
I saw both of your lines registered a second ago, any chance you have done some changes? Could you go ahead and power-cycle, the ATA while I'm grabbing a network trace on your account, thanks!Quote:
Originally Posted by Vumes
They were both registered because I reverted back and provisioned, then tried all over again. Power cycling now.
My Incoming calls disconnect after 30 secs, Outgoing fine
After being able to get in and make the changes I seem to be staying connected now - System Up Time: 21:48:45 up 5 min - first time that has shown more than 0 all day. Incoming and outgoing calls seem to be working fine after a couple test calls.
Odd, I was seeing them connected to the central02 server. Lets see how it goes this time.Quote:
Originally Posted by Vumes
Correction I set mine as directed to test it and port 2 just gives me a fast busy. Both say they registered.
So how do we know when to change the provisioning back?
Could you PM me your phone number, if you want to check a few last settings to make sure it is alright, otherwise whenever you are ready to revert feel free.Quote:
Originally Posted by Xponder1
Also, what action gives you fast busy? Incoming Call, outgoing Call? etc?
________
MONTANA MARIJUANA DISPENSARY
Sent. Port 1 I tested in and out both for 2 mins and they were fine.
Outbound calls and inbound did not work to the second port.Quote:
Originally Posted by VOIPoBrandon
I tested by calling my cell phone then using my wifes phone to call the house.
Was port 2 set to central02 too?Quote:
Originally Posted by Xponder1
Yes I just checked and made sure.Quote:
Originally Posted by VOIPoTim
I also get fast busy with outgoing calls on port 2.
EDIT: When I dial 11 digits it works. Dialing 7 digits on port 2 gives fast busy.
As Brandon requested I tried a 1 800 number and it had the same issue and I called my cell XXX -XXXX and it had the problem. After reading your comment I tried dialing my cell with the area code and it worked fine.Quote:
Originally Posted by scott2020
My static problem is pretty bad. I only can call from my cell phone. Other calls to other numbers from my cell are fine. It is static from the beginning of the ring in all the way to voicemail. Voicemail is all static as well. It is so loud I can't communicate. It seems to be only inbound calls right now. Also, my virtual number seems to be clear, so maybe it is something with my Level 3 DID here in MO.
I noticed port one has nothing in the outbound proxy field but port two has sip.voipwelcome.com
Does that matter?
Take out the sip.voipwelcome.com one.Quote:
Originally Posted by Xponder1
Removed and rebooted same issue.Quote:
Originally Posted by VOIPoTim
So this is only 7 digits and 800 number?Quote:
Originally Posted by Xponder1
Is this only on line 2 and they work fine on line 1?
100% correct. Line 1 is fine.Quote:
Originally Posted by VOIPoTim
Same here. Port 1 I can dial 7 digits and the call works. Port 2 I cannot dial 7 digits but 11 digit dialing works.
Alright guys, give the 7 digits a go -- and hold on the 800 numbers, due to the new registration on FXS2, we have to make some modifications to adjust. Please stand by.
________
Teen Vids
7 digits worked for me just now on port 2.
I tested and it worked fine. I did not read this until after I sent you the private message but I did test the 800 number you provided me and it worked fine.Quote:
Originally Posted by VOIPoBrandon
Incoming and outgoing are both working.
Anything else anyone finding?
Tried some more numbers including another 800# and all seem fine.Quote:
Originally Posted by VOIPoTim
One more thing for you guys testing this...
Set "Unregister On Reboot" to Yes for both lines.
Done and tested to confirm still working fine. ;)Quote:
Originally Posted by VOIPoTim