03-31-2016 02:38 PM - edited 03-18-2019 05:45 AM
Hello,
I am trying to register an sx10 with VCS and I am receiving some Sip errors.
I wanted to confirm the SX version is compatible with my version of VCS-C & TMS...
SX10 = TC7.1.3.db40e55
VCSC = X7.2.2
TMS = Version: 14.2.0
ERROR: SIP Profile Registration
SIP registration failed: 403 Forbidden. Verify SIP configuration and connectivity to SIP proxy.
ERROR: Call Protocol Registration
The system is not registered on SIP. It will not be able to place or receive calls until properly configured.
I have added the device in TMS and it does register, however I am getting frequent errors with Provisioning as well.
ERROR: Provisioning Status
Provisioning failed: Provisioning is in an error state.
I believe I may have a version issue so wanted to confirm versions needed.
Any help is appreciated.
Thanks!
Solved! Go to Solution.
04-19-2016 11:12 AM
I wanted to update this thread in case someone else comes across same issue.
The issue is resolved, it was caused by 2 issues.
a. the URI was not unique
b. the account I was using to authenticate was an AD account Synced with LDAP thru TMS. For Endpoints they need to have a local account.
Once SX was provided a new URI and a Local user was setup in VCS we were able to register.
03-31-2016 07:45 PM
SX10 is only officially supported in TMS version 14.4 and later if/when using TC version software, if you upgrade to CE8.0 then you'll be needing TMS 15.0 or later.
Check your system settings re the SIP error, also ensure you don't have a policy in place on the VCS which prevents it from registering.
/jens
Please rate replies and mark question(s) as "answered" if applicable.
04-01-2016 01:44 AM
Hello, Dennis
I think version your SX10 is not important for registration on VCS.
Do you have another endpoints which succesfully registered ?
You may perform factory reset for your SX10 and attempt to register after.
Also check registration Allow/Deny list , subzones accesse rules ..
br Oleksandr
04-19-2016 11:12 AM
I wanted to update this thread in case someone else comes across same issue.
The issue is resolved, it was caused by 2 issues.
a. the URI was not unique
b. the account I was using to authenticate was an AD account Synced with LDAP thru TMS. For Endpoints they need to have a local account.
Once SX was provided a new URI and a Local user was setup in VCS we were able to register.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide