dslreports logo
site
 
    All Forums Hot Topics Gallery
spc

spacer




how-to block ads


Search Topic:
uniqs
726
share rss forum feed


benkandroid

@bell.ca

[Internet] Bell 15/10 with third party voip

I've had up and down time with third party voip on Bell 15/10. Half of the time, it wouldn't registered. I have no other issue with Bell internet. For past month, I've done tracert to VOIP's server (222.122.38.110) and found a routine. I would like to know what could be a possible problem.

IP phone registered when I have IP: 76.69.216.183, 76.69.216.45, 76.69.216.209, 76.69.219.133

IP phone failed to register when I have IP: 65.94.145.226, 65.92.105.240, 65.92.105.140, 65.94.147.28

I'm located in Montreal, and IP address with 76.69.**.** is my local. However, 65.94.**.** is 600 km away from where I am. I wonder why I get dynamic IP of Ontario CO. and How it is related to my IP phone problem. Thanks,


urbang33k

join:2010-02-13
Canada
kudos:1

interesting problem and great observations on your part.

Could it be possible that your voip provider could be blocking connections from 65.x.x.x ?



benkandroid

@bell.ca

I highly doubt it. I'm certain that there are more clients in 65.92.x.x or 65.94.x.x area than my area. I had no luck with Bell tech on this matter, as my internet is working properly. I also made a request to VOIP company to troubleshoot, but nothing so far.


kovy

join:2009-03-26
kudos:8
reply to benkandroid

Isn't there any traceroute test you can do ?



benkandroid

@bell.ca

Yes, I've done tracert multiple times, and it always get stuck at same place when it doesn't work (get stuck here 121.189.11.242). I've sent a request to verify that to the voip company. But why is my VOIP phone IP dependant? and why do I get Toronto IP from Bell when I'm in Montreal? Is it a regular thing?


InvalidError

join:2008-02-03
kudos:5

said by benkandroid :

and why do I get Toronto IP from Bell when I'm in Montreal? Is it a regular thing?

If you are saying this based on geolocation, you need to keep in mind that geolocation is just a dumb database that gets updated with whatever the ISP updates it to. When netblocks get shuffled around, the geolocation data does not necessarily get updated and sometimes people may get IPs that geolocate to a different province or even a different country because records have not been updated yet.

ISPs have no obligation to keep geolocation data up to date so I would not be surprised if most netblocks are simply located to wherever the ISP specified upon initial acquisition and never bothered updating beyond that.

Dunlop

join:2011-07-13
kudos:2
Reviews:
·Bell Fibe
·ELECTRONICBOX
reply to benkandroid

Checked my setup and currently have a 69.*.*.* IP. I'm in the Montreal area also. The log on the sagecomm does not go back far enough to tell me what other IP's I've had,sorry

I have 15/10 also,or rather 15/1.5 ; (

I use VOIP.ms and do not have any issues



benkandroid

@bell.ca
reply to InvalidError

Thanks, InvalidError for your explanation.
More I think of it, this VOIP problem has to be dealt with VOIP provider, not Bell internet.



Kim Jong Il

@bellmobilite.ca
reply to benkandroid

Why is your traffic routing through Korea, assuming this geolocation DB is accurate?

»iplocation.truevue.org/121.189.11.242.html