SIP 2 Service does not save UserName

(1/5) > >>

TSellers:
I've been trying to setup SP2 Service to register with my voip.ms account (Google is on 1).

OBi110:
All the fields filled in with my account settings, according the the voip.ms Wiki for setting up OBi110.

Under SIP Credentials I enter my AuthUSerName and Password, hit submit, and the change is there. I then reboot, and it tells me on the status page there is an authentication error. I go back to the SIP Credentials and the UserName is missing: the line is blank and the default box is once again checked. Is this what is supposed to happen? If so I assume it happens because one of the other settings has caused the Authorization error, and when that happens the ATA just goes back to defaults? I would have expected that even if some other setting was out of whatck it would still save my AuthUserName setting.

Stewart:
If you are entering this info by accessing the OBi with your browser, you must first set (under System Management->Auto Provisioning) ITSP Povisioning->Method to Disabled and OBiTalk Provisioning->Method to Disabled.  Thereafter, all changes must be made at the OBi.

If you want to make future changes via OBiTALK, you can re-enable provisioning, but that will wipe out any changes you made locally.

TSellers:
Thanks very much for that Stewart, I wasn't expecting such a quick reply. I followed those instructions and indeed when I rebooted the change to my settings held after I rebooted.

Although now I see a 'Backing Off (741s):Authentication error' message in SP2 Service Status, as least now I can discount the SIP2 SIP Credentials as being the problem and carry on with troubleshooting the rest of the settings again. That same account is currently working through a Linksys PAP2T so it's probably some simple setting somewhere that I have overlooked.

Thanks again, the help was much appreciated!

Stewart:
If your PAP2T is currently online, make sure that the OBi is using a different sub-account; VoIP.ms does not permit multiple simultaneous registrations with the same credentials.

Next, if you entered your credentials by copy and paste, make sure that you didn't accidentally get a trailing space or other discrepancy.

Possibly, your router is causing trouble because of a broken ALG or a port conflict; try changing ProxyServerPort and RegistrarServerPort from 5060 to 5080, and/or changing X_UserAgentPort from 5061 to 5071 .

TSellers:
Thanks again for that. I had forgotten about the dual ATA conflict, in fact I think you may have pointed that out to me already last year when I was trying to get Freephoneline and voip.ms on the Obi when voip.ms was already running on the PAP2T. If I recall eventually at that time I could get SIP1 to work, but never could get SIP2. That was after shutting down the PAP2T and still not being able to register SIP2, so I shelved the Obi until today when I put GV on it.

Indeed I was trying to get it onto the same sub account that was being registered by the PAP2T. So I moved the Obi over to the main DID account this time. As I was already on port 5080 (because I was playing around trying to improve CSipSimple over WiFI and Android on 5060), I did not have to change that (voip.ms is also on 5080 on the PAP2T). When I went to change X_UserAgentPort I noticed X_KeepAliveServerPort was still on 5060 so I changed that to 5080, and did the other to 5071 as well. But alas no luck. I think after I get some shut-eye later today I will try to shut off the PAP2T completely and see if it makes a difference with getting it going.

I'm also batteling a weird issue with CSipSimple apparently not waking up fast enough on Android as the first call the voip.ms server thinks the device is not registered and sends the call to voice mail, then if you call back a minute later, it has woken up and will answer it. ANyway that's another matter completly, and thanks again for all the terrific help!

Navigation

[0] Message Index

[#] Next page