Bell doesn't charge any dry loop fees. It's mainly the resellers (Like Acanac, TechSavvy, etc..) that do.

Just so I am clear, you processed a port request for your Bell # through Voip MS and it happened and you didn't loose your Bell DSL? in anyway? That sounds pretty easy. I am just scared that when they port my #, my DSL is at risk of getting shut off (by Bell).

If you have DSL on the Bell line and you port the number from that line.. YOU WILL lose DSL service!

This is because your DSL service needs a phone number as a circuit ID. Even Dry Loop lines have a phone number... you'll even get a dial tone if you connect a telephone set to the Dry line... you just can't call anyone.

You need to first get Bell to move your DSL over to a dry loop... this will be another pair of wires. Then you can go ahead and port the number from the line that has only phone service on it.

I know this is a fact as it happened to me. I have Bell Fibe25 and it works great... I then decided to move my remaining Bell line ($80 a month) over to VoIP.MS. I did the port request that took 7 days, it was seamless. At around midnight the Fibe25 quit working.. a call to Bell and they're telling me "Well sir... you ported your number away!" I like "well so what?" They then gave me a new number just for the DSL and it was up and running again within a few hours... which was good. It seems it was all taken care of at the CO end.

HI guys

can someone help me with my issue on LAN where i have two SPA box and four IP Phones and when incoming calls come...the four phones rings but whn answered the other phones have bounce calls...


Can someone confirm is it the UDP protocol and how can this be fixed..


Many thanks

What do you mean by "the other phones have bounce calls"?

"the other phones have bounce calls" meaning other extensions still rings after one extension has answered the call

How long do they keep ringing?

Keeps ringing unless u hang up all the Phonesl

That doesn't sound like a UDP issue. Sounds to me like either a misconfiguration of your caller group or your router, which may keep the server from sending the kill signal to your other caller group members when the call has been answered.

Thanks Gimli will re check ma configs...if nt will come back to u

I want to keep my current phone number from Bell and port it to voip.ms, but they tell me that "Basically, the only reason is that our underlying carriers do not offer support for the portability in that region." What does this means?
Is that a problem with Bell or voip.ms? Is that a problem with the phone number or the territory? I live in Ste-Therese, Quebec.

Let's say I transfer my current phone number to an address in Laval, which is supported (from Bell to Bell), will I be able to transfer it to voip.ms after?

Short answer to your request martincactus is yes. :D

Let's say I transfer my current phone number to an address in Laval, which is supported (from Bell to Bell), will I be able to transfer it to voip.ms after?

Short answer to your request martincactus is yes. :D

Porting availability depends upon a carrier's "presence" in a rate centre. A rate centre is a geographic area with boundaries that determine local calling and phone numbers that can be assigned to you. If VoIP.ms' carriers don't provide service in your rate centre, there's unfortunately nothing you can do. Even if Bell allowed you to use your number at an address outside your rate centre (which they almost certainly won't - another advantage of VoIP) the number's rate centre wouldn't change. So if VoIP.ms can't port your number, your options are:

1) Order a new number from VoIP.ms, in a rate centre that is a local call from your rate centre.
2) Use a different service provider.
3) Wait for one of VoIP.ms' carriers to offer service in your rate centre.

m.