voip.ms discussion

[Typhooon]

Originally Posted by tbusa

good question, I really didn't know until you asked, and I just placed a call to 1888rogers1 and it worked, In my asterisk box I still have an outbound route to VOIPms for all E911, grnvoip's 911' service I wasn't too sure about, so I figured I'd play it safe just in case.

Rogers Toll free number covers all North America. You need to call "Canada Only" toll free numbers to test it.

[Typhooon]

Originally Posted by FunkyTown

I use the Linksys SPA9000 mostly. I do have the Linksys SPA2102 too. I did have a problem once where I blocked my number with *67, but it really only blocked my name. The number still displayed. It seems to depend on the route the call chooses as voip.ms appears to use more than one company.

I also do not use the value route because I find the quality horrible when calling any number in Nova Scotia. Yet if I call someone in Ontario it's clear. I call Halifax often so I leave it on premium. Even premium gets a lot of jitter when calling Nova Scotia. Value is useless. I'm not sure why the quality is so crappy when calling Atlantic Canada.

I'm using the Montreal server.

Your issue with call block may have to do with the server you're on or the adapter you're using. What codec are you using? G711U is the best for sound but the worst for bandwidth. I use G711U so I'll get the best quality.

I am using G711u. Also, I'm on a Fiber network with ton of bandwidths...

With regards to CID block, I just noticed *67 prefix only blocks my name!? At least that's what it says under the caller ID column in the CDR page.

[FunkyTown]

That's not accurate. Even though you're seeing your number in the cdr, it doesn't mean the person you are calling can see it. Voip.ms always shows which one of your numbers placed the call whether it's blocked or not.

Call your mom with it blocked and ask her if it shows up.

In any case it sounds like you've got it working.

[dennism3]

What about?

"Our service works best for users with a static public IP address, and therefore is usually not ideal for home users with a NAT router."

I guess that's Ok for outbound, if I understand correctly.

[holymoly]

International dialing specifically to europe.

I have the value, and have tried 033 and unable to secure connection.

also tried 011 and 00


Interesting as 011 did work in past.

and yes I am skipping the internal europe long distance number (0)

[Typhooon]

Originally Posted by dennism3

What about?

"Our service works best for users with a static public IP address, and therefore is usually not ideal for home users with a NAT router."

I guess that's Ok for outbound, if I understand correctly.

Is that part of Voip.ms policy or sth?

[tbusa]

I thought that looked familiar but I wasn't sure what he was talking about, thats in the grnvoip faq /forum section.

But that's for another thread.


Anyone else noticed the new support ticket system ?

[Typhooon]

Originally Posted by tbusa

...Anyone else noticed the new support ticket system ?

I did notice it. Today, when I logged in, it kept telling me there were non-secure items in the webpage blah blah blah...then I realized it was because they had modified their portal.

[Typhooon]

So I switched to Premium routing which seems to have taken care of all my older issues. But now there's a new issue: incoming call won't always go through, getting either a busy tone or no answer!? This doesn't happen all the time but has happened enough for me to notice it.

The other issue is the failover feature. Why don't failed calls transfer to my cell (I have it set up that way)?

Have you guys noticed any voice quality improvement in inbound calls when using premium route?

[Mango]

What's your "Register expires" set to? Setting this to something low like 300 or even 150 solves incoming call problems for a lot of people. The default of 3600 is much too long.

(Post edited because I misread what Typhooon said.)

[Typhooon]

Originally Posted by Mango

What's your "Register expires" set to? Setting this to something low like 300 or even 150 solves incoming call problems for a lot of people. The default of 3600 is much too long.

Thanks for the advice. It's set to 3600. I will change it to 300 and see how it works.

Originally Posted by Mango

I do indeed notice an improvement with premium routing. That's all I use now. I used to use value routing but I decided it just wasn't worth the hassle. And, even with premium routing, it's still a great deal.

m.

So just to make sure I've understood you right, you have noticed improvement on incoming calls using the Premium route, right?

[Mango]

Ohhhh. Sorry; I misread your post. Premium/value routing only affects outgoing calls, not incoming. Routing is defined by the terminating carrier (the person who calls you) so there is no possible way to route a call any differently, once it has already arrived. I do not notice any difference on incoming calls when the account is configured for value or premium.

Think of it like an airport. If I go to Vancouver airport and buy a ticket for Toronto, they might tell me I have to make a stop in Calgary first. But I couldn't get to Toronto and have them tell me I should have stopped in Calgary on the way

[Typhooon]

Originally Posted by Mango

Ohhhh. Sorry; I misread your post. Premium/value routing only affects outgoing calls, not incoming. Routing is defined by the terminating carrier (the person who calls you) so there is no possible way to route a call any differently, once it has already arrived. I do not notice any difference on incoming calls when the account is configured for value or premium.

Think of it like an airport. If I go to Vancouver airport and buy a ticket for Toronto, they might tell me I have to make a stop in Calgary first. But I couldn't get to Toronto and have them tell me I should have stopped in Calgary on the way

Thanks for the clarification. That's what I always though too. The reason I asked this question was because inbound calls started to drop on me after I changed the settings to Premium route. I will change registration expiry time to 300 to see if it solves the issue.

The other problem that I had yesterday was with an inbound call where the other party could not hear me right. I thought the premium routing could fix it.

[Mango]

The premium route should theoretically not cause inbound calls to drop, but stranger things have happened I'm slightly concerned about the failover to cell not working as it should work whether your device is properly registered or not. Changing your registration expiry time to 300 is a good thing to do anyway, but if that does not solve the problem, put in a support ticket for VoIP.ms to look at it.

[Typhooon]

Originally Posted by Mango

The premium route should theoretically not cause inbound calls to drop, but stranger things have happened I'm slightly concerned about the failover to cell not working as it should work whether your device is properly registered or not. Changing your registration expiry time to 300 is a good thing to do anyway, but if that does not solve the problem, put in a support ticket for VoIP.ms to look at it.

I am looking at "Fruits of my Labor" blog right now. It's a neat blog man, good job.

I will change the RTP packet size (as suggested in your blog) to 0.01 to see if it improves the quality for incoming calls. I will also change the expiry time.

I'm still not sure how the failover is supposed to work. I disconnectd the PAP2 from the Internet, and then called my voip.ms line...got nothing!