[Spce-user] Internal error when using TLS

[Andrew Pogrebennyk]

Hi,

Could you also look into kamailio-lb.log for this call and check if you
have any errors there?

On 08/29/2012 12:05 PM, Jirka Jirout wrote:
> Hello,
> 
> I have a rather weird issue here. If I try to make a call *to* client connected using TLS, I get an "NAT-Reply - S=500 - Server Internal Error". The log looks like this (1004 connected via TCP calls 1001 that uses TLS):
> 
>> Aug 29 11:50:34 crypto2 /usr/sbin/kamailio[2090]: INFO: <script>: Request leaving server, D-URI='sip:127.0.0.1:5080' - M=INVITE R=sips:1001 at 192.168.178.23:52423;transport=tcp F=sip:1004 at crypto.PROVIDER.cz T=sip:1001 at crypto.PROVIDER.cz IP=83.161.151.39:54945 (127.0.0.1:5888) ID=1106beed-8cff-0673-9aba-96acc4d7f665
>> Aug 29 11:50:34 crypto2 /usr/sbin/kamailio[2086]: INFO: <script>: NAT-Reply - S=500 - Server Internal Error F=sip:1004 at crypto.PROVIDER.cz T=sip:1001 at crypto.PROVIDER.cz IP=83.161.151.39:54945 (127.0.0.1:5080) ID=1106beed-8cff-0673-9aba-96acc4d7f665
>> Aug 29 11:50:34 crypto2 /usr/sbin/kamailio[2086]: INFO: <script>: Failure route for local call - M=INVITE R=sips:1001 at 192.168.178.23:52423;transport=tcp F=sip:1004 at crypto.PROVIDER.cz T=sip:1001 at crypto.PROVIDER.cz IP=83.161.151.39:54945 (127.0.0.1:5888) ID=1106beed-8cff-0673-9aba-96acc4d7f665
>> Aug 29 11:50:34 crypto2 /usr/sbin/kamailio[2086]: INFO: <script>: Stop mediaproxy for current branch using first Via - M=INVITE R=sips:1001 at 192.168.178.23:52423;transport=tcp F=sip:1004 at crypto.PROVIDER.cz T=sip:1001 at crypto.PROVIDER.cz IP=83.161.151.39:54945 (127.0.0.1:5888) ID=1106beed-8cff-0673-9aba-96acc4d7f665
> 
> and the packet from the server looks like this (note I am using 5888 as port for TCP since 5060 is somehow screwed by some firewall between the client and the server).
> 
>> U 2012/08/29 11:50:34.034807 127.0.0.1:5062 -> 127.0.0.1:5888
>> SIP/2.0 500 Server Internal Error'
>> Record-Route: <sip:127.0.0.1:5062;lr=on;ftag=2162558533;did=ecd.dfd55613;mpd=ii;rtpprx=yes;vsf=dU5ZM1lleEZ6TkxNaUpYTlBkZk11TlkzWWV4>'
>> Record-Route: <sip:127.0.0.1:5888;lr;r2=on;nat=yes;ngcplb=yes>,<sip:SERVER_PUBLIC_IP:5888;lr;r2=on;nat=yes>'
>> Via: SIP/2.0/UDP SERVER_PUBLIC_IP:5888;rport=5888;received=127.0.0.1;branch=z9hG4bK2299.7b625244b4cc820d44233263d65dcc44.0;i=336'
>> Via: SIP/2.0/TCP 192.168.178.25:54945;received=83.161.151.39;rport;branch=z9hG4bK3609433351;rport=54945'
>> From: <sip:1004 at crypto.PROVIDER.cz>;tag=2162558533'
>> To: <sip:1001 at crypto.PROVIDER.cz>;tag=3B8592BC-503DE5EA00008580-7E2BA700'
>> Call-ID: 1106beed-8cff-0673-9aba-96acc4d7f665'
>> CSeq: 1694823598 INVITE'
>> Server: Sipwise NGCP Application Server'
>> Content-Length: 0'
> 
> If the call is initiated by the client that uses TLS, it goes thru without any problems (unless the other party also uses TLS).
> 
> Any help or hint would be greatly appreciated. 
> 
> regards, jj
> 
> _______________________________________________
> Spce-user mailing list
> Spce-user at lists.sipwise.com
> http://lists.sipwise.com/listinfo/spce-user
>