Lync SIP Address Spacing

Author by Nathan Lasnoski

What's in a name?  Well, it seems quite a bit!  I was recently working on a Lync project where I was integrating an AudioCodes Mediant 1000 gateway with Exchange Unified Messaging and Lync.  In this integration, I had configured the Mediant 1000 IP Groups and had Exchange 2010 Unified Messaging working great with the existing PBX.  However, I ran into an issue when calling into Lync from the same gateway. The call when presented to Lync looked like this:
To: <sip:8899@Lync Voice;user=phone> Call-ID: 161529443425201116162@ CSeq: 1 INVITE Contact: <sip:2629999988@;transport=tcp> Supported: em,100rel,timer,replaces,path,early-session,resource-priority,sdp-anat Allow: REGISTER,OPTIONS,INVITE,ACK,CANCEL,BYE,NOTIFY,PRACK,REFER,INFO,SUBSCRIBE,UPDATE User-Agent: Audiocodes-Sip-Gateway-Mediant 1000/v.6.00A.042.005 Privacy: none P-Asserted-Identity: <sip:2623645809@> Content-Type: application/sdp Content-Disposition: session Content-Length: 306
Here is the associated error:
LTL_ERROR(TF_COMPONENT) [12]1F94.1F60::05/02/2011-21:16:02.400.00000e77 (S4,SipStack.OnMessageReceived:sipstack.cs(1530))(00000000002477E8)Failed to process incoming message: Invalid Request/Response line :    at Microsoft.Rtc.Internal.Sip.ParserModule.ValidateIncomingMessage(SipMessage message) at Microsoft.Rtc.Internal.Sip.ParserModule.ProcessIncoming(RawDataBuffer dataBuffer, SipConnection connection, SipMessage& message) at Microsoft.Rtc.Internal.Sip.MessageProcessingController.ProcessIncomingBuffer(RawDataBuffer buffer) TL_VERBOSE(TF_COMPONENT) [12]1F94.1F60::05/02/2011-21:16:02.400.00000e78 (S4,SipStack.OnMessageReceived:sipstack.cs(1579))(00000000002477E8)Indicating message receive failed to core layer
Notice anything interesting?  The sip address includes "#@Lync Voice" with a space. It turns out that Lync didn't like the space in the name.  I found out that the "IP Group Table" on the AudioCodes gateway had included a SIP Group Name of "Lync Voice", vs. my normal setting of "Lync", etc.  I changed it and it started working perfectly.  What was really interesting was that Exchange 2010 didn't seem to care about the same spacing issue. Happy voice integration! Nathan Lasnoski

Nathan Lasnoski

Chief Technology Officer