Problem with mi_fifo replies

classic Classic list List threaded Threaded
11 messages Options
Reply | Threaded
Open this post in threaded view
|

Problem with mi_fifo replies

opensipslist

Hello list,

The platform is:

  Solaris 11 x86 (nv-b91)
  OpenSIPS 1.6.0 with TLS

Some permissions and runtime info (see the FIFO):

  # ls -ld /pfx/var/opensips/*
  drwx------ 2 osuser osuser    45 Dec 9 00:03 /pfx/var/opensips/db
  prw-rw---- 1 osuser osuser     0 Dec 9 19:29 /pfx/var/opensips/opensips.fifo
  -rw-rw-r-- 1 root   root  218362 Dec 9 19:30 /pfx/var/opensips/opensips.log
  -rw-r--r-- 1 osuser osuser     5 Dec 9 19:27 /pfx/var/opensips/opensips.pid
  drwx------ 2 osuser osuser     2 Dec 9 19:17 /pfx/var/opensips/tmp

  # ps -ef | grep opensips
  osuser  2034  2030   0 19:27:10 ? 0:00 /pfx/sbin/opensips -P /pfx/var/opensips/opensips.pid
  osuser  2039  2030   0 19:27:10 ? 0:00 /pfx/sbin/opensips -P /pfx/var/opensips/opensips.pid
  [... more lines like these two ...]

PROBLEM
-------

When examining the location table using either opensipsctl(1) or
osipsconsoe(1) the commands hang:

  $ opensipsctl ul show --brief
  [hang]

In the log (debug=20) I see:

  Dec 09 20:03:57 name.host.tld <error> opensips[6280]: ERROR:mi_fifo:mi_open_reply_pipe: open error (/pfx/var/opensips/opensips_receiver_6293): No such file or directory
  Dec 09 20:03:57 name.host.tld <error> opensips[6280]: ERROR:mi_fifo:mi_fifo_server: cannot open reply pipe /pfx/var/opensips/opensips_receiver_6293
  Dec 09 20:03:57 name.host.tld <debug> opensips[6280]: DBG:mi_fifo:mi_fifo_server: entered consume
  Dec 09 20:03:57 name.host.tld <debug> opensips[6280]: DBG:mi_fifo:mi_fifo_server: **** done consume

It seems that the ul_dump command is getting piped to the FIFO,
but mi_fifo then tries to open another 'receiver' FIFO and cannot.

CONFIG opensipsctlrc
--------------------

  DBENGINE=DBTEXT
  DBHOST=localhost
  DBNAME=opensips
  DB_PATH=/pfx/var/opensips/db
  DBRWUSER=osuser
  DBRWPW=thishere1
  DBROUSER=osuser
  DBROPW=thishere2
  DBROOTUSER=root
  USERCOL="username"

  CTLENGINE=FIFO
  OSIPS_FIFO=/pfx/var/opensips/opensips.fifo
  MI_CONNECTOR=FIFO:/pfx/var/opensips/opensips.fifo

CONFIG opensips.cfg
-------------------

  loadmodule "mi_fifo.so"

  modparam("mi_fifo", "fifo_name", "/pfx/var/opensips/opensips.fifo")
  modparam("mi_fifo", "fifo_mode", 0660)
  modparam("mi_fifo", "fifo_user", "osuser")
  modparam("mi_fifo", "fifo_group", "osuser")
  modparam("mi_fifo", "reply_dir", "/pfx/var/opensips/")

Has anyone seen similar problems or have an idea how to solve it?

Thanks,
Brian

_______________________________________________
Users mailing list
[hidden email]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Reply | Threaded
Open this post in threaded view
|

Re: Problem with mi_fifo replies

Bogdan-Andrei Iancu
Hi Brian,

Does opensipsctl through some error ? because I see opensips receives
the command (via command FIFO), but it is not able to reply back because
the reply fifo does not exists. The reply fifo is created by the
application that fires the request, the opensipsctl in this case. So,
either opensipsctl does not properly create the reply fifo, either it is
created with wrong permissions (like if you run opensipsctl as root, the
reply fifo will be created with root ownership and opensips, running as
osuser, may not have permissions to write into the reply fifo.
So, if there are no error, try to run opensipsctl as user osuser also.

Regards,
Bogdan

[hidden email] wrote:

> Hello list,
>
> The platform is:
>
>   Solaris 11 x86 (nv-b91)
>   OpenSIPS 1.6.0 with TLS
>
> Some permissions and runtime info (see the FIFO):
>
>   # ls -ld /pfx/var/opensips/*
>   drwx------ 2 osuser osuser    45 Dec 9 00:03 /pfx/var/opensips/db
>   prw-rw---- 1 osuser osuser     0 Dec 9 19:29 /pfx/var/opensips/opensips.fifo
>   -rw-rw-r-- 1 root   root  218362 Dec 9 19:30 /pfx/var/opensips/opensips.log
>   -rw-r--r-- 1 osuser osuser     5 Dec 9 19:27 /pfx/var/opensips/opensips.pid
>   drwx------ 2 osuser osuser     2 Dec 9 19:17 /pfx/var/opensips/tmp
>
>   # ps -ef | grep opensips
>   osuser  2034  2030   0 19:27:10 ? 0:00 /pfx/sbin/opensips -P /pfx/var/opensips/opensips.pid
>   osuser  2039  2030   0 19:27:10 ? 0:00 /pfx/sbin/opensips -P /pfx/var/opensips/opensips.pid
>   [... more lines like these two ...]
>
> PROBLEM
> -------
>
> When examining the location table using either opensipsctl(1) or
> osipsconsoe(1) the commands hang:
>
>   $ opensipsctl ul show --brief
>   [hang]
>
> In the log (debug=20) I see:
>
>   Dec 09 20:03:57 name.host.tld <error> opensips[6280]: ERROR:mi_fifo:mi_open_reply_pipe: open error (/pfx/var/opensips/opensips_receiver_6293): No such file or directory
>   Dec 09 20:03:57 name.host.tld <error> opensips[6280]: ERROR:mi_fifo:mi_fifo_server: cannot open reply pipe /pfx/var/opensips/opensips_receiver_6293
>   Dec 09 20:03:57 name.host.tld <debug> opensips[6280]: DBG:mi_fifo:mi_fifo_server: entered consume
>   Dec 09 20:03:57 name.host.tld <debug> opensips[6280]: DBG:mi_fifo:mi_fifo_server: **** done consume
>
> It seems that the ul_dump command is getting piped to the FIFO,
> but mi_fifo then tries to open another 'receiver' FIFO and cannot.
>
> CONFIG opensipsctlrc
> --------------------
>
>   DBENGINE=DBTEXT
>   DBHOST=localhost
>   DBNAME=opensips
>   DB_PATH=/pfx/var/opensips/db
>   DBRWUSER=osuser
>   DBRWPW=thishere1
>   DBROUSER=osuser
>   DBROPW=thishere2
>   DBROOTUSER=root
>   USERCOL="username"
>
>   CTLENGINE=FIFO
>   OSIPS_FIFO=/pfx/var/opensips/opensips.fifo
>   MI_CONNECTOR=FIFO:/pfx/var/opensips/opensips.fifo
>
> CONFIG opensips.cfg
> -------------------
>
>   loadmodule "mi_fifo.so"
>
>   modparam("mi_fifo", "fifo_name", "/pfx/var/opensips/opensips.fifo")
>   modparam("mi_fifo", "fifo_mode", 0660)
>   modparam("mi_fifo", "fifo_user", "osuser")
>   modparam("mi_fifo", "fifo_group", "osuser")
>   modparam("mi_fifo", "reply_dir", "/pfx/var/opensips/")
>
> Has anyone seen similar problems or have an idea how to solve it?
>
> Thanks,
> Brian
>
> _______________________________________________
> Users mailing list
> [hidden email]
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
>  


--
Bogdan-Andrei Iancu
www.voice-system.ro


_______________________________________________
Users mailing list
[hidden email]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Reply | Threaded
Open this post in threaded view
|

Re: Problem with mi_fifo replies

opensipslist

Hello Bogdan,

On thur., dec 10, 2009, Bogdan-Andrei Iancu wrote:

>Does opensipsctl through some error ? because I see opensips receives
>the command (via command FIFO), but it is not able to reply back because
>the reply fifo does not exists. The reply fifo is created by the
>application that fires the request, the opensipsctl in this case. So,
>either opensipsctl does not properly create the reply fifo, either it is
>created with wrong permissions (like if you run opensipsctl as root, the
>reply fifo will be created with root ownership and opensips, running as
>osuser, may not have permissions to write into the reply fifo.
>So, if there are no error, try to run opensipsctl as user osuser also.
>
>[hidden email] wrote:
>> PROBLEM
>> -------
>>
>> When examining the location table using either opensipsctl(1) or
>> osipsconsoe(1) the commands hang:
>>
>>   $ opensipsctl ul show --brief
>>   [hang]
>>
>> In the log (debug=20) I see:
>>
>>   Dec 09 20:03:57 name.host.tld <error> opensips[6280]: ERROR:mi_fifo:mi_open_reply_pipe: open error (/pfx/var/opensips/opensips_receiver_6293): No such file or directory
>>   Dec 09 20:03:57 name.host.tld <error> opensips[6280]: ERROR:mi_fifo:mi_fifo_server: cannot open reply pipe /pfx/var/opensips/opensips_receiver_6293
>>
>> CONFIG opensipsctlrc
>> --------------------
>>
>>   CTLENGINE=FIFO
>>   OSIPS_FIFO=/pfx/var/opensips/opensips.fifo
>>   MI_CONNECTOR=FIFO:/pfx/var/opensips/opensips.fifo
>>
With your advice I found 1/2 the solution. The OSER_FIRET
variable was missing from opensipsctlrc, which seems to describe
where the reply FIFO should be opened. I had it set to OSIPS_FIRET,
figuring that OpenSER names were no longer being used.

...so using opensipsctl(1) now works (1/2 the problem.)

But even after placing OSER_FIRET in osipsconsolerc, the
osipsconsole(1) still hangs when calling 'ul show --brief':

  Dec 10 10:51:32 name.host.tld <error> opensips[17625]: ERROR:mi_fifo:mi_open_reply_pipe: open error (/pfx/var/opensips/fifo_reply): No such file or directory
  Dec 10 10:51:32 name.host.tld <error> opensips[17625]: ERROR:mi_fifo:mi_fifo_server: cannot open reply pipe /pfx/var/opensips/fifo_reply

Looking in the perl file 'osipsconsole' I see that 'fifo_reply' is
hardcoded to a variable simply called 'name', which is impossible to
debug because 'name' is used everywhere in the perl modules.

Do you happen to know how to set the 'fifo_reply' name and path in
the osipsconsolerc? Are these really hard coded?

Regards,
Brian

_______________________________________________
Users mailing list
[hidden email]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Reply | Threaded
Open this post in threaded view
|

Re: Problem with mi_fifo replies

opensipslist
In reply to this post by Bogdan-Andrei Iancu

Hello again,

On thur., dec 10, 2009, Bogdan-Andrei Iancu wrote:

>Does opensipsctl through some error ? because I see opensips receives
>the command (via command FIFO), but it is not able to reply back because
>the reply fifo does not exists. The reply fifo is created by the
>application that fires the request, the opensipsctl in this case. So,
>either opensipsctl does not properly create the reply fifo, either it is
>created with wrong permissions (like if you run opensipsctl as root, the
>reply fifo will be created with root ownership and opensips, running as
>osuser, may not have permissions to write into the reply fifo.
>So, if there are no error, try to run opensipsctl as user osuser also.
>
What exactly does 'MI_CONNECTOR' do, is the following config correct?

  # config file opensipsctlrc:
  CTLENGINE=FIFO
  OSIPS_FIFO=/pfx/var/opensips/opensips.fifo
  OSER_FIRET=/pfx/var/opensips
  MI_CONNECTOR=FIFO:/pfx/var/opensips/opensips.fifo

...and should it be the same in osipsconsolrc?

I think some of these config items through the cracks as OpenSER forked.
For example, 'OSER_FIRET' is nowhere to be found in the configs of
the current 1.6.0 distro, although it is used in the script files.

Brian

_______________________________________________
Users mailing list
[hidden email]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Reply | Threaded
Open this post in threaded view
|

Re: Problem with mi_fifo replies

Iulia Bublea-2
In reply to this post by opensipslist
Hi,

Regarding the osipsconsole, I have renamed the fifo reply file from $name to $fifo_reply_file. It is still hardcoded in the script. So u can change in the script the $fifo_reply_file parameter and for the path you can set, in the same file, the $fifo_reply_path. The two parameters are one below the other.

You can find the changed version of opensips on svn.


Regards,
Iulia


PROBLEM
-------

When examining the location table using either opensipsctl(1) or
osipsconsoe(1) the commands hang:

  $ opensipsctl ul show --brief
  [hang]

In the log (debug=20) I see:

  Dec 09 20:03:57 name.host.tld <error> opensips[6280]: ERROR:mi_fifo:mi_open_reply_pipe: open error (/pfx/var/opensips/opensips_receiver_6293): No such file or directory
  Dec 09 20:03:57 name.host.tld <error> opensips[6280]: ERROR:mi_fifo:mi_fifo_server: cannot open reply pipe /pfx/var/opensips/opensips_receiver_6293

CONFIG opensipsctlrc
--------------------

  CTLENGINE=FIFO
  OSIPS_FIFO=/pfx/var/opensips/opensips.fifo
  MI_CONNECTOR=FIFO:/pfx/var/opensips/opensips.fifo

      
With your advice I found 1/2 the solution. The OSER_FIRET
variable was missing from opensipsctlrc, which seems to describe
where the reply FIFO should be opened. I had it set to OSIPS_FIRET,
figuring that OpenSER names were no longer being used.

...so using opensipsctl(1) now works (1/2 the problem.)

But even after placing OSER_FIRET in osipsconsolerc, the
osipsconsole(1) still hangs when calling 'ul show --brief':

  Dec 10 10:51:32 name.host.tld <error> opensips[17625]: ERROR:mi_fifo:mi_open_reply_pipe: open error (/pfx/var/opensips/fifo_reply): No such file or directory
  Dec 10 10:51:32 name.host.tld <error> opensips[17625]: ERROR:mi_fifo:mi_fifo_server: cannot open reply pipe /pfx/var/opensips/fifo_reply

Looking in the perl file 'osipsconsole' I see that 'fifo_reply' is
hardcoded to a variable simply called 'name', which is impossible to
debug because 'name' is used everywhere in the perl modules.

Do you happen to know how to set the 'fifo_reply' name and path in
the osipsconsolerc? Are these really hard coded?

Regards,
Brian

_______________________________________________
Users mailing list
[hidden email]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

  


--
Iulia Bublea
Web: www.voice-system.ro
Email: [hidden email]

_______________________________________________
Users mailing list
[hidden email]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Reply | Threaded
Open this post in threaded view
|

Re: Problem with mi_fifo replies

Iulia Bublea-2
In reply to this post by opensipslist
Hi,

For the osipsconsole just uncomment the MI_CONNECTOR in the osipsconsolerc

Iulia
What exactly does 'MI_CONNECTOR' do, is the following config correct?

  # config file opensipsctlrc:
  CTLENGINE=FIFO
  OSIPS_FIFO=/pfx/var/opensips/opensips.fifo
  OSER_FIRET=/pfx/var/opensips
  MI_CONNECTOR=FIFO:/pfx/var/opensips/opensips.fifo

...and should it be the same in osipsconsolrc?

I think some of these config items through the cracks as OpenSER forked.
For example, 'OSER_FIRET' is nowhere to be found in the configs of
the current 1.6.0 distro, although it is used in the script files.

Brian

_______________________________________________
Users mailing list
[hidden email]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

  


--
Iulia Bublea
Web: www.voice-system.ro
Email: [hidden email]

_______________________________________________
Users mailing list
[hidden email]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Reply | Threaded
Open this post in threaded view
|

Re: Problem with mi_fifo replies

opensipslist

Hello Iulia,

An jeu., déc 10, 2009, Iulia Bublea schrieb:

>> What exactly does 'MI_CONNECTOR' do, is the following config correct?
>>
>>   # config file opensipsctlrc:
>>   CTLENGINE=FIFO
>>   OSIPS_FIFO=/pfx/var/opensips/opensips.fifo
>>   OSER_FIRET=/pfx/var/opensips
>>   MI_CONNECTOR=FIFO:/pfx/var/opensips/opensips.fifo
>>
>> ...and should it be the same in osipsconsolrc?
>>
> For the osipsconsole just uncomment the MI_CONNECTOR in the osipsconsolerc
>
okay, but what should its value be? Should MI_CONNECTOR and
OSIPS_FIFO always be set to the same path as in my example above?

Regards,
Brian

_______________________________________________
Users mailing list
[hidden email]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Reply | Threaded
Open this post in threaded view
|

Re: Problem with mi_fifo replies

Iulia Bublea-2
To my knowledge OSIPS_FIFO is not used in osispsconsolerc, the only parameter used is MI_FIFO.

Iulia


[hidden email] wrote:
Hello Iulia,

An jeu., déc 10, 2009, Iulia Bublea schrieb:
  
What exactly does 'MI_CONNECTOR' do, is the following config correct?

  # config file opensipsctlrc:
  CTLENGINE=FIFO
  OSIPS_FIFO=/pfx/var/opensips/opensips.fifo
  OSER_FIRET=/pfx/var/opensips
  MI_CONNECTOR=FIFO:/pfx/var/opensips/opensips.fifo

...and should it be the same in osipsconsolrc?

      
For the osipsconsole just uncomment the MI_CONNECTOR in the osipsconsolerc

    
okay, but what should its value be? Should MI_CONNECTOR and
OSIPS_FIFO always be set to the same path as in my example above?

Regards,
Brian

_______________________________________________
Users mailing list
[hidden email]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

  


--
Iulia Bublea
Web: www.voice-system.ro
Email: [hidden email]

_______________________________________________
Users mailing list
[hidden email]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Reply | Threaded
Open this post in threaded view
|

Re: Problem with mi_fifo replies

opensipslist

Hello Iulia,

An jeu., déc 10, 2009, Iulia Bublea schrieb:
> To my knowledge OSIPS_FIFO is not used in osispsconsolerc, the only  
> parameter used is MI_FIFO.
>
I think you mean 'OSIPS_FIFO is not used in osipsconsol' but that
is be a wrong impression, see grep(1) output below. Both MI_FIFO
and OSIPS_FIFO are indeed used by osipsconsole. The question is if
both should be set to the same path value, or where the
documentation is to describe choosing a path for the various
(how many?) FIFOs being used.

---- Cut ----

[host]/tmp/opensips-1.6.0-tls.orig$ grep OSIPS_FIFO scripts/osipsconsole
my $OSIPS_FIFO = "";
                                        $OSIPS_FIFO = $list[1];
        $OSIPS_FIFO = "/tmp/opensips_fifo";
        &write_read_fifo($OSIPS_FIFO,$path,$cmd_fifo);
                &write_read_fifo($OSIPS_FIFO,$path,$cmd_fifo);
                &write_read_fifo($OSIPS_FIFO,$path,$cmd_fifo);
                &write_read_fifo($OSIPS_FIFO,$path,":get_statistics:$name\nUAS_transactions\nUAC_transactions\ninuse_transactions\n\n");
                &write_read_fifo($OSIPS_FIFO,$path,":get_statistics:$name\nsent_replies\nsent_err_replies\nreceived_ACKs\n\n");
                &write_read_fifo($OSIPS_FIFO,$path,":get_statistics:$name\nusrloc:\n\n");
        $OSIPS_FIFO = $_[0];
        if (!-e $OSIPS_FIFO){
                print "File $OSIPS_FIFO does not exist!";
        if ( !-w $OSIPS_FIFO ) {
                print "Error opening OpenSIPS's FIFO " . $OSIPS_FIFO . "\n" .
                      "Make sure you have the line 'modparam(\"mi_fifo\", \"fifo_name\", \" " . $OSIPS_FIFO . "\")' in your config\n" .
        open(ANS,">$OSIPS_FIFO") or die "Could not open $OSIPS_FIFO for writing: $!\n";

Regards,
Brian

_______________________________________________
Users mailing list
[hidden email]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Reply | Threaded
Open this post in threaded view
|

Re: Problem with mi_fifo replies

Iulia Bublea-2
No, I meant that OSISP_FIFO is not used in osipsconsolerc.
Indeed it is used in osispconsole, but it is just a parameter and it's value comes from splitting MI_CONNECTOR by ":". That is all. For param configuring just use osipsconsolerc or opensispctlrc.

Iulia

[hidden email] wrote:
Hello Iulia,

An jeu., déc 10, 2009, Iulia Bublea schrieb:
  
To my knowledge OSIPS_FIFO is not used in osispsconsolerc, the only  
parameter used is MI_FIFO.

    
I think you mean 'OSIPS_FIFO is not used in osipsconsol' but that
is be a wrong impression, see grep(1) output below. Both MI_FIFO
and OSIPS_FIFO are indeed used by osipsconsole. The question is if
both should be set to the same path value, or where the
documentation is to describe choosing a path for the various
(how many?) FIFOs being used.

---- Cut ----

[host]/tmp/opensips-1.6.0-tls.orig$ grep OSIPS_FIFO scripts/osipsconsole
my $OSIPS_FIFO = "";
                                        $OSIPS_FIFO = $list[1];
        $OSIPS_FIFO = "/tmp/opensips_fifo";
        &write_read_fifo($OSIPS_FIFO,$path,$cmd_fifo);
                &write_read_fifo($OSIPS_FIFO,$path,$cmd_fifo);
                &write_read_fifo($OSIPS_FIFO,$path,$cmd_fifo);
                &write_read_fifo($OSIPS_FIFO,$path,":get_statistics:$name\nUAS_transactions\nUAC_transactions\ninuse_transactions\n\n");
                &write_read_fifo($OSIPS_FIFO,$path,":get_statistics:$name\nsent_replies\nsent_err_replies\nreceived_ACKs\n\n");
                &write_read_fifo($OSIPS_FIFO,$path,":get_statistics:$name\nusrloc:\n\n");
        $OSIPS_FIFO = $_[0];
        if (!-e $OSIPS_FIFO){
                print "File $OSIPS_FIFO does not exist!";
        if ( !-w $OSIPS_FIFO ) {
                print "Error opening OpenSIPS's FIFO " . $OSIPS_FIFO . "\n" . 
                      "Make sure you have the line 'modparam(\"mi_fifo\", \"fifo_name\", \" " . $OSIPS_FIFO . "\")' in your config\n" .
        open(ANS,">$OSIPS_FIFO") or die "Could not open $OSIPS_FIFO for writing: $!\n";

Regards,
Brian

_______________________________________________
Users mailing list
[hidden email]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

  


--
Iulia Bublea
Web: www.voice-system.ro
Email: [hidden email]

_______________________________________________
Users mailing list
[hidden email]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Reply | Threaded
Open this post in threaded view
|

Re: Problem with mi_fifo replies

opensipslist

Hello Iulia,

An jeu., déc 10, 2009, Iulia Bublea schrieb:
> No, I meant that OSISP_FIFO is not used in osipsconsolerc.
> Indeed it is used in osispconsole, but it is just a parameter and it's  
> value comes from splitting MI_CONNECTOR by ":". That is all. For param  
> configuring just use osipsconsolerc or opensispctlrc.
>
Okay I understand now but if OSIPS_FIFO is used both in osipsconsole(1)
and opensipsctl(1), then surely they both refer to the same concept
right? And if so, then when each of these two scripts resolves those
variables they should resolve to the same path, right?

I'm asking this to try to get a grip on what the values OSIPS_FIFO,
OSER_FIRE, and MI_CONNECTOR should be set to.

Is it correct to assume that OSIPS_FIFO and MI_CONNECTOR should both
be set and both resolve to the same path in opensipsctlrc?

Thanks,
Brian

_______________________________________________
Users mailing list
[hidden email]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users