Setting Up New Obi202
kaniki:
Quote from: MurrayB on August 31, 2015, 04:39:32 pm
I will let it fry overnight
make sure you got some marshmallows.. lol
MurrayB:
I set everything up SP1, SP2, and SP3 are all operating properly on Voip.ms as well as both phone ports. However, SP4 is not registering with Voip.ms. I reentered everything, which was copy and paste from Voip.ms or another Obi then tried manually entering server, account, and password. I compared all of the pages with other SP and phone and voice everything is OK. Yes, another Obi is registering that account OK and the new Obi202 is the only one on line.
My inclination is that the unit is defective. One SP down though sounds weird.
Thanks!
OzarkEdge:
Quote from: MurrayB on September 01, 2015, 11:21:47 am
My inclination is that the unit is defective. One SP down though sounds weird.
Not likely.
I would keep the old unit offline, off the sub-account.
Perhaps set a new SIP password on the subject sub-account.
And confirm the SP4 Voice Service settings... something like these:
SP4 Service - SP4 Service::Enable = checked ;VoIP.ms pop server sub-account1.
SP4 Service - SP4 Service::X_ServProvProfile = A ;or B, C, or D.
SP4 Service - SP4 Service::X_InboundCallRoute = ph1 ;route inbound to PH1
SP4 Service - SP4 Service::X_NoRegNoCall = checked ;speed up trunk group failover.
SP4 Service - SP4 Service::X_KeepAliveEnable = checked ;keep-alive router NAT session to allow a longer registration period.
SP4 Service - SP4 Service::X_KeepAliveExpires = 15 ;default seconds keep-alive period.
SP4 Service - SP4 Service::X_UserAgentPort = 6xxx4 ;move port to obscure it.
SP4 Service - SIP Credentials::AuthUserName = sub-account4 ID
SP4 Service - SIP Credentials::AuthPassword = sub-account4 password
SP4 Service - SIP Credentials::X_EnforceRequestUserID = checked ;prohibit anonymous SIP.
SP4 Service - Calling Features::CallerIDName = callerID name ;outbound CallerID name.
SP4 Service - Calling Features::MWIEnable = Enabled ;stutter tone message waiting indication on PH1.
SP4 Service - Calling Features::X_VMWIEnable = Enabled ;visual message waiting indication on PH1.
Submit
Reboot
What is the OBi status message for the failed registration?
OE
drgeoff:
Quote from: MurrayB on September 01, 2015, 11:21:47 am
My inclination is that the unit is defective. One SP down though sounds weird.
There is no different hardware employed for registering the individual SPs. And a software fault causing only one SP to fail to register is rather unlikely too.
If you are in doubt try swapping the non-registering account with one that is registering. Put the problem account on SP1 and put on SP4 the account that was on SP1.
MurrayB:
Thanks drgeoff - I just defaulted SP4 and reentered the values. I thought that I would try that before moving around the SPs. This is what the status shows:
SP4 Service Status
Parameter Name Value
Status Register Failed: 403 Forbidden
Any comments before I move the SPs around?
Thanks!
Navigation
[0] Message Index
[#] Next page
[*] Previous page