Mangowww.toao.net
join:2008-12-25
Alberta
kudos:11 Reviews:
 ·Anveo
 ·Shaw
·AcroVoice
·Callcentric
·callwithus
·voip.ms
·FreePhoneLine
 ·TELUS
| reply to mozerd
Re: [Voip.ms] Rings ongoing for long time Do the calls appear in the VoIP.ms CDR? If so, you can block them with Time Conditions and/or CallerID Filtering.
If they don't appear in the CDR, the symptoms are probably due to SIP scanners attempting to place calls through your device. This is especially likely since you have ports forwarded. Forwarding ports is actually bad practice - you shouldn't do that unless it won't work otherwise. One other thing you can do is change the UserAgentPort on the line that's having the problem to something other than 5060, and less than 65535.
m.
--
Dear Obihai, please fix the FXS to FXO Relay in the OBi110. Add this as your signature if you agree! |
Reviews:
 ·Verizon FiOS
·localphone.com
·callwithus
·voip.ms
·AT&T U-Verse
| We had been receiving mysterious inbound calls from 3 digit callerid numbers: 100 & 101. The router was not set on DMZ mode and there was no port forwarding. I wondered if these calls were coming in via the OBi network, but ultimately it didn't matter.
I have found the best way to prevent robot calls is to restrict which IP addresses that can connect to my OBi.
Voice Services -> ITSP Profile A -> SIP -> X_AccessList : voip.ms_ip_address
Then, only Voip.ms will be permitted in. One thing to watch out here: if a voip.ms server goes down, they might reroute calls via a different server. So you should add a comma-separated list of all the voip.ms server IP addresses for greatest reliability.
My current list:
209.62.1.2,74.54.54.178,67.215.241.250,74.63.41.218,78.129.153.20,67.205.74.164,174.137.63.206,69.147.236.82,68.233.226.97,64.120.22.242,174.34.146.162,174.142.75.171,174.137.63.206 |
 mozerdLight Will Pierce The DarknessPremium,MVM
join:2004-04-23
Nepean, ON | said by real_goose:I have found the best way to prevent robot calls is to restrict which IP addresses that can connect to my OBi.
Voice Services -> ITSP Profile A -> SIP -> X_AccessList : voip.ms_ip_address
Then, only Voip.ms will be permitted in. One thing to watch out here: if a voip.ms server goes down, they might reroute calls via a different server. So you should add a comma-separated list of all the voip.ms server IP addresses for greatest reliability. Excellent advice. Thank You.
--
David Mozer
IT-Expert on Call
Information Technology for Home and Business |
