Thanks for the reply
Actually one of my co-workers said this is normal for ESN5 (which is required for the SIP routing for OCS to work)
I just googled ESN5 and this came up (from this board):
The '105' (ed. 100 in my case) is a TCOS (Traveling Class of Service) value and is being added since...
I have inherited a release 7.0 system that has a strange problem. The called number on outgoing calls on a SIP trunk / IP DCH is pre-pending 100. This is not a DMI, not ZBD, not an HLOC or LOC. That 6667 is being dialled by a HOT-P key on an AST as part of an OCS testbed.
If I put a DMI on...
Just finished interop testing of IP Office and CS1000. Results are mixed. Outgoing calls from IP Office terminate correctly on UNistim sets and support all basic SIP functionality (Update and Refer).
Calls in the other direction get routed out the SPS to the IP Office on SIP trunks as...
If the set is showing an assert it has hit an unrecoverable software error in the set firmware. That is the way Spectralink does their error handling. They throw an assert and hang.
Download the crash dump off a set and open up a ticket with them.
Thanks. Going through that link now
I think we have the SIP routing ok. The problem is the media path after the call is setup.
Problem is that the CS1000 introduces a SIP Proxy Server into the scenario that you describe in that other thread.
I have to make sure I don't have a codec mismatch...
Hello all:
Just got this IPOffice in the lab a few days ago and have been trying to SIP trunk it to a CS1000 release 7.0 system.
I can't find any documentation on how to do this. I have the IP Office registered correctly on the SPS (NRS) and calls from third party sip clients registered to...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.