Re: [OpenSIPS-Users] where is has_sdp()

2011-05-10 Thread Jeff Chua
On Wed, May 11, 2011 at 2:37 AM, Bogdan-Andrei Iancu
 wrote:

> Replace the force_rtp_proxy from onreply_route with rtpproxy_answer() and
> the left force_rtp_proxy with rtpproxy_offer()

Bogdan,

Cool. I'll give that a try.

Thanks,
Jeff

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


Re: [OpenSIPS-Users] where is has_sdp()

2011-05-10 Thread Bogdan-Andrei Iancu

On 05/07/2011 07:25 PM, Jeff Chua wrote:

On Sat, May 7, 2011 at 12:51 AM, Bogdan-Andrei Iancu
  wrote:

Hi Jeff,

For a complete working script with NAT traversal, check the opensips virtual
machine (you can download it from the SourceForge download area of opensip
project).

Bogdan,

I've checked the config from the virtual machine, and it's still using
force_rtp_proxy where the new trunk/develop has replaced that with
rtpproxy_offer and rtpproxy_answer and I don't know how to make that
work. Where can I get the new config?

Hi Jeff,

Replace the force_rtp_proxy from onreply_route with rtpproxy_answer() 
and the left force_rtp_proxy with rtpproxy_offer()


Regards,
Bogdan

--
Bogdan-Andrei Iancu
OpenSIPS eBootcamp - 2nd of May 2011
OpenSIPS solutions and "know-how"


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


Re: [OpenSIPS-Users] mi_xmlrpc on FeeBSD amd64

2011-05-10 Thread Bogdan-Andrei Iancu

Hi Anton

http://download.ag-projects.com/XCAP/opensips-mi-proxy-1.0.4.tar.gz


Regards,
Bogdan


On 05/10/2011 03:33 PM, Anton Zagorskiy wrote:

Hi Bogdan,

Could you give a link to MI2FIFO proxy from ag projects?
Can't find it :(



-Original Message-
From: Bogdan-Andrei Iancu [mailto:bog...@opensips.org]
Sent: Friday, May 06, 2011 9:19 PM
To: users@lists.opensips.org; Anton Zagorskiy
Subject: Re: [OpenSIPS-Users] mi_xmlrpc on FeeBSD amd64

Hi Anton,

I remember facing a similar problem and the problem is somewhere in the
xmlrpc-c3 library :(

To be honest I was not able to get it work (or at least didn't pay to invest too
much time into it) and I uses the MI2FIFO proxy from ag projects.

Regards,
Bogdan

On 04/26/2011 01:39 PM, Anton Zagorskiy wrote:

Hi.

Does anyone use mi_xmlrpc module on FreeBSD amd64? (I have 8.2) I
can't get answer from OpenSIPS using menu 'MI Commands' in the
opensips-cp.

In a wireshark I see a normal TCP/IP session (socket isn't blocked).
But there are no any messages in a OpenSIPS log and in a mi_xmlrpc log
(i've setted modparam to /var/log/abyss.log)

Any suggestions?




--
Bogdan-Andrei Iancu
OpenSIPS eBootcamp - 2nd of May 2011
OpenSIPS solutions and "know-how"



--
Bogdan-Andrei Iancu
OpenSIPS eBootcamp - 2nd of May 2011
OpenSIPS solutions and "know-how"


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


[OpenSIPS-Users] Dialog timeout_avp kills call

2011-05-10 Thread duane . larson
I've got timeout_avp set up so that during the INVITE I set the timeout_avp  
to 120 seconds and during the ACK I set it to 7200 seconds. This seems to  
work for the Snom phones but I was testing a long call with the Blink  
client and after 2 hours the call is taken down. I am thinking this is  
because with the Snom phones the caller sends a Re-INVITE every 30 minutes  
and that resets the timeout_avp to 7200 seconds again. Should Blink be  
sending a Re-INVITE also? I want to be sure that my phone calls aren't  
being broken down after 2 hours.
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users


[OpenSIPS-Users] How to copy a specific header in 302 response

2011-05-10 Thread Montarou , Hélène
Hi,

 

Do you know how I can copy a specific header from a request into a 302 response?

 

Thank you,

 

Helene

 



From: Montarou, Hélène 
Sent: 8 mai 2011 21:11
To: users@lists.opensips.org
Subject: How to copy the Diversion header in 302 response

 

Hi,

 

I am using opensips-1.6.2-0 with the Diversion module.

 

I use the add_diversion('redirection') function and the Diversion header is 
added to the INVITE request.

However, I couldn't have it copied in the 302 response generated after the 
add-diversion is called.

 

Here is the code I am using:

 

ds_select_dst("2","4");

add_diversion("redirection");

sl_send_reply("302", "Redirect");

exit;

 

How can I force the signaling module to copy the Diversion header in the INVITE 
response 302?

 

Thank you,

 

Regards,

 

Helene

 

 

 

 

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


Re: [OpenSIPS-Users] mi_xmlrpc on FeeBSD amd64

2011-05-10 Thread Anton Zagorskiy
Hi Bogdan,

Could you give a link to MI2FIFO proxy from ag projects?
Can't find it :(


> -Original Message-
> From: Bogdan-Andrei Iancu [mailto:bog...@opensips.org]
> Sent: Friday, May 06, 2011 9:19 PM
> To: users@lists.opensips.org; Anton Zagorskiy
> Subject: Re: [OpenSIPS-Users] mi_xmlrpc on FeeBSD amd64
> 
> Hi Anton,
> 
> I remember facing a similar problem and the problem is somewhere in the
> xmlrpc-c3 library :(
> 
> To be honest I was not able to get it work (or at least didn't pay to invest 
> too
> much time into it) and I uses the MI2FIFO proxy from ag projects.
> 
> Regards,
> Bogdan
> 
> On 04/26/2011 01:39 PM, Anton Zagorskiy wrote:
> > Hi.
> >
> > Does anyone use mi_xmlrpc module on FreeBSD amd64? (I have 8.2) I
> > can't get answer from OpenSIPS using menu 'MI Commands' in the
> > opensips-cp.
> >
> > In a wireshark I see a normal TCP/IP session (socket isn't blocked).
> > But there are no any messages in a OpenSIPS log and in a mi_xmlrpc log
> > (i've setted modparam to /var/log/abyss.log)
> >
> > Any suggestions?
> >
> >
> 
> 
> --
> Bogdan-Andrei Iancu
> OpenSIPS eBootcamp - 2nd of May 2011
> OpenSIPS solutions and "know-how"


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


Re: [OpenSIPS-Users] dialog and acc

2011-05-10 Thread Denis Putyato
Bogdan

 

I understand, thank you

 

 

From: Bogdan-Andrei Iancu [mailto:bog...@opensips.org] 
Sent: Tuesday, May 10, 2011 12:56 PM
To: Denis Putyato
Cc: 'OpenSIPS users mailling list'
Subject: Re: [OpenSIPS-Users] dialog and acc

 

Hi Denis,

Yes, before the loose_route(), and it is critical as for sequential requests, 
the matching against existing dialogs is done somewhere inside loose_route() 
(via some callbacks). And when the dialog is matched, the dialog timeout is 
updated, so this is why you need to populate the AVP for dialog timeout before 
the loose_route.

Dialog related variables will be available available after the loose_route(), 
when the dialog was matched, so the dialog cotext is available.

Regards,
Bogdan

On 05/10/2011 11:51 AM, Denis Putyato wrote: 

Bogdan, one more question

You wrote “2) at ACK, before loose_route()”

Why before? Is this critical? 

I want to use $dlg_status variables to check if dialog exists (When received 
ACK), but in documentation said that this variables works only after 
loose_route() function

 

From: Bogdan-Andrei Iancu [mailto:bog...@opensips.org] 
Sent: Tuesday, May 10, 2011 12:43 PM
To: Denis Putyato
Cc: 'OpenSIPS users mailling list'
Subject: Re: [OpenSIPS-Users] dialog and acc

 

Hi Denis,

I can tell it works for sure, as I'm using this kind of dirty trick to cope 
with some buggy clients.

Best regards,
Bogdan

On 05/10/2011 06:42 AM, Denis Putyato wrote: 

Hello!

 

Thank you Bogdan, I will try you decision

 

From: Bogdan-Andrei Iancu [mailto:bog...@opensips.org] 
Sent: Friday, May 06, 2011 9:25 PM
To: OpenSIPS users mailling list
Cc: Denis Putyato
Subject: Re: [OpenSIPS-Users] dialog and acc

 

Hi Denis,

>From a proxy point of view, a 200OK means the dialog was establish. A proxy 
>cannot interfere with the ACK part - the acknowledgment is done between end 
>parties.

If the ACK is missing (in an established dialog), the callee party (according 
to RFC) must send a BYE (when finishing the 200 OK retransmission) to the 
caller.  This is something your callee doesn't do.

A simple work around is to use the dialog timeout in opensips:
1) at INVITE time, when dialog is created, set a 5 seconds timeout (dialog 
will be terminated by opensips, with BYE, in 5 secs after being established - 
do not forget to set the BYE_ON_TIMEOUT flag)
2) at ACK, before loose_route() set a new timeout to some long, long (3 
hours?) value.

So, if the ACK will mis, the 5 sec timeout will kick in and terminate the 
dialog; otherwise, opensips will prelong the dialog on ACK time.

Regards,
Bogdan

On 04/28/2011 03:06 PM, Denis Putyato wrote: 

Hello!

 

I noticed that cdr_flag in acc modules marks dialog for accounting as answered 
even there was no ACK on 200 OK.

As a result, I have acc record which has a big duration and status 200 OK.

 

Thank you for any help.

 

 

 

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








-- 
Bogdan-Andrei Iancu
OpenSIPS eBootcamp - 2nd of May 2011
OpenSIPS solutions and "know-how"







-- 
Bogdan-Andrei Iancu
OpenSIPS eBootcamp - 2nd of May 2011
OpenSIPS solutions and "know-how"






-- 
Bogdan-Andrei Iancu
OpenSIPS eBootcamp - 2nd of May 2011
OpenSIPS solutions and "know-how"
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users


Re: [OpenSIPS-Users] dialog and acc

2011-05-10 Thread Bogdan-Andrei Iancu

Hi Denis,

Yes, before the loose_route(), and it is critical as for sequential 
requests, the matching against existing dialogs is done somewhere inside 
loose_route() (via some callbacks). And when the dialog is matched, the 
dialog timeout is updated, so this is why you need to populate the AVP 
for dialog timeout before the loose_route.


Dialog related variables will be available available after the 
loose_route(), when the dialog was matched, so the dialog cotext is 
available.


Regards,
Bogdan

On 05/10/2011 11:51 AM, Denis Putyato wrote:


Bogdan, one more question

You wrote “2) at ACK, before loose_route()”

Why before? Is this critical?

I want to use $dlg_status variables to check if dialog exists (When 
received ACK), but in documentation said that this variables works 
only after loose_route() function


*From:*Bogdan-Andrei Iancu [mailto:bog...@opensips.org]
*Sent:* Tuesday, May 10, 2011 12:43 PM
*To:* Denis Putyato
*Cc:* 'OpenSIPS users mailling list'
*Subject:* Re: [OpenSIPS-Users] dialog and acc

Hi Denis,

I can tell it works for sure, as I'm using this kind of dirty trick to 
cope with some buggy clients.


Best regards,
Bogdan

On 05/10/2011 06:42 AM, Denis Putyato wrote:

Hello!

Thank you Bogdan, I will try you decision

*From:*Bogdan-Andrei Iancu [mailto:bog...@opensips.org]
*Sent:* Friday, May 06, 2011 9:25 PM
*To:* OpenSIPS users mailling list
*Cc:* Denis Putyato
*Subject:* Re: [OpenSIPS-Users] dialog and acc

Hi Denis,

From a proxy point of view, a 200OK means the dialog was establish. A 
proxy cannot interfere with the ACK part - the acknowledgment is done 
between end parties.


If the ACK is missing (in an established dialog), the callee party 
(according to RFC) must send a BYE (when finishing the 200 OK 
retransmission) to the caller.  This is something your callee doesn't do.


A simple work around is to use the dialog timeout in opensips:
1) at INVITE time, when dialog is created, set a 5 seconds timeout 
(dialog will be terminated by opensips, with BYE, in 5 secs after 
being established - do not forget to set the BYE_ON_TIMEOUT flag)
2) at ACK, before loose_route() set a new timeout to some long, 
long (3 hours?) value.


So, if the ACK will mis, the 5 sec timeout will kick in and terminate 
the dialog; otherwise, opensips will prelong the dialog on ACK time.


Regards,
Bogdan

On 04/28/2011 03:06 PM, Denis Putyato wrote:

Hello!

I noticed that cdr_flag in acc modules marks dialog for accounting as 
answered even there was no ACK on 200 OK.


As a result, I have acc record which has a big duration and status 200 OK.

Thank you for any help.

  
  
___

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





--
Bogdan-Andrei Iancu
OpenSIPS eBootcamp - 2nd of May 2011
OpenSIPS solutions and "know-how"




--
Bogdan-Andrei Iancu
OpenSIPS eBootcamp - 2nd of May 2011
OpenSIPS solutions and "know-how"



--
Bogdan-Andrei Iancu
OpenSIPS eBootcamp - 2nd of May 2011
OpenSIPS solutions and "know-how"

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


Re: [OpenSIPS-Users] dialog and acc

2011-05-10 Thread Denis Putyato
Bogdan, one more question

You wrote “2) at ACK, before loose_route()”

Why before? Is this critical? 

I want to use $dlg_status variables to check if dialog exists (When received 
ACK), but in documentation said that this variables works only after 
loose_route() function

 

From: Bogdan-Andrei Iancu [mailto:bog...@opensips.org] 
Sent: Tuesday, May 10, 2011 12:43 PM
To: Denis Putyato
Cc: 'OpenSIPS users mailling list'
Subject: Re: [OpenSIPS-Users] dialog and acc

 

Hi Denis,

I can tell it works for sure, as I'm using this kind of dirty trick to cope 
with some buggy clients.

Best regards,
Bogdan

On 05/10/2011 06:42 AM, Denis Putyato wrote: 

Hello!

 

Thank you Bogdan, I will try you decision

 

From: Bogdan-Andrei Iancu [mailto:bog...@opensips.org] 
Sent: Friday, May 06, 2011 9:25 PM
To: OpenSIPS users mailling list
Cc: Denis Putyato
Subject: Re: [OpenSIPS-Users] dialog and acc

 

Hi Denis,

>From a proxy point of view, a 200OK means the dialog was establish. A proxy 
>cannot interfere with the ACK part - the acknowledgment is done between end 
>parties.

If the ACK is missing (in an established dialog), the callee party (according 
to RFC) must send a BYE (when finishing the 200 OK retransmission) to the 
caller.  This is something your callee doesn't do.

A simple work around is to use the dialog timeout in opensips:
1) at INVITE time, when dialog is created, set a 5 seconds timeout (dialog 
will be terminated by opensips, with BYE, in 5 secs after being established - 
do not forget to set the BYE_ON_TIMEOUT flag)
2) at ACK, before loose_route() set a new timeout to some long, long (3 
hours?) value.

So, if the ACK will mis, the 5 sec timeout will kick in and terminate the 
dialog; otherwise, opensips will prelong the dialog on ACK time.

Regards,
Bogdan

On 04/28/2011 03:06 PM, Denis Putyato wrote: 

Hello!

 

I noticed that cdr_flag in acc modules marks dialog for accounting as answered 
even there was no ACK on 200 OK.

As a result, I have acc record which has a big duration and status 200 OK.

 

Thank you for any help.

 

 

 

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







-- 
Bogdan-Andrei Iancu
OpenSIPS eBootcamp - 2nd of May 2011
OpenSIPS solutions and "know-how"






-- 
Bogdan-Andrei Iancu
OpenSIPS eBootcamp - 2nd of May 2011
OpenSIPS solutions and "know-how"
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users


Re: [OpenSIPS-Users] dialog and acc

2011-05-10 Thread Bogdan-Andrei Iancu

Hi Denis,

I can tell it works for sure, as I'm using this kind of dirty trick to 
cope with some buggy clients.


Best regards,
Bogdan

On 05/10/2011 06:42 AM, Denis Putyato wrote:


Hello!

Thank you Bogdan, I will try you decision

*From:*Bogdan-Andrei Iancu [mailto:bog...@opensips.org]
*Sent:* Friday, May 06, 2011 9:25 PM
*To:* OpenSIPS users mailling list
*Cc:* Denis Putyato
*Subject:* Re: [OpenSIPS-Users] dialog and acc

Hi Denis,

From a proxy point of view, a 200OK means the dialog was establish. A 
proxy cannot interfere with the ACK part - the acknowledgment is done 
between end parties.


If the ACK is missing (in an established dialog), the callee party 
(according to RFC) must send a BYE (when finishing the 200 OK 
retransmission) to the caller.  This is something your callee doesn't do.


A simple work around is to use the dialog timeout in opensips:
1) at INVITE time, when dialog is created, set a 5 seconds timeout 
(dialog will be terminated by opensips, with BYE, in 5 secs after 
being established - do not forget to set the BYE_ON_TIMEOUT flag)
2) at ACK, before loose_route() set a new timeout to some long, 
long (3 hours?) value.


So, if the ACK will mis, the 5 sec timeout will kick in and terminate 
the dialog; otherwise, opensips will prelong the dialog on ACK time.


Regards,
Bogdan

On 04/28/2011 03:06 PM, Denis Putyato wrote:

Hello!

I noticed that cdr_flag in acc modules marks dialog for accounting as 
answered even there was no ACK on 200 OK.


As a result, I have acc record which has a big duration and status 200 OK.

Thank you for any help.

  
  
___

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




--
Bogdan-Andrei Iancu
OpenSIPS eBootcamp - 2nd of May 2011
OpenSIPS solutions and "know-how"



--
Bogdan-Andrei Iancu
OpenSIPS eBootcamp - 2nd of May 2011
OpenSIPS solutions and "know-how"

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