|
[Voip.ms] Inbound callers to me getting "this is long distance cgetting emails as people cannot call me.
a message saying 'this is a long distance call" and are calling from different area code and long distance. |
actions · 2012-Dec-15 2:47 pm · (locked) |
|
Re: [Voip.ms] Inbound callers to me getting "this is long dWhat does Voip.MS tech support say?
What server are you on? |
actions · 2012-Dec-15 3:45 pm · (locked) |
|
I'm on Houston server.
What's happening, I see in CDRs the calls are being forwarded to an 800 number, for some reason.
Support says to dial *73 to disable any call fwd feature, and they tried calling me, and it only rang once. Same thing happened on thursday. CDR still shows a call fwd. |
actions · 2012-Dec-15 3:57 pm · (locked) |
Trimline Premium Member join:2004-10-24 Windermere, FL |
Trimline
Premium Member
2012-Dec-15 4:41 pm
From the main panel, make sure you do not have any Call Forwarding rules and also check your Time Conditions. |
actions · 2012-Dec-15 4:41 pm · (locked) |
|
No call fwd rules and no time conditions |
actions · 2012-Dec-15 5:22 pm · (locked) |
hockeynomad |
the CDRs show it forwards to 1-800-555-1111 a Bell Canada calling card number.
This is bizarre. |
actions · 2012-Dec-15 5:52 pm · (locked) |
j1349705 Premium Member join:2006-04-15 Holly Springs, NC |
j1349705
Premium Member
2012-Dec-15 6:10 pm
said by hockeynomad:the CDRs show it forwards to 1-800-555-1111 a Bell Canada calling card number.
This is bizarre. A few things to try... Set your DID to go to voicemail or an echo test. See if the problems still occurs. If so, then the issue would be with VoIP.ms which is unlikely since nobody else is reporting similar issues. If this fixes the problem, factory default your ATA or IP phone and re-configure it from scratch. Do not back up and restore the configuration. You could also check the configuration and see if there is anything odd set up, but a factory default would guarantee that all settings are wiped out. |
actions · 2012-Dec-15 6:10 pm · (locked) |
2 edits |
thanks, waiting for a new reply from voip.ms support. waiting, waiting, waiting.... |
actions · 2012-Dec-15 6:14 pm · (locked) |
MartinMVoIP.ms Premium Member join:2008-07-21 |
to hockeynomad
I traced by your account with the number you provided. When placing the DID on echo test as suggestest on previous post by JIMK.
Echo test is reached properly. I traced with wireshark and I see that your device is sending back a "302 Moved temporarily packet". This looks like a forward from your device, however we'll investigate further to make sure we give you the appropriate answer. One sure thing is that the DID is fine. |
actions · 2012-Dec-15 7:22 pm · (locked) |
|
thanks for responding personally, Martin.
A factory reset of VOIP adapter advisable? |
actions · 2012-Dec-15 7:49 pm · (locked) |
hockeynomad |
OK, finally able to access the adapter web interface, and on user tab, there was the 800 number call forward.
Beats me how that got in there, haven't looked at the User tab in months.
that should fix. |
actions · 2012-Dec-15 7:55 pm · (locked) |
|
said by hockeynomad:OK, finally able to access the adapter web interface, and on user tab, there was the 800 number call forward.
Beats me how that got in there.... Truly bizarre. Anybody else that has access to the device? And are you sure it was not hacked? Check your security. Are you behind a router with at least a NAT firewall? |
actions · 2012-Dec-15 8:51 pm · (locked) |
PX Eliezer704 |
to MartinM
said by MartinM:This looks like a forward from your device, however we'll investigate further to make sure we give you the appropriate answer. One sure thing is that the DID is fine. Nice work. |
actions · 2012-Dec-15 8:52 pm · (locked) |
MangoUse DMZ and you get a kick in the dick. Premium Member join:2008-12-25 www.toao.net |
Mango
Premium Member
2012-Dec-15 9:08 pm
My bet is someone dialed the Cfwd All Act Code. |
actions · 2012-Dec-15 9:08 pm · (locked) |
|
said by Mango:My bet is someone dialed the Cfwd All Act Code. Hmmm. But when he dialed *73 which should have cancelled, it didn't help. |
actions · 2012-Dec-15 9:31 pm · (locked) |
MangoUse DMZ and you get a kick in the dick. Premium Member join:2008-12-25 www.toao.net |
Mango
Premium Member
2012-Dec-15 9:33 pm
Ahh, I missed that. Thanks. |
actions · 2012-Dec-15 9:33 pm · (locked) |
·Fido MikroTik RB750Gr3 MikroTik wAP AC Panasonic KX-TGP500
1 recommendation |
to PX Eliezer704
said by PX Eliezer704:said by Mango:My bet is someone dialed the Cfwd All Act Code. Hmmm. But when he dialed *73 which should have cancelled, it didn't help. You are assuming that Cfwd All Deact Code is still set to *73, it might not be. |
actions · 2012-Dec-16 12:17 am · (locked) |
|
Still leave us the problem of how the [Cfwd All Act Code] was activated, IF that was the case.... |
actions · 2012-Dec-16 12:28 am · (locked) |
j1349705 Premium Member join:2006-04-15 Holly Springs, NC |
j1349705
Premium Member
2012-Dec-16 2:40 pm
said by PX Eliezer704:Still leave us the problem of how the [Cfwd All Act Code] was activated, IF that was the case.... Good point... I hope the ATA is behind a firewall or NAT device without any ports forwarded, and that the default password has changed. Somebody may have found it with a port scanner and started to mess with it, possibly to see if it was open for abuse (such as the famous fraudulent long distance calls to some expensive international destination). I bring this up because some a common troubleshooting step is to allow all incoming traffic to the ATA during troubleshooting... and it wouldn't be hard to forget to secure it again after troubleshooting is complete. |
actions · 2012-Dec-16 2:40 pm · (locked) |
|
Spoke to a friend and he mentioned maybe need a password for web interface.
I just log in with "Admin" |
actions · 2012-Dec-16 6:20 pm · (locked) |
|
You need:
1) A strong password on your ATA.
2) Your ATA behind a router with some firewall protection.
3) That you do NOT use the router's DMZ setting for the ATA.
4) That you do NOT forward ports on the router unless absolutely necessary for your VoIP service to work. |
actions · 2012-Dec-16 6:52 pm · (locked) |
|
said by PX Eliezer704:You need:
1) A strong password on your ATA. OK
2) Your ATA behind a router with some firewall protection. How?
3) That you do NOT use the router's DMZ setting for the ATA. Don't know what you mean
4) That you do NOT forward ports on the router unless absolutely necessary for your VoIP service to work. How to know? |
actions · 2012-Dec-16 7:00 pm · (locked) |
|
to hockeynomad
I hope some now agree that voip.ms is not reliable for incoming calls. Period and it does not seem like they care. Just going through the motions of responding to tickets and acting like your case is unique. I can tell you from experience with numerous voip.ms lines, they are not reliable for incoming calls. Period. Sorry to fans of voip.ms, but they are simply not reliable and I can't recommend them anymore. |
actions · 2012-Dec-17 9:57 am · (locked) |
j1349705 Premium Member join:2006-04-15 Holly Springs, NC |
j1349705
Premium Member
2012-Dec-17 10:11 am
said by pauleyisle :I hope some now agree that voip.ms is not reliable for incoming calls. Period and it does not seem like they care. Just going through the motions of responding to tickets and acting like your case is unique. I can tell you from experience with numerous voip.ms lines, they are not reliable for incoming calls. Period. Sorry to fans of voip.ms, but they are simply not reliable and I can't recommend them anymore. If you had actually read this thread, you would have realized that the problem was with the ATA and had nothing to do with the service provider. |
actions · 2012-Dec-17 10:11 am · (locked) |
|
your moderator at work
hidden :
|