voip.ms AccountRegister Failed: 403 Forbidden
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.
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.
Clive:
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.
Navigation
[0] Message Index
[#] Next page
[*] Previous page