News:

On Tuesday September 6th the forum will be down for maintenance from 9:30 PM to 11:59 PM PDT

Main Menu

voip.ms AccountRegister Failed: 403 Forbidden

Started by Look30, October 10, 2012, 03:09:40 PM

Previous topic - Next topic

Look30

I am new to voip but although I did everything  , I hope , right , created voip.ms account , purchased DID number , when I register the service on my Obi 110 as second line I get :

voip.ms Account   Register Failed: 403 Forbidden.
What is wrong ?

Please help.

hwittenb

You can get 403 Forbidden from voip.ms if your password is not correct.

Look30

#2
It was the username. Obi configuration should explain that voip.ms username is NOT the same as when you login into voip.ms.
The correct user name is found  in the Portal under SIP/IAX Main Username  and is alphanumeric 123456.
Password is the same as when you login on the website account.

geva

FYI - you can change your SIP/IAX password for that peer user name so that it is not the same as your VoIP.ms portal account.  This just adds another layer of security as someone gaining access to your SIP password would not be able to connect to your portal and start screwing around with settings or removing call restrictions.

tavie888

Hello,

Today after registering my voip.ms sub-account to SP2 in OBiTALK Portal, I also got an error 403 because my AuthUserID and AuthUserPassword for this sub-account is different from those of my voip.ms credentials.  In other words, I failed to register OBi110 to my sub-account.

I had to change userid and password back to those of voip.ms main account before I can register the device.

Does anyone know how to register an OBi device to a sub-account of voip.ms?

Lavarock7

I was having problems with Voip.Ms calls today and replied here, but it appears that my problem is not related to this. I removed my reply from this thread.
My websites: Kona Coffee: http://itskona.com and Web Hosting: http://planetaloha.info
A simplified Voip explanation: http://voip.planet-aloha.com

geva

Quote from: tavie888 on November 19, 2012, 08:37:26 PM
Today after registering my voip.ms sub-account to SP2 in OBiTALK Portal, I also got an error 403 because my AuthUserID and AuthUserPassword for this sub-account is different from those of my voip.ms credentials.  In other words, I failed to register OBi110 to my sub-account.

I had to change userid and password back to those of voip.ms main account before I can register the device.

Does anyone know how to register an OBi device to a sub-account of voip.ms?

You need to update the credentials used in the Obi to the ones which you setup for the VoIP.ms sub-account.  You are essentially connecting as a different "user" (or peer, or endpoint).  If you account number is something like 175643, then the sub accounts are numbered like 175643_1 in the order in which you create them.  During the sub-account creation process you also set a strong password for the sub-account, and this needs to be put into the Obi configuration.

It is really no more complicated than the initial setup... you are just changing the credentials.

Clive

I regularly get 403 Forbidden on my obi boxes. Often happens for 2 - 10 mins at a time. Sometimes I change the user id to force a reboot and set it back again and that usually resolves it.

Just don't know why it keeps happening.

Lavarock7

When setting up Voip.Ms accounts, I always create subaccounts so that I can more easily manage the account. That allows me to create a test subaccount for Csipsimple or Zoiper, etc.
My websites: Kona Coffee: http://itskona.com and Web Hosting: http://planetaloha.info
A simplified Voip explanation: http://voip.planet-aloha.com

Clive

#9
I have 40 sub accounts and it's only on the obi dashboard that they appear to have this issue as they still show as registered on the voip.ms admin page.

RFord

Clive:

I think your problem is related to the Registration Period.  I have mine set to 30 (seconds).  I would also make sure that:

InviteExpires           30      
ReInviteExpires           10      
RegisterExpires           30      
RegisterMinExpires   15      
RegisterRetryInterval   120   

SERVICE PROVIDERS  >>  Under ITSP Profile X  >>  SIP   (X = A or B)

Clive

#11
Thanks for that, I'll give it a go and see if it cures the problem.

Doesn't extending the register retry period lengthen the time it would be 'offline'?

ElKayy

I got the reason 403 trying to register an OBi adapter as well. I was using my web portal email address and password - which is incorrect and to clarify what Look30 said: the username is what VOIP.ms calls: SIP/IAX Main Username and it is numeric (223344) not alphanumeric