Calls over VPN -- SIP_URL::ParseUrlBase ParseSipUrlParams failed 80004005

I am finding in my environment that users who are on a VPN remotely have issues making phone calls to anyone else who's internal or even someone outside on their cell phone. 

The VPN client being used is Citrix Access Gateway. 

User makes calls over the Lync 2010 Client. 

I turned on Logging and gathered details from the Tracing directory with Snooper and came across these. Any idea of what is going on?

The person they're trying to call is showing up there as a name instead of a number in the log. Is that normal? 



Component: UCCP
Level: ERROR
Flag: N/A
Function: N/A
Source: N/A
Local Time: 01/23/2015-09:42:24.249
Sequence# : 00000373
CorrelationId : N/A
ThreadId : 1138
ProcessId : 1134
CpuId : 0
Original Log Entry :
01/23/2015|09:42:24.249 1134:1138 ERROR :: SIP_URL::ParseUrlParams invalid char Q found when trying to parse params


Component: UCCP
Level: ERROR
Flag: N/A
Function: N/A
Source: N/A
Local Time: 01/23/2015-09:42:24.249
Sequence# : 00000374
CorrelationId : N/A
ThreadId : 1138
ProcessId : 1134
CpuId : 0
Original Log Entry :
01/23/2015|09:42:24.249 1134:1138 ERROR :: SIP_URL::ParseUrlBase ParseSipUrlParams failed 80004005



Component: UCCP
Level: ERROR
Flag: N/A
Function: N/A
Source: N/A
Local Time: 01/23/2015-09:42:24.249
Sequence# : 00000375
CorrelationId : N/A
ThreadId : 1138
ProcessId : 1134
CpuId : 0
Original Log Entry :
01/23/2015|09:42:24.249 1134:1138 ERROR :: SIP_URL::InternalInitialize ParseSipUrl(sip:John Quincy) failed 80ee0012
January 24th, 2015 12:23am

I also ran a SIPStack Logging on the Lync server, and got this from the log file. Not sure if it's related:

Phone call:

Component: SIPStack
Level: TL_ERROR
Flag: TF_NETWORK
Function: CBufferChain::Decrypt
Source: BufferChain.cpp(3393)
Local Time: 01/23/2015-16:04:13.486
Sequence# : 00092405
CorrelationId : 
ThreadId : 3540
ProcessId : 10A0
CpuId : 5
Original Log Entry :
TL_ERROR(TF_NETWORK) [5]10A0.3540::01/23/2015-22:04:13.486.00092405 (SIPStack,CBufferChain::Decrypt:BufferChain.cpp(3393))( 000000000F693570 ) Unsupported result from schannel will close connection

Free Windows Admin Tool Kit Click here and download it now
January 24th, 2015 1:14am

Hi,

For the VPN, when users connect to the corporate network using a VPN client, Lync media traffic is sent through the VPN tunnel. This configuration can create additional latency and jitter because media traffic must pass through an additional layer of encryption and decryption.

The recommend way is to use a split tunnel for VPN. Then Lync client connects to the Access Edge Server for all signaling connections when on the corporate VPN. In addition, media sessions dont be allowed to establish connectivity through the VPN tunnel. Media sessions will be routed through the A/V Edge Server public interface.

More details:

http://blogs.technet.com/b/nexthop/archive/2011/11/15/enabling-lync-media-to-bypass-a-vpn-tunnel.aspx

Best Regards,
Eason Huang

January 26th, 2015 12:10pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics