[OpenSIPS-Users] msrp relay

Mon Feb 18 10:10:53 CET 2013

I installed msrprelay and run it successful. My problem are two SIP end-points cannot make File Transfer session if them located behind NAT. Please see flow:
INVITE sip:1001 at 192.168.103.107:1059;transport=tcp SIP/2.0
Record-Route: <sip:123.30.188.104;transport=tcp;lr=on;did=817.c172;nat=yes>
Via: SIP/2.0/TCP 123.30.188.104;branch=z9hG4bKb2d7.61f1d4b2.0;i=2
Via: SIP/2.0/TCP 192.168.0.35:55150;received=113.160.24.110;branch=z9hG4bK891608784;rport=55150
From: <sip:1004 at 123.30.188.104>;tag=891604370
To: <sip:1001 at 123.30.188.104>
Contact: <sip:1004 at 192.168.0.35:55150;alias=113.160.24.110~55150~2;transport=tcp>;+g.oma.sip-im;language="en,fr"
Call-ID: 5538bbe8-b226-77d1-f14e-8b9ff44f0afd
CSeq: 6081 INVITE
Content-Type: application/sdp
Content-Length: 547
Max-Forwards: 16
Subject: FIXME
Allow: INVITE, ACK, CANCEL, BYE, MESSAGE, OPTIONS, NOTIFY, PRACK, UPDATE, REFER
Privacy: none
P-Access-Network-Info: ADSL;utran-cell-id-3gpp=00000000
User-Agent: IM-client/OMA1.0 Boghe/v2.0.130.804
P-Preferred-Identity: <sip:1004 at 123.30.188.104>
Supported: 100rel

v=0
o=doubango 1983 678901 IN IP4 192.168.0.35
s=-
c=IN IP4 192.168.0.35
t=0 0
m=message 55152 TCP/MSRP *
c=IN IP4 192.168.0.35
a=path:msrp://192.168.0.35:55152/891607881;tcp
a=connection:new
a=setup:actpass
a=accept-types:message/CPIM application/octet-stream
a=accept-wrapped-types:application/octet-stream image/jpeg image/gif image/bmp image/png
a=sendonly
a=file-selector:name:"asr_tts.png" type:application/octet-stream size:18679
a=file-transfer-id:891584904
a=file-disposition:attachment
a=file-icon:cid:test at doubango.org

SIP/2.0 100 Trying (sent from the Transaction Layer)
Via: SIP/2.0/TCP 123.30.188.104;branch=z9hG4bKb2d7.61f1d4b2.0;i=2
From: <sip:1004 at 123.30.188.104>;tag=891604370
To: <sip:1001 at 123.30.188.104>
Call-ID: 5538bbe8-b226-77d1-f14e-8b9ff44f0afd
CSeq: 6081 INVITE
Content-Length: 0
Via: SIP/2.0/TCP 192.168.0.35:55150;rport=55150;received=113.160.24.110;branch=z9hG4bK891608784
Record-Route: <sip:123.30.188.104;transport=tcp;lr=on;did=817.c172;nat=yes>

SIP/2.0 180 Ringing
Via: SIP/2.0/TCP 123.30.188.104;branch=z9hG4bKb2d7.61f1d4b2.0;i=2
From: <sip:1004 at 123.30.188.104>;tag=891604370
To: <sip:1001 at 123.30.188.104>;tag=1839963
Contact: <sip:1001 at 192.168.103.107:1059;transport=tcp>
Call-ID: 5538bbe8-b226-77d1-f14e-8b9ff44f0afd
CSeq: 6081 INVITE
Content-Length: 0
Via: SIP/2.0/TCP 192.168.0.35:55150;rport=55150;received=113.160.24.110;branch=z9hG4bK891608784
Record-Route: <sip:123.30.188.104;transport=tcp;lr=on;did=817.c172;nat=yes>
Require: 100rel
RSeq: 4539
Allow: ACK, BYE, CANCEL, INVITE, MESSAGE, NOTIFY, OPTIONS, PRACK, REFER, UPDATE

PRACK sip:1001 at 192.168.103.107:1059;transport=tcp SIP/2.0
Via: SIP/2.0/TCP 123.30.188.104;branch=z9hG4bK82d7.8af0dc21.0;i=2
Via: SIP/2.0/TCP 192.168.0.35:55150;received=113.160.24.110;branch=z9hG4bK891604861;rport=55150
From: <sip:1004 at 123.30.188.104>;tag=891604370
To: <sip:1001 at 123.30.188.104>;tag=1839963
Contact: <sip:1004 at 192.168.0.35:55150;alias=113.160.24.110~55150~2;transport=tcp>;+g.oma.sip-im;language="en,fr"
Call-ID: 5538bbe8-b226-77d1-f14e-8b9ff44f0afd
CSeq: 6082 PRACK
Content-Length: 0
Max-Forwards: 16
Subject: FIXME
Allow: INVITE, ACK, CANCEL, BYE, MESSAGE, OPTIONS, NOTIFY, PRACK, UPDATE, REFER
Privacy: none
P-Access-Network-Info: ADSL;utran-cell-id-3gpp=00000000
User-Agent: IM-client/OMA1.0 Boghe/v2.0.130.804
RAck: 4539 6081 INVITE

SIP/2.0 200 OK
Via: SIP/2.0/TCP 123.30.188.104;branch=z9hG4bK82d7.8af0dc21.0;i=2
From: <sip:1004 at 123.30.188.104>;tag=891604370
To: <sip:1001 at 123.30.188.104>;tag=1839963
Contact: <sip:1001 at 192.168.103.107:1059;transport=tcp>
Call-ID: 5538bbe8-b226-77d1-f14e-8b9ff44f0afd
CSeq: 6082 PRACK
Content-Length: 0
Via: SIP/2.0/TCP 192.168.0.35:55150;rport=55150;received=113.160.24.110;branch=z9hG4bK891604861

SIP/2.0 200 OK
Via: SIP/2.0/TCP 123.30.188.104;branch=z9hG4bKb2d7.61f1d4b2.0;i=2
From: <sip:1004 at 123.30.188.104>;tag=891604370
To: <sip:1001 at 123.30.188.104>;tag=1839963
Contact: <sip:1001 at 192.168.103.107:1059;transport=tcp>
Call-ID: 5538bbe8-b226-77d1-f14e-8b9ff44f0afd
CSeq: 6081 INVITE
Content-Type: application/sdp
Content-Length: 315
Via: SIP/2.0/TCP 192.168.0.35:55150;rport=55150;received=113.160.24.110;branch=z9hG4bK891608784
Record-Route: <sip:123.30.188.104;transport=tcp;lr=on;did=817.c172;nat=yes>
Allow: ACK, BYE, CANCEL, INVITE, MESSAGE, NOTIFY, OPTIONS, PRACK, REFER, UPDATE

v=0
o=doubango 1983 678901 IN IP4 192.168.103.107
s=-
c=IN IP4 192.168.103.107
t=0 0
m=message 1060 TCP/MSRP *
c=IN IP4 192.168.103.107
a=path:msrp://192.168.103.107:1060/1838028;tcp
a=connection:new
a=setup:active
a=accept-types:message/CPIM
a=accept-wrapped-types:application/octet-stream
a=recvonly

ACK sip:1001 at 192.168.103.107:1059;transport=tcp SIP/2.0
Via: SIP/2.0/TCP 123.30.188.104;branch=z9hG4bKcydzigwkX;i=2
Via: SIP/2.0/TCP 192.168.0.35:55150;received=113.160.24.110;branch=z9hG4bK891589177;rport=55150
From: <sip:1004 at 123.30.188.104>;tag=891604370
To: <sip:1001 at 123.30.188.104>;tag=1839963
Contact: <sip:1004 at 192.168.0.35:55150;alias=113.160.24.110~55150~2;transport=tcp>;+g.oma.sip-im;language="en,fr"
Call-ID: 5538bbe8-b226-77d1-f14e-8b9ff44f0afd
CSeq: 6081 ACK
Content-Length: 0
Max-Forwards: 16
Subject: FIXME
Allow: INVITE, ACK, CANCEL, BYE, MESSAGE, OPTIONS, NOTIFY, PRACK, UPDATE, REFER
Privacy: none
P-Access-Network-Info: ADSL;utran-cell-id-3gpp=00000000
User-Agent: IM-client/OMA1.0 Boghe/v2.0.130.804

BYE sip:1001 at 192.168.103.107:1059;transport=tcp SIP/2.0
Via: SIP/2.0/TCP 123.30.188.104;branch=z9hG4bK92d7.e0554b27.0;i=2
Via: SIP/2.0/TCP 192.168.0.35:55150;received=113.160.24.110;branch=z9hG4bK891605340;rport=55150
From: <sip:1004 at 123.30.188.104>;tag=891604370
To: <sip:1001 at 123.30.188.104>;tag=1839963
Call-ID: 5538bbe8-b226-77d1-f14e-8b9ff44f0afd
CSeq: 6083 BYE
Content-Length: 0
Max-Forwards: 16
Accept-Contact: *;+g.oma.sip-im
Accept-Contact: *;language="en,fr"
Subject: FIXME
Allow: INVITE, ACK, CANCEL, BYE, MESSAGE, OPTIONS, NOTIFY, PRACK, UPDATE, REFER
Privacy: none
P-Access-Network-Info: ADSL;utran-cell-id-3gpp=00000000
User-Agent: IM-client/OMA1.0 Boghe/v2.0.130.804
P-Preferred-Identity: <sip:1004 at 123.30.188.104>

SIP/2.0 200 OK
Via: SIP/2.0/TCP 123.30.188.104;branch=z9hG4bK92d7.e0554b27.0;i=2
From: <sip:1004 at 123.30.188.104>;tag=891604370
To: <sip:1001 at 123.30.188.104>;tag=1839963
Contact: <sip:1001 at 192.168.103.107:1059;transport=tcp>
Call-ID: 5538bbe8-b226-77d1-f14e-8b9ff44f0afd
CSeq: 6083 BYE
Content-Length: 0
Via: SIP/2.0/TCP 192.168.0.35:55150;rport=55150;received=113.160.24.110;branch=z9hG4bK891605340

I run msrprelay and SIP server on same physical server with IP: 123.30.188.104. 

________________________________
 From: Saúl Ibarra Corretgé <saul at ag-projects.com>
To: OpenSIPS users mailling list <users at lists.opensips.org> 
Sent: Monday, February 18, 2013 3:10 PM
Subject: Re: [OpenSIPS-Users] msrp relay

On Feb 18, 2013, at 5:03 AM, nguyen khue wrote:

> Hi all,
> 
> How I can integrates msrprelay (msrprelay.org) with opensips to make File Transfer session between SIP end-points located behind NAT?. Please guide me. 
> I tested file transfer between two SIP end-points in LAN and it worked successful.
> 

What problems did you ran into? Did you follow the installation guide http://msrprelay.org/projects/msrprelay/wiki/InstallationGuide ?

Regards,

--
Saúl Ibarra Corretgé
AG Projects

_______________________________________________
Users mailing list
Users at lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20130218/cd2ffc1c/attachment-0001.htm>