<div dir="ltr">Hi,<div><br></div><div>I think it's more helpful if you can give us calltrace in case of using msrp, sipproxy and of course 2 sip clients. Msrprelay it's act as a mediaproxy or the sip client should connect first to msrprelay, stream info from msrp and use them in invite to the sip proxy ?</div>
<div><br></div><div style>Thanks,</div><div style>Dani</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Mon, Feb 18, 2013 at 11:35 AM, Saúl Ibarra Corretgé <span dir="ltr"><<a href="mailto:saul@ag-projects.com" target="_blank">saul@ag-projects.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im"><br>
On Feb 18, 2013, at 10:10 AM, nguyen khue wrote:<br>
<br>
> 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:<br>
<br>
</div>An MSRP relay is not something that you install and automagically will solve the NAT problems. It has to be used by the endpoints themselves. You'll need to configure your endpoints to use an incoming relay and then you'll see it in the a=path SDP attribute.<br>
<br>
Relays need credentials but MSRPRelay uses the credentials from the OpenSIPS subscriber table, so you can specify the same credentials of your SIP account.<br>
<br>
<br>
Regards,<br>
<div class="HOEnZb"><div class="h5"><br>
> INVITE sip:1001@192.168.103.107:1059;transport=tcp SIP/2.0<br>
> Record-Route: <sip:123.30.188.104;transport=tcp;lr=on;did=817.c172;nat=yes><br>
> Via: SIP/2.0/TCP 123.30.188.104;branch=z9hG4bKb2d7.61f1d4b2.0;i=2<br>
> Via: SIP/2.0/TCP 192.168.0.35:55150;received=113.160.24.110;branch=z9hG4bK891608784;rport=55150<br>
> From: <<a href="mailto:sip%3A1004@123.30.188.104">sip:1004@123.30.188.104</a>>;tag=891604370<br>
> To: <<a href="mailto:sip%3A1001@123.30.188.104">sip:1001@123.30.188.104</a>><br>
> Contact: <sip:1004@192.168.0.35:55150;alias=113.160.24.110~55150~2;transport=tcp>;+g.oma.sip-im;language="en,fr"<br>
> Call-ID: 5538bbe8-b226-77d1-f14e-8b9ff44f0afd<br>
> CSeq: 6081 INVITE<br>
> Content-Type: application/sdp<br>
> Content-Length: 547<br>
> Max-Forwards: 16<br>
> Subject: FIXME<br>
> Allow: INVITE, ACK, CANCEL, BYE, MESSAGE, OPTIONS, NOTIFY, PRACK, UPDATE, REFER<br>
> Privacy: none<br>
> P-Access-Network-Info: ADSL;utran-cell-id-3gpp=00000000<br>
> User-Agent: IM-client/OMA1.0 Boghe/v2.0.130.804<br>
> P-Preferred-Identity: <<a href="mailto:sip%3A1004@123.30.188.104">sip:1004@123.30.188.104</a>><br>
> Supported: 100rel<br>
><br>
><br>
> v=0<br>
> o=doubango 1983 678901 IN IP4 192.168.0.35<br>
> s=-<br>
> c=IN IP4 192.168.0.35<br>
> t=0 0<br>
> m=message 55152 TCP/MSRP *<br>
> c=IN IP4 192.168.0.35<br>
> a=path:msrp://<a href="http://192.168.0.35:55152/891607881;tcp" target="_blank">192.168.0.35:55152/891607881;tcp</a><br>
> a=connection:new<br>
> a=setup:actpass<br>
> a=accept-types:message/CPIM application/octet-stream<br>
> a=accept-wrapped-types:application/octet-stream image/jpeg image/gif image/bmp image/png<br>
> a=sendonly<br>
> a=file-selector:name:"asr_tts.png" type:application/octet-stream size:18679<br>
> a=file-transfer-id:891584904<br>
> a=file-disposition:attachment<br>
> a=<a href="mailto:file-icon%3Acid%3Atest@doubango.org">file-icon:cid:test@doubango.org</a><br>
><br>
> SIP/2.0 100 Trying (sent from the Transaction Layer)<br>
> Via: SIP/2.0/TCP 123.30.188.104;branch=z9hG4bKb2d7.61f1d4b2.0;i=2<br>
> From: <<a href="mailto:sip%3A1004@123.30.188.104">sip:1004@123.30.188.104</a>>;tag=891604370<br>
> To: <<a href="mailto:sip%3A1001@123.30.188.104">sip:1001@123.30.188.104</a>><br>
> Call-ID: 5538bbe8-b226-77d1-f14e-8b9ff44f0afd<br>
> CSeq: 6081 INVITE<br>
> Content-Length: 0<br>
> Via: SIP/2.0/TCP 192.168.0.35:55150;rport=55150;received=113.160.24.110;branch=z9hG4bK891608784<br>
> Record-Route: <sip:123.30.188.104;transport=tcp;lr=on;did=817.c172;nat=yes><br>
><br>
><br>
> SIP/2.0 180 Ringing<br>
> Via: SIP/2.0/TCP 123.30.188.104;branch=z9hG4bKb2d7.61f1d4b2.0;i=2<br>
> From: <<a href="mailto:sip%3A1004@123.30.188.104">sip:1004@123.30.188.104</a>>;tag=891604370<br>
> To: <<a href="mailto:sip%3A1001@123.30.188.104">sip:1001@123.30.188.104</a>>;tag=1839963<br>
> Contact: <sip:1001@192.168.103.107:1059;transport=tcp><br>
> Call-ID: 5538bbe8-b226-77d1-f14e-8b9ff44f0afd<br>
> CSeq: 6081 INVITE<br>
> Content-Length: 0<br>
> Via: SIP/2.0/TCP 192.168.0.35:55150;rport=55150;received=113.160.24.110;branch=z9hG4bK891608784<br>
> Record-Route: <sip:123.30.188.104;transport=tcp;lr=on;did=817.c172;nat=yes><br>
> Require: 100rel<br>
> RSeq: 4539<br>
> Allow: ACK, BYE, CANCEL, INVITE, MESSAGE, NOTIFY, OPTIONS, PRACK, REFER, UPDATE<br>
><br>
><br>
> PRACK sip:1001@192.168.103.107:1059;transport=tcp SIP/2.0<br>
> Via: SIP/2.0/TCP 123.30.188.104;branch=z9hG4bK82d7.8af0dc21.0;i=2<br>
> Via: SIP/2.0/TCP 192.168.0.35:55150;received=113.160.24.110;branch=z9hG4bK891604861;rport=55150<br>
> From: <<a href="mailto:sip%3A1004@123.30.188.104">sip:1004@123.30.188.104</a>>;tag=891604370<br>
> To: <<a href="mailto:sip%3A1001@123.30.188.104">sip:1001@123.30.188.104</a>>;tag=1839963<br>
> Contact: <sip:1004@192.168.0.35:55150;alias=113.160.24.110~55150~2;transport=tcp>;+g.oma.sip-im;language="en,fr"<br>
> Call-ID: 5538bbe8-b226-77d1-f14e-8b9ff44f0afd<br>
> CSeq: 6082 PRACK<br>
> Content-Length: 0<br>
> Max-Forwards: 16<br>
> Subject: FIXME<br>
> Allow: INVITE, ACK, CANCEL, BYE, MESSAGE, OPTIONS, NOTIFY, PRACK, UPDATE, REFER<br>
> Privacy: none<br>
> P-Access-Network-Info: ADSL;utran-cell-id-3gpp=00000000<br>
> User-Agent: IM-client/OMA1.0 Boghe/v2.0.130.804<br>
> RAck: 4539 6081 INVITE<br>
><br>
><br>
> SIP/2.0 200 OK<br>
> Via: SIP/2.0/TCP 123.30.188.104;branch=z9hG4bK82d7.8af0dc21.0;i=2<br>
> From: <<a href="mailto:sip%3A1004@123.30.188.104">sip:1004@123.30.188.104</a>>;tag=891604370<br>
> To: <<a href="mailto:sip%3A1001@123.30.188.104">sip:1001@123.30.188.104</a>>;tag=1839963<br>
> Contact: <sip:1001@192.168.103.107:1059;transport=tcp><br>
> Call-ID: 5538bbe8-b226-77d1-f14e-8b9ff44f0afd<br>
> CSeq: 6082 PRACK<br>
> Content-Length: 0<br>
> Via: SIP/2.0/TCP 192.168.0.35:55150;rport=55150;received=113.160.24.110;branch=z9hG4bK891604861<br>
><br>
><br>
> SIP/2.0 200 OK<br>
> Via: SIP/2.0/TCP 123.30.188.104;branch=z9hG4bKb2d7.61f1d4b2.0;i=2<br>
> From: <<a href="mailto:sip%3A1004@123.30.188.104">sip:1004@123.30.188.104</a>>;tag=891604370<br>
> To: <<a href="mailto:sip%3A1001@123.30.188.104">sip:1001@123.30.188.104</a>>;tag=1839963<br>
> Contact: <sip:1001@192.168.103.107:1059;transport=tcp><br>
> Call-ID: 5538bbe8-b226-77d1-f14e-8b9ff44f0afd<br>
> CSeq: 6081 INVITE<br>
> Content-Type: application/sdp<br>
> Content-Length: 315<br>
> Via: SIP/2.0/TCP 192.168.0.35:55150;rport=55150;received=113.160.24.110;branch=z9hG4bK891608784<br>
> Record-Route: <sip:123.30.188.104;transport=tcp;lr=on;did=817.c172;nat=yes><br>
> Allow: ACK, BYE, CANCEL, INVITE, MESSAGE, NOTIFY, OPTIONS, PRACK, REFER, UPDATE<br>
><br>
> v=0<br>
> o=doubango 1983 678901 IN IP4 192.168.103.107<br>
> s=-<br>
> c=IN IP4 192.168.103.107<br>
> t=0 0<br>
> m=message 1060 TCP/MSRP *<br>
> c=IN IP4 192.168.103.107<br>
> a=path:msrp://<a href="http://192.168.103.107:1060/1838028;tcp" target="_blank">192.168.103.107:1060/1838028;tcp</a><br>
> a=connection:new<br>
> a=setup:active<br>
> a=accept-types:message/CPIM<br>
> a=accept-wrapped-types:application/octet-stream<br>
> a=recvonly<br>
><br>
> ACK sip:1001@192.168.103.107:1059;transport=tcp SIP/2.0<br>
> Via: SIP/2.0/TCP 123.30.188.104;branch=z9hG4bKcydzigwkX;i=2<br>
> Via: SIP/2.0/TCP 192.168.0.35:55150;received=113.160.24.110;branch=z9hG4bK891589177;rport=55150<br>
> From: <<a href="mailto:sip%3A1004@123.30.188.104">sip:1004@123.30.188.104</a>>;tag=891604370<br>
> To: <<a href="mailto:sip%3A1001@123.30.188.104">sip:1001@123.30.188.104</a>>;tag=1839963<br>
> Contact: <sip:1004@192.168.0.35:55150;alias=113.160.24.110~55150~2;transport=tcp>;+g.oma.sip-im;language="en,fr"<br>
> Call-ID: 5538bbe8-b226-77d1-f14e-8b9ff44f0afd<br>
> CSeq: 6081 ACK<br>
> Content-Length: 0<br>
> Max-Forwards: 16<br>
> Subject: FIXME<br>
> Allow: INVITE, ACK, CANCEL, BYE, MESSAGE, OPTIONS, NOTIFY, PRACK, UPDATE, REFER<br>
> Privacy: none<br>
> P-Access-Network-Info: ADSL;utran-cell-id-3gpp=00000000<br>
> User-Agent: IM-client/OMA1.0 Boghe/v2.0.130.804<br>
><br>
><br>
> BYE sip:1001@192.168.103.107:1059;transport=tcp SIP/2.0<br>
> Via: SIP/2.0/TCP 123.30.188.104;branch=z9hG4bK92d7.e0554b27.0;i=2<br>
> Via: SIP/2.0/TCP 192.168.0.35:55150;received=113.160.24.110;branch=z9hG4bK891605340;rport=55150<br>
> From: <<a href="mailto:sip%3A1004@123.30.188.104">sip:1004@123.30.188.104</a>>;tag=891604370<br>
> To: <<a href="mailto:sip%3A1001@123.30.188.104">sip:1001@123.30.188.104</a>>;tag=1839963<br>
> Call-ID: 5538bbe8-b226-77d1-f14e-8b9ff44f0afd<br>
> CSeq: 6083 BYE<br>
> Content-Length: 0<br>
> Max-Forwards: 16<br>
> Accept-Contact: *;+g.oma.sip-im<br>
> Accept-Contact: *;language="en,fr"<br>
> Subject: FIXME<br>
> Allow: INVITE, ACK, CANCEL, BYE, MESSAGE, OPTIONS, NOTIFY, PRACK, UPDATE, REFER<br>
> Privacy: none<br>
> P-Access-Network-Info: ADSL;utran-cell-id-3gpp=00000000<br>
> User-Agent: IM-client/OMA1.0 Boghe/v2.0.130.804<br>
> P-Preferred-Identity: <<a href="mailto:sip%3A1004@123.30.188.104">sip:1004@123.30.188.104</a>><br>
><br>
><br>
> SIP/2.0 200 OK<br>
> Via: SIP/2.0/TCP 123.30.188.104;branch=z9hG4bK92d7.e0554b27.0;i=2<br>
> From: <<a href="mailto:sip%3A1004@123.30.188.104">sip:1004@123.30.188.104</a>>;tag=891604370<br>
> To: <<a href="mailto:sip%3A1001@123.30.188.104">sip:1001@123.30.188.104</a>>;tag=1839963<br>
> Contact: <sip:1001@192.168.103.107:1059;transport=tcp><br>
> Call-ID: 5538bbe8-b226-77d1-f14e-8b9ff44f0afd<br>
> CSeq: 6083 BYE<br>
> Content-Length: 0<br>
> Via: SIP/2.0/TCP 192.168.0.35:55150;rport=55150;received=113.160.24.110;branch=z9hG4bK891605340<br>
><br>
> I run msrprelay and SIP server on same physical server with IP: 123.30.188.104.<br>
><br>
><br>
><br>
><br>
</div></div><div class="HOEnZb"><div class="h5">> From: Saúl Ibarra Corretgé <<a href="mailto:saul@ag-projects.com">saul@ag-projects.com</a>><br>
> To: OpenSIPS users mailling list <<a href="mailto:users@lists.opensips.org">users@lists.opensips.org</a>><br>
> Sent: Monday, February 18, 2013 3:10 PM<br>
> Subject: Re: [OpenSIPS-Users] msrp relay<br>
><br>
><br>
> On Feb 18, 2013, at 5:03 AM, nguyen khue wrote:<br>
><br>
> > Hi all,<br>
> ><br>
> > How I can integrates msrprelay (<a href="http://msrprelay.org" target="_blank">msrprelay.org</a>) with opensips to make File Transfer session between SIP end-points located behind NAT?. Please guide me.<br>
> > I tested file transfer between two SIP end-points in LAN and it worked successful.<br>
> ><br>
><br>
> What problems did you ran into? Did you follow the installation guide <a href="http://msrprelay.org/projects/msrprelay/wiki/InstallationGuide" target="_blank">http://msrprelay.org/projects/msrprelay/wiki/InstallationGuide</a> ?<br>
><br>
> Regards,<br>
><br>
> --<br>
> Saúl Ibarra Corretgé<br>
> AG Projects<br>
><br>
><br>
><br>
><br>
> _______________________________________________<br>
> Users mailing list<br>
> <a href="mailto:Users@lists.opensips.org">Users@lists.opensips.org</a><br>
> <a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br>
><br>
><br>
> _______________________________________________<br>
> Users mailing list<br>
> <a href="mailto:Users@lists.opensips.org">Users@lists.opensips.org</a><br>
> <a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br>
<br>
--<br>
Saúl Ibarra Corretgé<br>
AG Projects<br>
<br>
<br>
<br>
<br>
_______________________________________________<br>
Users mailing list<br>
<a href="mailto:Users@lists.opensips.org">Users@lists.opensips.org</a><br>
<a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br>Dani Popa
</div>