OBiTALK Community

General Support => Installation and Set-Up (Devices) => Topic started by: Tack on July 28, 2011, 12:24:49 PM

Title: Problem Adding VOIP.MS
Post by: Tack on July 28, 2011, 12:24:49 PM
I have wanted to add VOIP.MS on SP2 (Google Voice is on SP1), so I went to the ObTalk page, clicked the Obi110 number, which brought up a page allowing the SP2 account to be entered.  I chose VOIP.MS from the dropdown and entered account data.

Now, it's still unconnected, and the data for VOIP set-up has not be transfered to the Obi110, as I can see by pulling up its own configuration page, which shows no SP2 account information has been entered.

I was under the impression that this occurred by some script.  Does the VOIP.MS info have to be entered into Obi110 annually?

Appreciate the assistance, as always.
 
Title: Re: Problem Adding VOIP.MS
Post by: RonR on July 28, 2011, 12:39:59 PM
You have to configure the OBi via the OBiTALK Web Portal or locally through the OBi itself, but not both.

To configure the OBi locally, you must disable Auto Provisioning to prevent the OBiTALK Web Portal from overwriting your local settings every time you reboot.

To configure the OBi from the OBiTALK Web Portal, you must have Auto Provisioning enabled.

The OBiTALK Web Portal is not smart enough to leave your locally changed settings alone.  It the OBiTALK Web Portal hasn't been updated with the changes you've made locally, enabling Auto Provisioning will allow the OBiTALK Web Portal to overwrite them.

If you've been making changes to the OBi locally with Auto Provisioning disabled, you should backup your OBi configuration and import that file to the OBiTALK Web Portal before enabling Auto Provisioning if you want the changes you've made locally to be preserved.
Title: Re: Problem Adding VOIP.MS
Post by: Tack on July 28, 2011, 12:56:38 PM
I had disabled auto provisioning (if you recall) so I could enter a setting to make incoming calls ring the Obi-attached phone as well as my softphone.

I think i'll just enter the VOIP info manually, but, as far as importing the Obi backup to ObiTalk, how does one do that?  I don't see any obvious import function on the home page or device set-up.

Thanks.
Title: Re: Problem Adding VOIP.MS
Post by: RonR on July 28, 2011, 01:07:15 PM
OBi

System Management -> Device Update -> Backup Configuration


OBiTALK Web Portal

OBi Dashboard -> Your OBi Device -> OBi Expert Configuration -> Import Config to OBi Expert


If you've gotten comfortable configuring the OBi locally, it's much easier/simpler to continue doing so plus you have access to more functionality and status locally than you do through the OBiTALK Web Portal.
Title: Re: Problem Adding VOIP.MS
Post by: Tack on July 28, 2011, 01:45:34 PM
Thanks for valuable advice.

OK, I entered all the information locally, as per voip.ms instruction: http://wiki.voip.ms/article/OBi110

However, I am getting the following error: Backing Off (499s):Authentication error

What now?

Thanks.

P.S.  There are no funds deposited yet in my new 'free" voip account.  Would that have an effect?
Title: Re: Problem Adding VOIP.MS
Post by: Tack on July 28, 2011, 01:56:18 PM
I might add that on the local Obi setup, there are not transports shown under the dropdown boxes for registrarserver and proxyserver, just blank white space.  And, there's no useragenttransport setting shwon, at all.

Hmmmm....
Title: Re: Problem Adding VOIP.MS
Post by: RonR on July 28, 2011, 02:00:31 PM
Service Providers -> ITSP Profile B -> General -> Name

is not used, but VoIP.ms would be a whole lot more meaninful than 100000.


Service Providers -> ITSP Profile B -> Sip -> RegistrarServer

can be left at default since it's the same as ProxyServer.


Don't forget:

Voice Services -> SP2 Service -> X_ServProvProfile : B


Authentication error is almost certainly a bad username/password.
Title: Re: Problem Adding VOIP.MS
Post by: RonR on July 28, 2011, 02:05:18 PM
Quote from: Tack on July 28, 2011, 01:56:18 PM
I might add that on the local Obi setup, there are not transports shown under the dropdown boxes for registrarserver and proxyserver, just blank white space.  And, there's no useragenttransport setting shwon, at all.

I'm not sure what you're talking about here.

Everything on ITSPB/SP2 should be at Default, except:


Service Providers -> ITSP Profile B -> General -> Name : VoIP.ms

Service Providers -> ITSP Profile B -> SIP -> ProxyServer : atlanta.voip.ms

Voice Services -> SP2 Service -> AuthUserName : (your sip credentials username)

Voice Services -> SP2 Service -> AuthPassword : (your sip credentials password)

Voice Services -> SP2 Service -> X_ServProvProfile : B

Voice Services -> SP2 Service -> CallerIDName : (your name)
Title: Re: Problem Adding VOIP.MS
Post by: Tack on July 28, 2011, 02:51:00 PM
Tellling SP2 to use Profile B did the trick, I think.  Status now shows: Registered (server=68.233.226.97:5060; expire in 51s)

Is that what I want to see?

Thanks.
Title: Re: Problem Adding VOIP.MS
Post by: RonR on July 28, 2011, 03:01:57 PM
Looks promising.

The real test is to make a call.
Title: Re: Problem Adding VOIP.MS
Post by: Tack on July 28, 2011, 03:19:11 PM
Guess I have to add some funds to the account unless someone knows a free test-call number.
Title: Re: Problem Adding VOIP.MS
Post by: QBZappy on July 28, 2011, 04:11:36 PM
Echo test on voipms works with zero balance in the account I think. Dial 4443. I'm not sure how you are setup, you may need to setup a dial plan for 4 digit calling.
Title: Re: Problem Adding VOIP.MS
Post by: Tack on July 28, 2011, 07:49:54 PM
Thanks.  Yes, 4443 worked perfectly for echo test.  I'm good to go.

Title: Re: Problem Adding VOIP.MS
Post by: TSellers on August 12, 2011, 04:36:16 PM
I'm also having a problem getting VOIP.ms on SP2 Service, ITSP Profile B. I have Freephoneline on Profile A and it works fine. My voip.ms is working fine on a PAP2T ATA. I have followed the instructions above, using my own password, server and configuration examples in voip.ms tutorial for the Obi110, but still no luck. Because I have Freephoneline on port 5060, I placed voip.ms on port 5080 which I was advised to do by a VOIP.ms support person when I was setting up the Linksys ATA. So accordingly I have used that port assignment in the Obi110, and I have also forwarded it in the Router tables to the IP that the Obi is using.

Any suggestions on how to proceed would be much appreciated,

Regards, John
Title: Re: Problem Adding VOIP.MS
Post by: RonR on August 12, 2011, 04:45:53 PM
You shouldn't need to change any port numbers in the OBi.  I recommend you return them all to Default.  In your router, forward ports 5060 - 5061 and you should be fine.

The most common cause of problems is forgetting:

Voice Services -> SP2 Service -> X_ServProvProfile : B

The settings in Reply #7 above should be appropriate.
Title: Re: Problem Adding VOIP.MS
Post by: TSellers on August 12, 2011, 08:14:28 PM
Thanks for that.

I had noted that configuration string and changed it to X_ServProvProfile B

I also changed the Ports back to 5060 as suggested, and reviewed the changes suggested in reply #7 to make sure I had not missed anything. In addition I noted that VOIP.ms had suggested:

QuoteThe default is PSTN. Select SP1 Service if you only have one SIP account configured on the device. Select Trunk Group 1 to have it attempt to place calls using SP1 first, then SP2. Additional Trunk groups can be configured under Voice Services >> Gateways and Trunk Groups.

So I played with those settings some more and did some trial and error, but nothing I did had any effect. Could my present problem lay in the Gateway and Trunk Group settings?
Title: Re: Problem Adding VOIP.MS
Post by: RonR on August 12, 2011, 08:43:07 PM
You've never mentioned exactly how it's not working.

Does:

Status -> System Status -> SP2 Service Status -> Status

show registered?

You don't need anything set under: Voice Services -> Gateways and Trunk Groups

Physical Interfaces -> PHONE Port PrinaryLine is probably set to SP1 Service, which means you have to place calls for SP2 using **2 + number.
Title: Re: Problem Adding VOIP.MS
Post by: TSellers on August 12, 2011, 08:50:38 PM
Thanks, I was going around in circles trying and retrying various parameters when the post was updated.

Status for SP2 is: Register Failed: 403

Line port satus shows:
On Hook 
0 mA 
0 V

My phone port is set to 'Trunk Goup 1' as suggested by the voip.ms tutorial.  In Trunk Group 1 settings the TrunkList is sp1,sp2
Title: Re: Problem Adding VOIP.MS
Post by: RonR on August 12, 2011, 08:58:11 PM
Using Trunk Group 1 will cause calls to go out SP1 if available, SP2 otherwise.

The OBi is talking to VOIP.ms, but VOIP.ms is rejecting the SIP Registration request.  Are you sure you're using the correct SIP credentials?

Ignore the VOIP.ms tutotial and use ONLY the settings in Reply #7 above.  Everything else on SP2 and ITSPB should be set to Default.
Title: Re: Problem Adding VOIP.MS
Post by: TSellers on August 12, 2011, 09:14:28 PM
Thanks,

Just to be safe, under system management I did a 'Reset Configuration' first. Then I went back and just entered the steps shown in #7. I did not configure SP1, so it is back to defaults. THe only difference from step #7 of course is the server I use which is 'Toronto2.voip.ms' rather than Atlanta. After a reboot I see: 'Register Failed: 403'

FOr my user ID and password I cut and paste them direct from my account page at voip.ms, and make sure there are no leading or trailing spaces on the line before saving it. THey are the same as what the PAP2T is using as well.
Title: Re: Problem Adding VOIP.MS
Post by: RonR on August 12, 2011, 09:19:17 PM
You don't have the PAP2T also registering, do you?  Some providers allow multiple registrations, other don't.

Does your router have SIP ALG support?  If so, turn it off.

You might try another server, just in case the Toronto server is having problems at the moment.
Title: Re: Problem Adding VOIP.MS
Post by: TSellers on August 12, 2011, 09:34:37 PM
Bless you, reminds me of a good british detective series thinking of that...

yes the PAP2T was also still connected to the router. So I went back and disconnected the RJ45 cable. Gave it some time and a few reboots, and still seeing 'Register Failed: 403'.

I'm running DD-WRT mega on my router, so I'll have a look around in it and see if I can find ALG, all I've found so far is 'Milkfish SIP Router' tab which is disabled.
Title: Re: Problem Adding VOIP.MS
Post by: sramaswamy on November 29, 2011, 05:09:45 PM
Thanks RonR and others for the tip. I had exactly same problem and the fix mentioned by RonR worked

Voice Services -> SP2 Service -> X_ServProvProfile : B

The ObiTalk configuration page is very well thought out and so easy to work with. But wonder how they forgot to update this value for voip.ms. While I do not mind updating the configuration locally, it is overwhelming with so many fields. ObiTalk makes it all nice and effortless.

I will let voip.ms know about this fix, so that they can update their wiki page with this instruction.

Thanks once again. RonR,  you are simply awesome.
Title: Re: Problem Adding VOIP.MS
Post by: TSellers on November 29, 2011, 08:18:11 PM
Thanks for the update. I have actually not used the Obi since the last post. I'm thinking now to use one ATA for voip.ms, and the Obi for freephoneline.ca, or vice-versa. I'm giving up on the concept of using the one Obi ATA for 2 different providers.