<html><head></head><body><div class="ydp3ab33935yahoo-style-wrap" style="font-family:arial;font-size:16px;"><div></div>
<div dir="ltr" data-setdir="false">I have fixed most of the issues I had. I think that in the process of testing I mixed up an ie<->ei. Things are set up properly now and audio is flowing to the client on my mobile phone.</div><div dir="ltr" data-setdir="false"><br></div><div dir="ltr" data-setdir="false">Thanks for the help.</div><div dir="ltr" data-setdir="false"><br></div><div dir="ltr" data-setdir="false">Gavin<br></div><div><br></div>
</div><div id="ydpeed3c161yahoo_quoted_2262589201" class="ydpeed3c161yahoo_quoted">
<div style="font-family:'Helvetica Neue', Helvetica, Arial, sans-serif;font-size:13px;color:#26282a;">
<div>
On Wednesday, April 19, 2023 at 02:19:44 PM ADT, Gavin Murphy <iiagavin@aim.com> wrote:
</div>
<div><br></div>
<div><br></div>
<div><div id="ydpeed3c161yiv4811245097"><div><div style="font-family:arial;font-size:16px;" class="ydpeed3c161yiv4811245097ydpad927ad2yahoo-style-wrap"><div></div>
<div dir="ltr">So I did remember that the rtpproxy_offer and rtpproxy_answer functions can take an IP address as a second parameter. That was able to address the SDP issue in the 183.</div><div dir="ltr"><br clear="none"></div><div dir="ltr">However, I am still not getting audio flowing to the client. I have a suspicion that it's related to the SDP on the incoming INVITE having a connection address of 192.0.0.2, and rtpproxy being unable to route to that address. I though that I could call fix_nated_sdp(2) ahead of the call to rtpproxy_offer() in order to adjust the SDP before rtpproxy got hold of it, but that results in a mangled connection line with the client address and the private address getting concatenated in the resulting SDP (e.g. c: IN IP4 72.1.2.3.4192.168.2.251).</div><div dir="ltr"><br clear="none"></div><div dir="ltr">Is there any way to address this? I was hoping that the client I'm using (ZoiPer) might support STUN/TURN/ICE, but it doesn't appear that it does.</div><div dir="ltr"><br clear="none"></div><div dir="ltr">Thanks,</div><div dir="ltr"><br clear="none"></div><div dir="ltr">Gavin<br clear="none"></div><div><br clear="none"></div>
</div><div id="ydpeed3c161yiv4811245097yqt09235" class="ydpeed3c161yiv4811245097yqt0555978323"><div id="ydpeed3c161yiv4811245097ydpbeb9261ayahoo_quoted_2457960773" class="ydpeed3c161yiv4811245097ydpbeb9261ayahoo_quoted">
<div style="font-family:'Helvetica Neue', Helvetica, Arial, sans-serif;font-size:13px;color:#26282a;">
<div>
On Wednesday, April 19, 2023 at 02:09:13 PM ADT, Gavin Murphy via Users <users@lists.opensips.org> wrote:
</div>
<div><br clear="none"></div>
<div><br clear="none"></div>
<div><div dir="ltr">Yes. I am assuming the rtpproxy_offer("ei") should be used when the INVITE comes in from the external network, and rtpproxy_answer("ie") should be used in the onreply_route to handle the 183 and 200.<br clear="none"></div><div dir="ltr"><br clear="none"></div><div dir="ltr">Gavin<br clear="none"></div><div dir="ltr"><br clear="none"></div><div dir="ltr"><br clear="none"></div><div dir="ltr"><br clear="none"></div><div dir="ltr">Sent via BlackBerry Hub+ Inbox for Android<br clear="none"></div><div dir="ltr"><br clear="none"></div><div dir="ltr"><br clear="none"></div><div dir="ltr"> Original Message <br clear="none"></div><div dir="ltr"><br clear="none"></div><div dir="ltr"><br clear="none"></div><div dir="ltr">From: <a shape="rect" href="mailto:callum.guy@x-on.co.uk" rel="nofollow" target="_blank">callum.guy@x-on.co.uk</a><br clear="none"></div><div dir="ltr">Sent: April 19, 2023 1:12 p.m.<br clear="none"></div><div dir="ltr">To: <a shape="rect" href="mailto:iiagavin@aim.com" rel="nofollow" target="_blank">iiagavin@aim.com</a><br clear="none"></div><div dir="ltr">Cc: <a shape="rect" href="mailto:users@lists.opensips.org" rel="nofollow" target="_blank">users@lists.opensips.org</a><br clear="none"></div><div dir="ltr">Subject: Re: [OpenSIPS-Users] NAT & RTPProxy<br clear="none"></div><div dir="ltr"><br clear="none"></div><div dir="ltr"><br clear="none"></div><div dir="ltr">Just to confirm, for a call from the client to the application server<br clear="none"></div><div dir="ltr">you should be running rtp_offer("ei") in the main route for a non-LR<br clear="none"></div><div dir="ltr">INVITE and rtp_answer("ie") in the on reply route (when handling the<br clear="none"></div><div dir="ltr">183 response).<br clear="none"></div><div dir="ltr"><br clear="none"></div><div dir="ltr">Is that what you're doing?<br clear="none"></div><div dir="ltr"><br clear="none"></div><div dir="ltr">On Wed, 19 Apr 2023 at 17:08, Gavin Murphy <<a shape="rect" href="mailto:iiagavin@aim.com" rel="nofollow" target="_blank">iiagavin@aim.com</a>> wrote:<br clear="none"></div><div dir="ltr">><br clear="none"></div><div dir="ltr">> Hi Callum,<br clear="none"></div><div dir="ltr">><br clear="none"></div><div dir="ltr">> thanks for the additional info. I removed the -A option from the rtpproxy command line but am essentially getting the same result. The INVITE does get the address translated correctly, such that it's the rtpproxy's internal IP address when the INVITE is forwarded on to the application server.<br clear="none"></div><div dir="ltr">><br clear="none"></div><div dir="ltr">> However when a 183 comes back from the application server, the IP is updated to the internal address, regardless of which i/e combination I use. I can't seem to get it to populate the external IP.<br clear="none"></div><div dir="ltr">><br clear="none"></div><div dir="ltr">> Thoughts?<br clear="none"></div><div dir="ltr">><br clear="none"></div><div dir="ltr">> Gavin<br clear="none"></div><div dir="ltr">><br clear="none"></div><div dir="ltr">> On Wednesday, April 19, 2023 at 12:52:04 PM ADT, Callum Guy <<a shape="rect" href="mailto:callum.guy@x-on.co.uk" rel="nofollow" target="_blank">callum.guy@x-on.co.uk</a>> wrote:<br clear="none"></div><div dir="ltr">><br clear="none"></div><div dir="ltr">><br clear="none"></div><div dir="ltr">> Hi Gavin,<br clear="none"></div><div dir="ltr">><br clear="none"></div><div dir="ltr">> Its been a while since i used rtpproxy (favouring RTPEngine these<br clear="none"></div><div dir="ltr">> days) however I believe the main issue may be the listen option - this<br clear="none"></div><div dir="ltr">> should be "-l [internal]/[external]"<br clear="none"></div><div dir="ltr">><br clear="none"></div><div dir="ltr">> -l 192.168.2.251/142.1.2.3<br clear="none"></div><div dir="ltr">><br clear="none"></div><div dir="ltr">> Once implemented you do indeed need to set ei/ie/ee etc in the offer<br clear="none"></div><div dir="ltr">> options to specify which address you wish to present for each scenario<br clear="none"></div><div dir="ltr">> you are handling.<br clear="none"></div><div dir="ltr">><br clear="none"></div><div dir="ltr">> This also applies to -A however you should only need that if running<br clear="none"></div><div dir="ltr">> those addresses behind NAT.<br clear="none"></div><div dir="ltr">><br clear="none"></div><div dir="ltr">> Hope that helps to move you forward!<br clear="none"></div><div dir="ltr">><br clear="none"></div><div dir="ltr">> Callum<br clear="none"></div><div dir="ltr">><br clear="none"></div><div dir="ltr">> On Wed, 19 Apr 2023 at 15:01, Gavin Murphy <<a shape="rect" href="mailto:iiagavin@aim.com" rel="nofollow" target="_blank">iiagavin@aim.com</a>> wrote:<br clear="none"></div><div dir="ltr">> ><br clear="none"></div><div dir="ltr">> > Hi Callum,<br clear="none"></div><div dir="ltr">> ><br clear="none"></div><div dir="ltr">> > yes, I do have rtpproxy set up in bridged mode. It is run using the following command (public IPs changed):<br clear="none"></div><div dir="ltr">> ><br clear="none"></div><div dir="ltr">> > rtpproxy -F -s udp:127.0.0.1:7722 -l 192.168.2.251/192.168.2.251 -A 142.1.2.3/142.1.2.3 -m 10000 -M 10100<br clear="none"></div><div dir="ltr">> ><br clear="none"></div><div dir="ltr">> > The client source IP seen by opensips is 72.1.2.3, and the SDP has a connection IP of 192.0.0.2.<br clear="none"></div><div dir="ltr">> ><br clear="none"></div><div dir="ltr">> > In opensips' route configuration, when the incoming request is determined to be an INVITE, I call rtpproxy_offer(). I've tried passing no flags as well as every combination of "i" and "e". In each case the SDP's connection IP that is passed to the internal server is rtpproxy's advertised address (142.1.2.3), as it seems to think that the 192.0.0.2 is an internal address that needs to be converted to the advertised address, even when the "ei" flags are passed in rtpproxy_offer(). I've also tried passing the "s", "c", and "o" flags, with the same fundamental issue each time.<br clear="none"></div><div dir="ltr">> ><br clear="none"></div><div dir="ltr">> > On the SDP answer, I am calling rtpproxy_answer("ie"), and that seems to result in no update to the SDP. The same IP (from the application server) that comes in is the one that is sent back to the client. It should be the public IP address (142.1.2.3).<br clear="none"></div><div dir="ltr">> ><br clear="none"></div><div dir="ltr">> > Thoughts?<br clear="none"></div><div dir="ltr">> ><br clear="none"></div><div dir="ltr">> > Thanks,<br clear="none"></div><div dir="ltr">> ><br clear="none"></div><div dir="ltr">> > Gavin<br clear="none"></div><div dir="ltr">> ><br clear="none"></div><div dir="ltr">> ><br clear="none"></div><div dir="ltr">> > On Wednesday, April 19, 2023 at 07:06:54 AM ADT, Callum Guy <<a shape="rect" href="mailto:callum.guy@x-on.co.uk" rel="nofollow" target="_blank">callum.guy@x-on.co.uk</a>> wrote:<br clear="none"></div><div dir="ltr">> ><br clear="none"></div><div dir="ltr">> ><br clear="none"></div><div dir="ltr">> > Hi Gavin,<br clear="none"></div><div dir="ltr">> ><br clear="none"></div><div dir="ltr">> > Using an RTP proxy is a good approach, you'll need to set it up in<br clear="none"></div><div dir="ltr">> > bridge mode so that it is aware of the internal and external addresses<br clear="none"></div><div dir="ltr">> > so that it can present the public IP to the client and private to the<br clear="none"></div><div dir="ltr">> > application server.<br clear="none"></div><div dir="ltr">> ><br clear="none"></div><div dir="ltr">> > You probably don't need fix_nated_sdp as rtpproxy/rtpengine will do<br clear="none"></div><div dir="ltr">> > that for you, you'll just need to tell it which address to use which<br clear="none"></div><div dir="ltr">> > differs for each product.<br clear="none"></div><div dir="ltr">> ><br clear="none"></div><div dir="ltr">> > Good luck!<br clear="none"></div><div dir="ltr">> ><br clear="none"></div><div dir="ltr">> > Callum<br clear="none"></div><div dir="ltr">> ><br clear="none"></div><div dir="ltr">> > On Wed, 19 Apr 2023 at 06:39, Gavin Murphy via Users<br clear="none"></div><div dir="ltr">> > <<a shape="rect" href="mailto:users@lists.opensips.org" rel="nofollow" target="_blank">users@lists.opensips.org</a>> wrote:<br clear="none"></div><div dir="ltr">> > ><br clear="none"></div><div dir="ltr">> > > Hello,<br clear="none"></div><div dir="ltr">> > ><br clear="none"></div><div dir="ltr">> > > I'm trying to set up an instance of opensips to support a testing SIP phone calling into my simulated network. The client is running from a mobile phone. The connection from the client comes in from the public network, but the client sees its own IP as private (192.0.0.2). My test network is running on virtual machines on my laptop, and is behind a NATed home router, so all of the VMs are in private IP space (192.168.x.x). It looks something like this:<br clear="none"></div><div dir="ltr">> > ><br clear="none"></div><div dir="ltr">> > > client -> mobile network (NAT) -> home router (NAT) -> opensips -> application server<br clear="none"></div><div dir="ltr">> > ><br clear="none"></div><div dir="ltr">> > > I am having trouble relaying the media from the network to the client. I have made various attempts of using the rtpproxy and the matmodule, but nothing has been successful so far. When using rtpproxy it writes the SDP going back to the client in the 183 with the internal IP. But if I just use fix_nated_sdp() the media doesn't go through the proxy server. If I try to use both (fix_nated_sdp() followed by rtpproxy_answer()), rtpproxy doesn't properly re-write the SDP (it ends up with a concatenation of the the private and the public advertised address.<br clear="none"></div><div dir="ltr">> > ><br clear="none"></div><div dir="ltr">> > > Anyone have any advice or experience with this kind of setup?<br clear="none"></div><div dir="ltr">> > ><br clear="none"></div><div dir="ltr">> > > Thanks,<br clear="none"></div><div dir="ltr">> > ><br clear="none"></div><div dir="ltr">> > > Gavin<br clear="none"></div><div dir="ltr">> > > _______________________________________________<br clear="none"></div><div dir="ltr">> > > Users mailing list<br clear="none"></div><div dir="ltr">> > > <a shape="rect" href="mailto:Users@lists.opensips.org" rel="nofollow" target="_blank">Users@lists.opensips.org</a><br clear="none"></div><div dir="ltr">> > > <a shape="rect" href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" rel="nofollow" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br clear="none"></div><div dir="ltr">> ><br clear="none"></div><div dir="ltr">> > --<br clear="none"></div><div dir="ltr">> ><br clear="none"></div><div dir="ltr">> ><br clear="none"></div><div dir="ltr">> ><br clear="none"></div><div dir="ltr">> ><br clear="none"></div><div dir="ltr">> ><br clear="none"></div><div dir="ltr">> ><br clear="none"></div><div dir="ltr">> > *0333 332 0000 | x-on.co.uk <<a shape="rect" href="https://www.x-on.co.uk" rel="nofollow" target="_blank">https://www.x-on.co.uk</a>> | **<br clear="none"></div><div dir="ltr">> > <<a shape="rect" href="https://www.linkedin.com/company/x-on" rel="nofollow" target="_blank">https://www.linkedin.com/company/x-on</a>> <<a shape="rect" href="https://www.facebook.com/XonTel" rel="nofollow" target="_blank">https://www.facebook.com/XonTel</a>><br clear="none"></div><div dir="ltr">> > <<a shape="rect" href="https://twitter.com/xonuk" rel="nofollow" target="_blank">https://twitter.com/xonuk</a>> ** | **Practice Index Reviews<br clear="none"></div><div dir="ltr">> > <<a shape="rect" href="https://practiceindex.co.uk/gp/x-on" rel="nofollow" target="_blank">https://practiceindex.co.uk/gp/x-on</a>>*<br clear="none"></div><div dir="ltr">> ><br clear="none"></div><div dir="ltr">> > *Our new office address: 22 Riduna<br clear="none"></div><div dir="ltr">> > Park, Melton IP12 1QT.*<br clear="none"></div><div dir="ltr">> ><br clear="none"></div><div dir="ltr">> > X-on<br clear="none"></div><div dir="ltr">> > is a trading name of Storacall Technology Ltd<br clear="none"></div><div dir="ltr">> > a limited company registered in<br clear="none"></div><div dir="ltr">> > England and Wales.<br clear="none"></div><div dir="ltr">> ><br clear="none"></div><div dir="ltr">> > Registered Office :<br clear="none"></div><div dir="ltr">> > Glebe Farm, Down Street, Dummer, Basingstoke, Hampshire, England RG25 2AD.<br clear="none"></div><div dir="ltr">> > Company Registration No. 2578478.<br clear="none"></div><div dir="ltr">> ><br clear="none"></div><div dir="ltr">> > The information in this e-mail is<br clear="none"></div><div dir="ltr">> > confidential and for use by the addressee(s)<br clear="none"></div><div dir="ltr">> > only. If you are not the<br clear="none"></div><div dir="ltr">> > intended recipient, please notify X-on immediately on +44(0)333 332 0000<br clear="none"></div><div dir="ltr">> > and delete the<br clear="none"></div><div dir="ltr">> > message from your computer. If you are not a named addressee<br clear="none"></div><div dir="ltr">> > you must not use,<br clear="none"></div><div dir="ltr">> > disclose, disseminate, distribute, copy, print or reply<br clear="none"></div><div dir="ltr">> > to this email. Views<br clear="none"></div><div dir="ltr">> > or opinions expressed by an individual<br clear="none"></div><div dir="ltr">> > within this<br clear="none"></div><div dir="ltr">> > email may not necessarily<br clear="none"></div><div dir="ltr">> > reflect the views of X-on or its associated<br clear="none"></div><div dir="ltr">> > companies. Although X-on routinely<br clear="none"></div><div dir="ltr">> > screens for viruses, addressees should<br clear="none"></div><div dir="ltr">> > scan this email and any attachments<br clear="none"></div><div dir="ltr">> > for<br clear="none"></div><div dir="ltr">> > viruses. X-on makes no<br clear="none"></div><div dir="ltr">> > representation or warranty as to the absence of viruses<br clear="none"></div><div dir="ltr">> > in this email or<br clear="none"></div><div dir="ltr">> > any attachments.<br clear="none"></div><div dir="ltr">><br clear="none"></div><div dir="ltr">> ><br clear="none"></div><div dir="ltr">> ><br clear="none"></div><div dir="ltr">> ><br clear="none"></div><div dir="ltr">> ><br clear="none"></div><div dir="ltr">> ><br clear="none"></div><div dir="ltr">> ><br clear="none"></div><div dir="ltr">> ><br clear="none"></div><div dir="ltr">> ><br clear="none"></div><div dir="ltr">><br clear="none"></div><div dir="ltr">> --<br clear="none"></div><div dir="ltr">><br clear="none"></div><div dir="ltr">><br clear="none"></div><div dir="ltr">><br clear="none"></div><div dir="ltr">><br clear="none"></div><div dir="ltr">><br clear="none"></div><div dir="ltr">><br clear="none"></div><div dir="ltr">> *0333 332 0000 | x-on.co.uk <<a shape="rect" href="https://www.x-on.co.uk" rel="nofollow" target="_blank">https://www.x-on.co.uk</a>> | **<br clear="none"></div><div dir="ltr">> <<a shape="rect" href="https://www.linkedin.com/company/x-on" rel="nofollow" target="_blank">https://www.linkedin.com/company/x-on</a>> <<a shape="rect" href="https://www.facebook.com/XonTel" rel="nofollow" target="_blank">https://www.facebook.com/XonTel</a>><br clear="none"></div><div dir="ltr">> <<a shape="rect" href="https://twitter.com/xonuk" rel="nofollow" target="_blank">https://twitter.com/xonuk</a>> ** | **Practice Index Reviews<br clear="none"></div><div dir="ltr">> <<a shape="rect" href="https://practiceindex.co.uk/gp/x-on" rel="nofollow" target="_blank">https://practiceindex.co.uk/gp/x-on</a>>*<br clear="none"></div><div dir="ltr">><br clear="none"></div><div dir="ltr">> *Our new office address: 22 Riduna<br clear="none"></div><div dir="ltr">> Park, Melton IP12 1QT.*<br clear="none"></div><div dir="ltr">><br clear="none"></div><div dir="ltr">> X-on<br clear="none"></div><div dir="ltr">> is a trading name of Storacall Technology Ltd<br clear="none"></div><div dir="ltr">> a limited company registered in<br clear="none"></div><div dir="ltr">> England and Wales.<br clear="none"></div><div dir="ltr">><br clear="none"></div><div dir="ltr">> Registered Office :<br clear="none"></div><div dir="ltr">> Glebe Farm, Down Street, Dummer, Basingstoke, Hampshire, England RG25 2AD.<br clear="none"></div><div dir="ltr">> Company Registration No. 2578478.<br clear="none"></div><div dir="ltr">><br clear="none"></div><div dir="ltr">> The information in this e-mail is<br clear="none"></div><div dir="ltr">> confidential and for use by the addressee(s)<br clear="none"></div><div dir="ltr">> only. If you are not the<br clear="none"></div><div dir="ltr">> intended recipient, please notify X-on immediately on +44(0)333 332 0000<br clear="none"></div><div dir="ltr">> and delete the<br clear="none"></div><div dir="ltr">> message from your computer. If you are not a named addressee<br clear="none"></div><div dir="ltr">> you must not use,<br clear="none"></div><div dir="ltr">> disclose, disseminate, distribute, copy, print or reply<br clear="none"></div><div dir="ltr">> to this email. Views<br clear="none"></div><div dir="ltr">> or opinions expressed by an individual<br clear="none"></div><div dir="ltr">> within this<br clear="none"></div><div dir="ltr">> email may not necessarily<br clear="none"></div><div dir="ltr">> reflect the views of X-on or its associated<br clear="none"></div><div dir="ltr">> companies. Although X-on routinely<br clear="none"></div><div dir="ltr">> screens for viruses, addressees should<br clear="none"></div><div dir="ltr">> scan this email and any attachments<br clear="none"></div><div dir="ltr">> for<br clear="none"></div><div dir="ltr">> viruses. X-on makes no<br clear="none"></div><div dir="ltr">> representation or warranty as to the absence of viruses<br clear="none"></div><div dir="ltr">> in this email or<br clear="none"></div><div dir="ltr">> any attachments.<br clear="none"></div><div dir="ltr">><br clear="none"></div><div dir="ltr">><br clear="none"></div><div dir="ltr">><br clear="none"></div><div dir="ltr">><br clear="none"></div><div dir="ltr">><br clear="none"></div><div dir="ltr">><br clear="none"></div><div dir="ltr">><br clear="none"></div><div dir="ltr">><br clear="none"></div><div dir="ltr"><br clear="none"></div><div dir="ltr">--<br clear="none"></div><div dir="ltr"><br clear="none"></div><div dir="ltr"><br clear="none"></div><div dir="ltr"><br clear="none"></div><div dir="ltr"><br clear="none"></div><div dir="ltr"><br clear="none"></div><div dir="ltr"><br clear="none"></div><div dir="ltr">*0333 332 0000 | x-on.co.uk <<a shape="rect" href="https://www.x-on.co.uk" rel="nofollow" target="_blank">https://www.x-on.co.uk</a>> | **<br clear="none"></div><div dir="ltr"><<a shape="rect" href="https://www.linkedin.com/company/x-on" rel="nofollow" target="_blank">https://www.linkedin.com/company/x-on</a>> <<a shape="rect" href="https://www.facebook.com/XonTel" rel="nofollow" target="_blank">https://www.facebook.com/XonTel</a>><br clear="none"></div><div dir="ltr"> <<a shape="rect" href="https://twitter.com/xonuk" rel="nofollow" target="_blank">https://twitter.com/xonuk</a>> ** | **Practice Index Reviews<br clear="none"></div><div dir="ltr"><<a shape="rect" href="https://practiceindex.co.uk/gp/x-on" rel="nofollow" target="_blank">https://practiceindex.co.uk/gp/x-on</a>>*<br clear="none"></div><div dir="ltr"><br clear="none"></div><div dir="ltr">*Our new office address: 22 Riduna<br clear="none"></div><div dir="ltr">Park, Melton IP12 1QT.*<br clear="none"></div><div dir="ltr"><br clear="none"></div><div dir="ltr">X-on<br clear="none"></div><div dir="ltr">is a trading name of Storacall Technology Ltd<br clear="none"></div><div dir="ltr">a limited company registered in<br clear="none"></div><div dir="ltr">England and Wales.<br clear="none"></div><div dir="ltr"><br clear="none"></div><div dir="ltr">Registered Office :<br clear="none"></div><div dir="ltr">Glebe Farm, Down Street, Dummer, Basingstoke, Hampshire, England RG25 2AD.<br clear="none"></div><div dir="ltr">Company Registration No. 2578478.<br clear="none"></div><div dir="ltr"><br clear="none"></div><div dir="ltr">The information in this e-mail is<br clear="none"></div><div dir="ltr">confidential and for use by the addressee(s)<br clear="none"></div><div dir="ltr">only. If you are not the<br clear="none"></div><div dir="ltr">intended recipient, please notify X-on immediately on +44(0)333 332 0000<br clear="none"></div><div dir="ltr">and delete the<br clear="none"></div><div dir="ltr">message from your computer. If you are not a named addressee<br clear="none"></div><div dir="ltr">you must not use,<br clear="none"></div><div dir="ltr">disclose, disseminate, distribute, copy, print or reply<br clear="none"></div><div dir="ltr">to this email. Views<br clear="none"></div><div dir="ltr">or opinions expressed by an individual<br clear="none"></div><div dir="ltr">within this<br clear="none"></div><div dir="ltr">email may not necessarily<br clear="none"></div><div dir="ltr">reflect the views of X-on or its associated<br clear="none"></div><div dir="ltr">companies. Although X-on routinely<br clear="none"></div><div dir="ltr">screens for viruses, addressees should<br clear="none"></div><div dir="ltr">scan this email and any attachments<br clear="none"></div><div dir="ltr">for<br clear="none"></div><div dir="ltr">viruses. X-on makes no<br clear="none"></div><div dir="ltr">representation or warranty as to the absence of viruses<br clear="none"></div><div dir="ltr">in this email or<br clear="none"></div><div dir="ltr">any attachments.<br clear="none"></div><div dir="ltr"><br clear="none"></div><div dir="ltr"><br clear="none"></div><div dir="ltr"><br clear="none"></div><div dir="ltr"><br clear="none"></div><div dir="ltr"><br clear="none"></div><div dir="ltr"><br clear="none"></div><div dir="ltr"><br clear="none"></div><div dir="ltr"><br clear="none"></div><div dir="ltr">_______________________________________________<br clear="none"></div><div dir="ltr">Users mailing list<br clear="none"></div><div dir="ltr"><a shape="rect" href="mailto:Users@lists.opensips.org" rel="nofollow" target="_blank">Users@lists.opensips.org</a><br clear="none"></div><div dir="ltr"><a shape="rect" href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" rel="nofollow" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br clear="none"></div></div>
</div>
</div></div></div></div></div>
</div>
</div></body></html>