I think Lync Server is not correctly handling the SIP CANCEL message with cause=200. Scenario: calls are dual forked by the PBX, one goes to the SIP phone, the other one goes through the SIP trunk to Lync Server. If the call is answered by the phone, the PBX sends a CANCEL message to Lync with: Reason: SIP; cause=200; text="Call completed elsewhere". Lync Server also generates a SIP message 487, request terminated, with ...more »
If you create a trusted application endpoint, and assign a SIP address where the "sip:" prefix is either capitalized or in all upper case, you don't get an error/warning. However, if you then try to send an IM to that endpoint, you get obscure errors. The solution is to change the "sip:" prefix to all lower case. It would be nice if Lync either errored when you try to assign it, or just corrected it to all lower case. ...more »
I have only one SIP domain in my deployment, yet when I go to enable a new user in the Control Panel, the SIP domain fields under "Generate user's SIP URI" are all blank. I need to click the pull-down and select from the only option there is. Lync has a "Default" SIP domain. The CSCP should populate the SIP domain fields on the form with this value automatically. Should the developers see reason why this shouldn't ...more »
support standards based SIP phones without the need for 3rd parting software (smartsip) or gateway.
I would presume these phone would get limited lync functionality: basic presence like on a call and available, and some other limitations.