voip.ms discussion - Page 22 - Canadian TV, Computing and Home Theatre Forums

FunkyTown · 2009-05-16, 11:08 AM

Well I have contacted support and they said they haven't changed anything on their end at voip.ms.

I've tried switching servers. I'm on the Toronto one now. Let's see how reliable that one is.

Mango · 2009-05-16, 11:27 AM

Wysiwyg: I heard a rumor that Eastern Canada ports are faster than Western Canada ports. Hopefully this is the case for you. Keep in touch with them and be sure they are aware of this date.

99semaj: There are two ways of communicating via SIP URI. One is internally on your network, between the phones in your house, and the other is externally via a SIP URI that you set up on the VoIP.ms website.

The easiest/cheapest way to receive calls from the Internet via SIP URI is to create an Internal Extension on the Edit Sub Account page. Once you're done, the SIP URI will appear on the Manage Sub Account page.

Does this answer your question? If not, there are many ways to use SIP URIs and if you explain a bit more about what you want to do, I'm sure someone here will be able to help you out.

m.

99semaj · 2009-05-17, 12:28 AM

I guess I just don't understand how the SIP URI's should work.

I thought that I should be able to call internally between my IP phones by using IP addresses. i.e. call directly to an extension using the SIP URI listed in the Manage Sub-Account screen. Doesn't work.

Alternately, I thought I could use the SIP URI's screen to create a SIP address that would ring the entire DID.

Can't get it working, though.

Mango · 2009-05-17, 12:30 AM

If you want to call internally between your IP phones on your private network, try [VoIP.ms username]@[internal IP address]. This works for Linksys devices; I imagine it would also work with Aastra ones. The advantage to this technique is that there is less latency than if you use the VoIP.ms SIP URIs.

Note that for Linksys devices, you must enable the "Allow IP Dialing" setting. A similar setting may exist on your phones.

Does that help? What you're trying should work, though this may be a better workaround.

m.

mlord · 2009-05-20, 09:23 PM

I have had several reports now, both from callers and callees, that they hear "tones" periodically during calls with me (I use voip.ms).

Like, "touch tones", or "call progress tones", while we are speaking, every few minutes.

I don't hear them at this end. So I suspect perhaps our PAP2T is doing it, but I don't know which possible config option might be causing that.

Any ideas?

abcezas123 · 2009-05-21, 03:20 PM

Same here. I hear it when I call from my cell into my DID at home. Mix of analog phones connected via a spa3102.

holymoly · 2009-05-22, 12:11 PM

Tones could indicate a call waiting. I get more of a beep. Is that it?

mlord · 2009-05-22, 02:43 PM

Quote:

Originally Posted by holymoly

Tones could indicate a call waiting. I get more of a beep. Is that it?

No, the party on the other end does not have that feature. Remember, it's others who hear it, not me the voip.ms user.

I tried it today -- called home from another line. It's kind of a flat tone sound, once in a while during the conversation.

Peculiar.

profets · 2009-05-25, 05:29 PM

thought i'd post an update.. I made a request to port my # from teksavvy to voip.ms on may13. i've had several email updates during the past week and received an FOC for May 25. Just a little while ago the pots line at home stopped working. when i have a minute I gotta setup my pap2t and see how it works.
Less than 2 weeks for the whole port, not bad.

wysiwyg · 2009-05-25, 05:45 PM

Thanks for sharing this. I'm still waiting for my FOC date. I need to terminate the line by June 26th, so I just hope it happens before that as I don't know how much time to gve Bell to cancel a line if the port did not occur yet.

It's only been a week since it was submitted to Bell, so it's still good.

Is there a way to tell if Bell received it? Would calling 310BELL help? I know their phone CS is terrible.

tbusa · 2009-05-25, 08:53 PM

I have ported about 10 bell lines and all took around 13-18 days, I didn't get the FOC date until the last day of the all the ports.

They must be bleeding DID's like crazy

profets · 2009-05-26, 06:29 AM

^lol...

a year ago i was with bell and ported to teksavvy. took a few weeks that time.

apn · 2009-05-26, 08:54 AM

@wysiwyg: Per my upstream comments, the port to voip.ms can be frustrating.

Even though you technically don't need to speak to the telco you're leaving, I found it worthwhile because there's still a lot of blind waiting for the LNP request to complete. You're basically in limbo once voip.ms has sent the request to your carrier.

You can call Bell to ask if they've received the port request (I had to do this w/ Rogers), however, just be prepared to be 'talked-to' by the retentions department

In my case, Rogers confirmed they'd not received anything (this after voip.ms said they'd sent it weeks earlier), so I had to kick voip.ms in the pants to re-submit and expedite the request.

Check everything!, as an old Manager once told me, You get what you inspect, not what you expect

PS: After some initial glitches and adjusting my NAT settings, my service has worked flawlessly. My In-Laws just completed a port from Bell last Friday, and another relative is bugging me to help him escape Rogers.

wysiwyg · 2009-05-26, 09:54 AM

Thanks everyone. I'm still well within the timeline for a porting request, so if in 1-2 weeks, there's still no action, I might start to call Bell to check. I'm really looking forward to begin using voip.ms as my primary line :-)

APN, how long did your relative's port request take from the time it was submitted to Bell?

apn · 2009-05-26, 10:53 AM

Quote:

APN, how long did your relative's port request take from the time it was submitted to Bell?

20 days start to finish: requested Saturday May 2nd, ported Friday May 22nd

2009-05-16, 11:27 AM	#317
Mango Join Date: Nov 2008 Location: Alberta Posts: 796	Wysiwyg: I heard a rumor that Eastern Canada ports are faster than Western Canada ports. Hopefully this is the case for you. Keep in touch with them and be sure they are aware of this date. 99semaj: There are two ways of communicating via SIP URI. One is internally on your network, between the phones in your house, and the other is externally via a SIP URI that you set up on the VoIP.ms website. The easiest/cheapest way to receive calls from the Internet via SIP URI is to create an Internal Extension on the Edit Sub Account page. Once you're done, the SIP URI will appear on the Manage Sub Account page. Does this answer your question? If not, there are many ways to use SIP URIs and if you explain a bit more about what you want to do, I'm sure someone here will be able to help you out. m. __________________ Mango's dial plan for an OBi ATA

2009-05-17, 12:30 AM	#319
Mango Join Date: Nov 2008 Location: Alberta Posts: 796	If you want to call internally between your IP phones on your private network, try [VoIP.ms username]@[internal IP address]. This works for Linksys devices; I imagine it would also work with Aastra ones. The advantage to this technique is that there is less latency than if you use the VoIP.ms SIP URIs. Note that for Linksys devices, you must enable the "Allow IP Dialing" setting. A similar setting may exist on your phones. Does that help? What you're trying should work, though this may be a better workaround. m. __________________ Mango's dial plan for an OBi ATA

2009-05-20, 09:23 PM	#320
mlord Veteran Join Date: Nov 2006 Posts: 1,545	Tones heard at the other end ??? I have had several reports now, both from callers and callees, that they hear "tones" periodically during calls with me (I use voip.ms). Like, "touch tones", or "call progress tones", while we are speaking, every few minutes. I don't hear them at this end. So I suspect perhaps our PAP2T is doing it, but I don't know which possible config option might be causing that. Any ideas?

Thread Tools	Search this Thread
Show Printable Version Email this Page	Search this Thread: Advanced Search
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

2009-05-16, 11:08 AM	#316
FunkyTown Join Date: May 2006 Location: Gatineau, QC Posts: 1,158	Well I have contacted support and they said they haven't changed anything on their end at voip.ms. I've tried switching servers. I'm on the Toronto one now. Let's see how reliable that one is.

2009-05-17, 12:28 AM	#318
99semaj Veteran Join Date: Jun 2007 Location: /dev/null Posts: 2,664	I guess I just don't understand how the SIP URI's should work. I thought that I should be able to call internally between my IP phones by using IP addresses. i.e. call directly to an extension using the SIP URI listed in the Manage Sub-Account screen. Doesn't work. Alternately, I thought I could use the SIP URI's screen to create a SIP address that would ring the entire DID. Can't get it working, though.

2009-05-21, 03:20 PM	#321
abcezas123 Rookie Join Date: Apr 2009 Posts: 11	Same here. I hear it when I call from my cell into my DID at home. Mix of analog phones connected via a spa3102.

2009-05-22, 12:11 PM	#322
holymoly Join Date: Apr 2005 Location: Mississauga, Ontario Posts: 179	Tones could indicate a call waiting. I get more of a beep. Is that it?

2009-05-25, 05:29 PM	#324
profets Join Date: Jan 2007 Location: Ontario Posts: 763	thought i'd post an update.. I made a request to port my # from teksavvy to voip.ms on may13. i've had several email updates during the past week and received an FOC for May 25. Just a little while ago the pots line at home stopped working. when i have a minute I gotta setup my pap2t and see how it works. Less than 2 weeks for the whole port, not bad.

2009-05-25, 05:45 PM	#325
wysiwyg Join Date: May 2002 Location: Toronto - Davisville Subway Posts: 908	Thanks for sharing this. I'm still waiting for my FOC date. I need to terminate the line by June 26th, so I just hope it happens before that as I don't know how much time to gve Bell to cancel a line if the port did not occur yet. It's only been a week since it was submitted to Bell, so it's still good. Is there a way to tell if Bell received it? Would calling 310BELL help? I know their phone CS is terrible.

2009-05-25, 08:53 PM	#326
tbusa Join Date: Jan 2007 Location: Oshawa Posts: 175	I have ported about 10 bell lines and all took around 13-18 days, I didn't get the FOC date until the last day of the all the ports. They must be bleeding DID's like crazy

2009-05-26, 06:29 AM	#327
profets Join Date: Jan 2007 Location: Ontario Posts: 763	^lol... a year ago i was with bell and ported to teksavvy. took a few weeks that time.

2009-05-26, 08:54 AM	#328
apn Join Date: Jul 2007 Posts: 569	@wysiwyg: Per my upstream comments, the port to voip.ms can be frustrating. Even though you technically don't need to speak to the telco you're leaving, I found it worthwhile because there's still a lot of blind waiting for the LNP request to complete. You're basically in limbo once voip.ms has sent the request to your carrier. You can call Bell to ask if they've received the port request (I had to do this w/ Rogers), however, just be prepared to be 'talked-to' by the retentions department In my case, Rogers confirmed they'd not received anything (this after voip.ms said they'd sent it weeks earlier), so I had to kick voip.ms in the pants to re-submit and expedite the request. Check everything!, as an old Manager once told me, You get what you inspect, not what you expect PS: After some initial glitches and adjusting my NAT settings, my service has worked flawlessly. My In-Laws just completed a port from Bell last Friday, and another relative is bugging me to help him escape Rogers.

2009-05-26, 09:54 AM	#329
wysiwyg Join Date: May 2002 Location: Toronto - Davisville Subway Posts: 908	Thanks everyone. I'm still well within the timeline for a porting request, so if in 1-2 weeks, there's still no action, I might start to call Bell to check. I'm really looking forward to begin using voip.ms as my primary line :-) APN, how long did your relative's port request take from the time it was submitted to Bell?