[OpenSIPS-Users] RTP proxy dialog impacted by async

2019-03-08 Thread Callum Guy 
Hi OpenSIPs Community,

I wanted to report an issue I discovered when attempting to use the
rtpproxy module, using the dialog backed rtpproxy_engage() function.
Finding that it was not engaging in certain scenarios I took a closer look
at the activity on the control port and discovered that OpenSIPS never sent
a request to open the session in this scenario.

To help illustrate, here is an example control port sequence of a properly
engaged call:

65098_11 *UR*8.8.8.8c9,8,0,3,101,13 *the-call-id* 192.168.153.223 10248
*from-tag*;1
65118_19 *LR*8.8.8.8c8,101 *the-call-id* 192.168.153.223 10248 *from-tag*;1
*to-tag*;1

In my scenario the *UR* (create session) request was never received.
Without claiming any expertise on the rtpproxy protocol this was clearly
not correct and the *LC* (update session) request could not locate a
session to act on.

Following a fairly lengthy investigation I traced the issue back to my
usage of the async() function where i was issuing the rtpproxy_engage()
request before calling async for another purpose. The solution was simply
to move the rtpproxy_engage() call to after the async method.

I'm happy that the issue is resolved for my requirements however I thought
I would share the experience to the list in case others found themselves
having a similar issue.

Thanks!

Callum

-- 





*0333 332   |  www.x-on.co.uk   |   ** 
    
   *


X-on
is a trading name of Storacall 
Technology Ltd a limited company registered in
England and Wales.


Registered Office : Avaland House, 110 London Road, Apsley, Hemel 
Hempstead,
Herts, HP3 9SD. Company Registration No. 2578478.

The 
information in this e-mail is confidential and for use by the addressee(s)

only. If you are not the intended recipient, please notify X-on immediately 
on +44(0)333 332  and delete the
message from your computer. If you are 
not a named addressee you must not use,
disclose, disseminate, distribute, 
copy, print or reply to this email. Views
or opinions expressed by an 
individual
within this email may not necessarily
reflect the views of X-on 
or its associated companies. Although X-on routinely
screens for viruses, 
addressees should scan this email and any attachments
for
viruses. X-on 
makes no representation or warranty as to the absence of viruses
in this 
email or any attachments.










___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] tls -> udp

2019-03-08 Thread Johan De Clercq 
Thanks for the additional clarification Bogdan.

Op do 7 mrt. 2019 om 10:48 schreef Bogdan-Andrei Iancu :

> Hi John,
>
> For (2), there is nothing special you need to do - the double_rr is by
> default enabled and you just need to do record_route() - opensips is
> automatically figure out that there is a protocol changing and do a
> double RR headers.
>
> Regarding (1) and (3) - the proto info in RURI/destination is overriding
> the info in forced socket - if you have a explicit UDP destination, but
> a TLS socket forced, the socket will be discarded and a proper one (UDP)
> will be found.
>
> Shortly said, you need only (1).
>
> Regards,
>
> Bogdan-Andrei Iancu
>
> OpenSIPS Founder and Developer
>https://www.opensips-solutions.com
> OpenSIPS Summit 2019
>https://www.opensips.org/events/Summit-2019Amsterdam/
>
> On 02/13/2019 11:15 AM, John Quick wrote:
> > Hi Johan,
> >
> > I've configured Proxy servers to do this a few times.
> > You should do the following:
> > 1) For Requests going from TLS to UDP, change any occurrence of
> > "transport=tls" in the R-URI parameters. I use the following to do this:
> > subst_uri('/transport=tls/transport=udp/I');
> >
> > 2) Make sure OpenSIPS adds correct Record-Route headers.
> > Default behaviour in this case is to add 2 RR headers when you call
> > record_route(). Make sure double_rr has not been disabled in the modparam
> > section.
> > One header describes the TLS socket and the other header describes the
> UDP
> > socket. These are needed for sequential Loose-Routed requests later in
> the
> > dialogue.
> >
> > 3) Just before you relay the request over UDP, call the
> force_send_socket()
> > function. For example:
> > force_send_socket(udp:12.34.56.78:5060);
> >
> > Hope this helps.
> >
> > John Quick
> > Smartvox Limited
> >
> >
> >
> > ___
> > Users mailing list
> > Users@lists.opensips.org
> > http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
>
> ___
> Users mailing list
> Users@lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] registrar lookup function

2019-03-08 Thread Pasan Meemaduma via Users 
 Hi Bogdan,
Thanks for the clarification. All good now.

On Friday, 8 March 2019, 1:52:18 PM GMT+5:30, Bogdan-Andrei Iancu 
 wrote:  
 
  Hi Pasan,
 
 It is about filtering based on SIP methods. During registration, an UAC may 
list the supported SIP methods for that registration (like INVITE, MESSAGE). If 
the filtering is activated during the lookup() for a SUBSCRIBE, the lookup will 
fail as the current methods does not match the supported methods in the 
registered contact.
 
 Regards,
  Bogdan-Andrei Iancu

OpenSIPS Founder and Developer
  https://www.opensips-solutions.com
OpenSIPS Summit 2019
  https://www.opensips.org/events/Summit-2019Amsterdam/
 On 03/08/2019 05:34 AM, Pasan Meemaduma via Users wrote:
  
 Hi Guys, 
  Would someone able to shed some light on the method filtering flag (m) in 
registrar lookup function do  ? I'm having trouble understanding its purpose. 
Can somone give me an example of how it works ? 
  registrar Module 
   
|  
|  
| 
  |  
registrar Module
  |

  |

  |

  
  
  
  Thank you.
  
  
 ___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users 
 
   ___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] registrar lookup function

2019-03-08 Thread Bogdan-Andrei Iancu 

Hi Pasan,

It is about filtering based on SIP methods. During registration, an UAC 
may list the supported SIP methods for that registration (like INVITE, 
MESSAGE). If the filtering is activated during the lookup() for a 
SUBSCRIBE, the lookup will fail as the current methods does not match 
the supported methods in the registered contact.


Regards,

Bogdan-Andrei Iancu

OpenSIPS Founder and Developer
  https://www.opensips-solutions.com
OpenSIPS Summit 2019
  https://www.opensips.org/events/Summit-2019Amsterdam/

On 03/08/2019 05:34 AM, Pasan Meemaduma via Users wrote:

Hi Guys,

Would someone able to shed some light on the method filtering flag (m) 
in registrar lookup function do ? I'm having trouble understanding its 
purpose. Can somone give me an example of how it works ?


registrar Module 







registrar Module





Thank you.


___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users


___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users