[Spce-user] Problem with local calls

[Andrew Pogrebennyk]

Daniel,
There is some external entity mangling the contents of SIP headers.

Most likely you have a router with SIP ALG function enabled. LB sends an
INVITE to the callee with two Record-Route headers with server's
eaddress and iaddress (127.0.0.1). We get back a 200 OK with 127.0.0.1
changed to 77.253.151.193:49156:

#
U 87.98.235.176:5060 -> 77.253.151.193:61699
INVITE
sip:kim at 77.253.151.193:49155;transport=udp;registering_acc=sip_leofon_pl
SIP/2.0.
Max-Forwards: 10.
Record-Route:
<sip:87.98.235.176;r2=on;lr=on;ftag=3459D4E4-4FFC0F5E0005DEC8-D1E51700>.
Record-Route:
<sip:127.0.0.1;r2=on;lr=on;ftag=3459D4E4-4FFC0F5E0005DEC8-D1E51700>.
Via: SIP/2.0/UDP 87.98.235.176;branch=z9hG4bK52c8.873a2d91.0.
Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKGS47LavA;rport=5080.
From: "123" <sip:123 at sip.leofon.pl>;tag=3459D4E4-4FFC0F5E0005DEC8-D1E51700.
To: <sip:kim at sip.leofon.pl>.
CSeq: 10 INVITE.
Call-ID: e7f8806e61b301f6811b9f4b686df8d0 at 0:0:0:0:0:0:0:0_b2b-1.
P-Asserted-Identity: <sip:123 at sip.leofon.pl>.
Supported: timer.
Session-Expires: 300.
Min-SE: 90.
Content-Type: application/sdp.
Content-Length: 1095.
Contact: <sip:ngcp-lb at 87.98.235.176:5060>.
[...]

#
U 77.253.151.193:61699 -> 87.98.235.176:5060
SIP/2.0 200 OK.
To: <sip:kim at sip.leofon.pl>;tag=8904001d.
Via: SIP/2.0/UDP 87.98.235.176;branch=z9hG4bK52c8.873a2d91.0,SIP/2.0/UDP
127.0.0.1:5080;branch=z9hG4bKGS47LavA;rport=5080.
Record-Route:
<sip:87.98.235.176;r2=on;lr=on;ftag=3459D4E4-4FFC0F5E0005DEC8-D1E51700>,<sip:77.253.151.193:49156;r2=on;lr=on;ftag=3459D4E4-4FFC0F5E0005DEC8-D1E51700>.

CSeq: 10 INVITE.
Call-ID: e7f8806e61b301f6811b9f4b686df8d0 at 0:0:0:0:0:0:0:0_b2b-1.
From: "123" <sip:123 at sip.leofon.pl>;tag=3459D4E4-4FFC0F5E0005DEC8-D1E51700.
Contact: "kim"
<sip:kim at 77.253.151.193:49155;transport=udp;registering_acc=sip_leofon_pl>.
User-Agent: Jitsi1.1-nightly.build.4108Windows 7.
Content-Type: application/sdp.
Content-Length: 959.

Please check your router.

P.S. I have noticed some packets with truncated SDP, e.g.:
a=fmtp:104 profile-level-id=4DE01f;packetizat
or:
a=imageattr:104 send * re
Need to check separately what is causing this issue.

On 07/10/2012 02:45 PM, Daniel Speichert wrote:
> I have tried Jitsi nightly build (on both sides) and the same problem
> occured.
> Client-side symptoms are:
> - call is initiated
> - call is answered
> - call is NOT connected
> 
> I attach a SIP trace started just before the call was initiated until a
> few moments after clients timeout out connecting the call.
> 
> Regards,
> Daniel Speichert
>