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