Re: [OpenSIPS-Users] FIFO very fragile
On Mon, May 9, 2011 at 7:28 PM, Dave Singer wrote: > Brett, > > In your perl app are you starting and forking/threading the read before >print FIFO ":uptime:reply_fifo\n"; > ? Dave, I tried all sorts of ways. I'm pretty sure my problem comes down to some failicy in how I'm performing my open statement to write to the opensips fifo. My first attempt was linearly: 1. Open Reader 2. Open Writer 3. Write fifo command to writer (/tmp/opensips_fifo) 4. Loop over Reader filehandle until I get something Because of the way fifos work, this naturally blocks on the reader and never makes it to the writer. This is verified by administering an "echo" to the fifo with a valid command and everyone wakes up (and works properly) Second attempt was forking 1. Open Reader 2. Sleep 5 seconds 3. Fork 4. Fork Opens Writer 5. Fork writes to writer (/tmp/opensips_fifo) 6. Reader in loop looking for data from filehandle This also blocks on the reader. From what I can see, it doesn't appear that anything ever gets written (at least not properly) to /tmp/opensips_fifo. I've tried opening it with > and >. I've also tried explicit sysopen calls for write only and a few other variants. None of them worked Next I tried the above scenario, but I wrote another perl script that did nothing but open /tmp/opensips_fifo and wrote to it.. That didn't work either. That was running on another terminal altogether. So no backgrounding funny business here.. Last attempt was forking with a system call. 1. Open Reader 2. Fork 3. Fork executes system call to `echo` command to /tmp/opensips_fifo 4. Reader in loop looking for data from filehandle 5. Reader returns result from opensips *SUCCESS* That last variant works over and over... Of course, this issue above is notably a different issue than my original posting which is really about the fragility of the fifo itself. If given improper commands it tends to lock up (just the fifo, nothing else). If you have any ideas on what to do here, I'd appreciate it. :) Thanks! -Brett ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] dialog and acc
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" ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] FIFO very fragile
Brett,
In your perl app are you starting and forking/threading the read before
print FIFO ":uptime:reply_fifo\n";
?
I seem to remember starting the read process first to be very important.
My speculation is the reply fifo is not truely active until it has a
process actively attached and reading from it. So when opensips tries
to write to it, it succeeds checking the fifo file exists and it has
proper properties but when it tries to write to it linux says it is
not ready or something since it is not a buffer per say. Then opensips
waits for something to update/push it which never happens. (again just
my speculation from my previous efforts)
Dave
On Mon, May 9, 2011 at 5:01 PM, Brett Nemeroff wrote:
>
> Dave,
> Yeah, I do actually get a reply. Works reliably too as long as I'm careful
> about what I'm asking for. I'm trying to do all of this directly from perl.
> For some reason I can't write to the fifo with a simple:
> open(FIFO,">/tmp/opensips_fifo");
> print FIFO ":uptime:reply_fifo\n";
> The fifo never receives it.. now, if I leave the reader attached and use
> "echo" from bash, it works great.
> Really, the concern I have it doing things that cause the fifo to "die" and
> become unavailable. I've seen this with the opensipsctl script as well, where
> the fifo just stops responding until you restart.
> -Brett
>
> On Mon, May 9, 2011 at 4:03 PM, Dave Singer wrote:
>>
>> Are you actually able to get results out of the reply fifo?
>> It's been a long time since I created my bash fifo script so I don't
>> remember all the particulars of what I ran into.
>> It can be important to start the read fifo before sending the command
>>
>> Hear is a snippet from a bash fifo I did.
>>
>> trap "\rm -f $dlg $fifo_reply ${fifo_answer}* 2> /dev/null; exit 1" 0
>> if [ ! -w $FIFO ] ; then # can I write to FIFO server?
>> echo "Error opening ser's FIFO $FIFO" >> $DEBUG_OUT
>> echo "FAILED"
>> exit 1
>> fi
>> mkdir -p $fifo_dir 2> /dev/null
>> mkfifo $fifo_reply # create a reply FIFO
>> if [ $? -ne 0 ] ; then
>> echo "error opening reply fifo $fifo_reply" >> $DEBUG_OUT
>> echo "FAILED"
>> exit 1
>> fi
>> chmod a+w $fifo_reply
>> # start reader now so that it is ready for replies
>> # immediately after a request is out
>> cat < $fifo_reply > $dlg &
>> fifo_job="$!"
>>
>> # set trap to cleanup in case of problems or outside kill
>> trap "kill -9 $fifo_job $fifo_answer_job 2>1 >> $DEBUG_OUT ; exit 1" 0
>> # finally actually push command to the fifo
>> echo "reply pid: $fifo_job, reply fifo: $fifo_reply" >> $DEBUG_OUT
>>
>> You may want to just use the fifo handeling built into opensipsctl
>> eg:
>> /path/opensipsctl fifo ps
>>
>> Dave
>>
>>
>> On Mon, May 9, 2011 at 1:42 PM, Brett Nemeroff wrote:
>>>
>>> Dave,
>>> I don't think those are the issues. First of all, if I supply the full path
>>> to the reply fifo, I get an error message that the filename is invalid.
>>> More importantly, it doesn't work. :) without the full path, it does work.
>>> Secondly, I don't think it's SELinux issue because it *does work*
>>> repeatedly over and over. But an extra carriage return spoils the fun for
>>> everyone and I can't fix it without restarting opensips.
>>> Do you believe SELinux could cause an issue like that?
>>> Thanks!
>>> -Brett
>>>
>>> On Mon, May 9, 2011 at 3:39 PM, Dave Singer
>>> wrote:
Brett,
I believe you need the full path to the reply fifo.
Try:
echo -e ":address_dump:/tmp/my_fifo\n\n" > /tmp/opensips_fifo
you may also have a permissions ( chmod a+w /tmp/my_fifo ) and/or SELinux
issue (very likely if SELinux is enabled, I posted a howto for SELinux in
the list a number of months back)
Dave
On Mon, May 9, 2011 at 9:40 AM, Brett Nemeroff wrote:
>
> Hello List,
> So I've been doing some testing with the mi_fifo and found that it
> appears to be really fragile. Here's what I've done:
> mkfifo /tmp/my_fifo
> cat /tmp/my_fifo&
> echo -e ":address_dump:my_fifo\n\n" > /tmp/opensips_fifo
> *returns*
> 200 OK
> 48 <1.2.3.4,2, 0, 0, NULL, NULL>
> ** cat process ends
> cat /tmp/my_fifo&
> echo -e ":address_dump:my_fifo\n\n" > /tmp/opensips_fifo
> ** nothing
> At this point, I can't make the fifo work again until I restart opensips.
> If I detach from the fifo (kill the cat, so to speak), and reattach it
> doesn't work. Nothing seems to make it responsive again. At first I
> though something was horribly broken, but then I removed one of my \n
> from the fifo command and now it works "as expected". Two new-lines
> shouldn't break the fifo, right?
> Thanks!
> -Brett
>
>
>
> ___
> Users mailing list
> Users@lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
--
David Singer
Re: [OpenSIPS-Users] FIFO very fragile
Dave,
Yeah, I do actually get a reply. Works reliably too as long as I'm careful
about what I'm asking for. I'm trying to do all of this directly from perl.
For some reason I can't write to the fifo with a simple:
open(FIFO,">/tmp/opensips_fifo");
print FIFO ":uptime:reply_fifo\n";
The fifo never receives it.. now, if I leave the reader attached and use
"echo" from bash, it works great.
Really, the concern I have it doing things that cause the fifo to "die" and
become unavailable. I've seen this with the opensipsctl script as well,
where the fifo just stops responding until you restart.
-Brett
On Mon, May 9, 2011 at 4:03 PM, Dave Singer wrote:
> Are you actually able to get results out of the reply fifo?
> It's been a long time since I created my bash fifo script so I don't
> remember all the particulars of what I ran into.
> It can be important to start the read fifo before sending the command
>
> Hear is a snippet from a bash fifo I did.
>
> trap "\rm -f $dlg $fifo_reply ${fifo_answer}* 2> /dev/null; exit 1" 0
> if [ ! -w $FIFO ] ; then # can I write to FIFO server?
> echo "Error opening ser's FIFO $FIFO" >> $DEBUG_OUT
> echo "FAILED"
> exit 1
> fi
> mkdir -p $fifo_dir 2> /dev/null
> mkfifo $fifo_reply # create a reply FIFO
> if [ $? -ne 0 ] ; then
> echo "error opening reply fifo $fifo_reply" >> $DEBUG_OUT
> echo "FAILED"
> exit 1
> fi
> chmod a+w $fifo_reply
> # start reader now so that it is ready for replies
> # immediately after a request is out
> cat < $fifo_reply > $dlg &
> fifo_job="$!"
>
> # set trap to cleanup in case of problems or outside kill
> trap "kill -9 $fifo_job $fifo_answer_job 2>1 >> $DEBUG_OUT ; exit 1" 0
> # finally actually push command to the fifo
> echo "reply pid: $fifo_job, reply fifo: $fifo_reply" >> $DEBUG_OUT
>
> You may want to just use the fifo handeling built into opensipsctl
> eg:
> /path/opensipsctl fifo ps
>
> Dave
>
>
>
> On Mon, May 9, 2011 at 1:42 PM, Brett Nemeroff wrote:
>
>> Dave,
>> I don't think those are the issues. First of all, if I supply the full
>> path to the reply fifo, I get an error message that the filename is invalid.
>> More importantly, it doesn't work. :) without the full path, it does work.
>>
>> Secondly, I don't think it's SELinux issue because it *does work*
>> repeatedly over and over. But an extra carriage return spoils the fun for
>> everyone and I can't fix it without restarting opensips.
>>
>> Do you believe SELinux could cause an issue like that?
>> Thanks!
>> -Brett
>>
>>
>> On Mon, May 9, 2011 at 3:39 PM, Dave Singer wrote:
>>
>>> Brett,
>>> I believe you need the full path to the reply fifo.
>>> Try:
>>> echo -e ":address_dump:/tmp/my_fifo\n\n" > /tmp/opensips_fifo
>>>
>>> you may also have a permissions ( chmod a+w /tmp/my_fifo ) and/or SELinux
>>> issue (very likely if SELinux is enabled, I posted a howto for SELinux in
>>> the list a number of months back)
>>>
>>> Dave
>>>
>>> On Mon, May 9, 2011 at 9:40 AM, Brett Nemeroff wrote:
>>>
Hello List,
So I've been doing some testing with the mi_fifo and found that it
appears to be really fragile. Here's what I've done:
mkfifo /tmp/my_fifo
cat /tmp/my_fifo&
echo -e ":address_dump:my_fifo\n\n" > /tmp/opensips_fifo
*returns*
200 OK
48 <1.2.3.4,2, 0, 0, NULL, NULL>
** cat process ends
cat /tmp/my_fifo&
echo -e ":address_dump:my_fifo\n\n" > /tmp/opensips_fifo
** nothing
At this point, I can't make the fifo work again until I restart
opensips. If I detach from the fifo (kill the cat, so to speak), and
reattach it doesn't work. Nothing seems to make it responsive again. At
first I though something was horribly broken, but then I removed one of my
\n from the fifo command and now it works "as expected". Two new-lines
shouldn't break the fifo, right?
Thanks!
-Brett
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>>
>>>
>>> --
>>> David Singer
>>>
>>> ___
>>> 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
>>
>>
>
>
> --
> David Singer
>
> ___
> 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] Pjsip dialler with openIMS core
Looks like you sent your request to the wrong list. On Mon, May 9, 2011 at 12:24 AM, abid khan wrote: > Hello everybody, > I want to know main criteria or parameters which > i have to fulfill if i want to register* pjsip dialer* with openIMS core. > When i try to register pjsip dialler with openims core my server send does > not send "Authorization " to pjsip in response and then 504 (request time > out) in end. So any one can please help me in this. > > -- > *Abid khan > * > > ___ > 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] FIFO very fragile
Are you actually able to get results out of the reply fifo?
It's been a long time since I created my bash fifo script so I don't
remember all the particulars of what I ran into.
It can be important to start the read fifo before sending the command
Hear is a snippet from a bash fifo I did.
trap "\rm -f $dlg $fifo_reply ${fifo_answer}* 2> /dev/null; exit 1" 0
if [ ! -w $FIFO ] ; then # can I write to FIFO server?
echo "Error opening ser's FIFO $FIFO" >> $DEBUG_OUT
echo "FAILED"
exit 1
fi
mkdir -p $fifo_dir 2> /dev/null
mkfifo $fifo_reply # create a reply FIFO
if [ $? -ne 0 ] ; then
echo "error opening reply fifo $fifo_reply" >> $DEBUG_OUT
echo "FAILED"
exit 1
fi
chmod a+w $fifo_reply
# start reader now so that it is ready for replies
# immediately after a request is out
cat < $fifo_reply > $dlg &
fifo_job="$!"
# set trap to cleanup in case of problems or outside kill
trap "kill -9 $fifo_job $fifo_answer_job 2>1 >> $DEBUG_OUT ; exit 1" 0
# finally actually push command to the fifo
echo "reply pid: $fifo_job, reply fifo: $fifo_reply" >> $DEBUG_OUT
You may want to just use the fifo handeling built into opensipsctl
eg:
/path/opensipsctl fifo ps
Dave
On Mon, May 9, 2011 at 1:42 PM, Brett Nemeroff wrote:
> Dave,
> I don't think those are the issues. First of all, if I supply the full path
> to the reply fifo, I get an error message that the filename is invalid. More
> importantly, it doesn't work. :) without the full path, it does work.
>
> Secondly, I don't think it's SELinux issue because it *does work*
> repeatedly over and over. But an extra carriage return spoils the fun for
> everyone and I can't fix it without restarting opensips.
>
> Do you believe SELinux could cause an issue like that?
> Thanks!
> -Brett
>
>
> On Mon, May 9, 2011 at 3:39 PM, Dave Singer wrote:
>
>> Brett,
>> I believe you need the full path to the reply fifo.
>> Try:
>> echo -e ":address_dump:/tmp/my_fifo\n\n" > /tmp/opensips_fifo
>>
>> you may also have a permissions ( chmod a+w /tmp/my_fifo ) and/or SELinux
>> issue (very likely if SELinux is enabled, I posted a howto for SELinux in
>> the list a number of months back)
>>
>> Dave
>>
>> On Mon, May 9, 2011 at 9:40 AM, Brett Nemeroff wrote:
>>
>>> Hello List,
>>> So I've been doing some testing with the mi_fifo and found that it
>>> appears to be really fragile. Here's what I've done:
>>>
>>> mkfifo /tmp/my_fifo
>>> cat /tmp/my_fifo&
>>> echo -e ":address_dump:my_fifo\n\n" > /tmp/opensips_fifo
>>> *returns*
>>> 200 OK
>>> 48 <1.2.3.4,2, 0, 0, NULL, NULL>
>>> ** cat process ends
>>> cat /tmp/my_fifo&
>>> echo -e ":address_dump:my_fifo\n\n" > /tmp/opensips_fifo
>>> ** nothing
>>>
>>> At this point, I can't make the fifo work again until I restart opensips.
>>> If I detach from the fifo (kill the cat, so to speak), and reattach it
>>> doesn't work. Nothing seems to make it responsive again. At first I though
>>> something was horribly broken, but then I removed one of my \n from the fifo
>>> command and now it works "as expected". Two new-lines shouldn't break the
>>> fifo, right?
>>>
>>> Thanks!
>>> -Brett
>>>
>>>
>>>
>>>
>>> ___
>>> Users mailing list
>>> Users@lists.opensips.org
>>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>>
>>>
>>
>>
>> --
>> David Singer
>>
>> ___
>> 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
>
>
--
David Singer
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
[OpenSIPS-Users] Need help defining a stackexchange (i.e. stackoverflow) for telephony
For those of that are fans of stackoverflow.com, and stackexchange.com, there's an effort to define a telephony stackexchange site. It's still in the definition phase -- what it needs to move forwards is more votes on on/off topic questions, and perhaps some better questions to vote for or against. If you're interested in helping out, or following the progress, visit: http://area51.stackexchange.com/proposals/12932/telephony/ Cheers, spd ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] FIFO very fragile
Dave, I don't think those are the issues. First of all, if I supply the full path to the reply fifo, I get an error message that the filename is invalid. More importantly, it doesn't work. :) without the full path, it does work. Secondly, I don't think it's SELinux issue because it *does work* repeatedly over and over. But an extra carriage return spoils the fun for everyone and I can't fix it without restarting opensips. Do you believe SELinux could cause an issue like that? Thanks! -Brett On Mon, May 9, 2011 at 3:39 PM, Dave Singer wrote: > Brett, > I believe you need the full path to the reply fifo. > Try: > echo -e ":address_dump:/tmp/my_fifo\n\n" > /tmp/opensips_fifo > > you may also have a permissions ( chmod a+w /tmp/my_fifo ) and/or SELinux > issue (very likely if SELinux is enabled, I posted a howto for SELinux in > the list a number of months back) > > Dave > > On Mon, May 9, 2011 at 9:40 AM, Brett Nemeroff wrote: > >> Hello List, >> So I've been doing some testing with the mi_fifo and found that it appears >> to be really fragile. Here's what I've done: >> >> mkfifo /tmp/my_fifo >> cat /tmp/my_fifo& >> echo -e ":address_dump:my_fifo\n\n" > /tmp/opensips_fifo >> *returns* >> 200 OK >> 48 <1.2.3.4,2, 0, 0, NULL, NULL> >> ** cat process ends >> cat /tmp/my_fifo& >> echo -e ":address_dump:my_fifo\n\n" > /tmp/opensips_fifo >> ** nothing >> >> At this point, I can't make the fifo work again until I restart opensips. >> If I detach from the fifo (kill the cat, so to speak), and reattach it >> doesn't work. Nothing seems to make it responsive again. At first I though >> something was horribly broken, but then I removed one of my \n from the fifo >> command and now it works "as expected". Two new-lines shouldn't break the >> fifo, right? >> >> Thanks! >> -Brett >> >> >> >> >> ___ >> Users mailing list >> Users@lists.opensips.org >> http://lists.opensips.org/cgi-bin/mailman/listinfo/users >> >> > > > -- > David Singer > > ___ > 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] FIFO very fragile
Brett, I believe you need the full path to the reply fifo. Try: echo -e ":address_dump:/tmp/my_fifo\n\n" > /tmp/opensips_fifo you may also have a permissions ( chmod a+w /tmp/my_fifo ) and/or SELinux issue (very likely if SELinux is enabled, I posted a howto for SELinux in the list a number of months back) Dave On Mon, May 9, 2011 at 9:40 AM, Brett Nemeroff wrote: > Hello List, > So I've been doing some testing with the mi_fifo and found that it appears > to be really fragile. Here's what I've done: > > mkfifo /tmp/my_fifo > cat /tmp/my_fifo& > echo -e ":address_dump:my_fifo\n\n" > /tmp/opensips_fifo > *returns* > 200 OK > 48 <1.2.3.4,2, 0, 0, NULL, NULL> > ** cat process ends > cat /tmp/my_fifo& > echo -e ":address_dump:my_fifo\n\n" > /tmp/opensips_fifo > ** nothing > > At this point, I can't make the fifo work again until I restart opensips. > If I detach from the fifo (kill the cat, so to speak), and reattach it > doesn't work. Nothing seems to make it responsive again. At first I though > something was horribly broken, but then I removed one of my \n from the fifo > command and now it works "as expected". Two new-lines shouldn't break the > fifo, right? > > Thanks! > -Brett > > > > > ___ > Users mailing list > Users@lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > > -- David Singer ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] db_oracle module not working
I am using version 1.6.4. Please let me know which version should i USE AND what am I missing? Abid Saleem Date: Mon, 9 May 2011 11:49:54 +0300 From: vladp...@opensips.org To: users@lists.opensips.org Subject: Re: [OpenSIPS-Users] db_oracle module not working Message body Hello, As far as I can see, the db_oracle module is exporting the use_table function. both in trunk and in the stable 1.6 releases. Are you sure you are using the proper sources ? Regards, -- Vlad Paiu OpenSIPS Developer On 05/07/2011 09:36 AM, Abid Saleem wrote: Hi, I have compiled db_oracle fine with OSIPS 1.6.X. Now when I change my opensipsctlrc file to connect to Oracle and load module db_oracle in opensips.cfg and then start opensips, it is giving me following error. Can somebody help me with this as quickly as possible. Here are the errors I receive in log file. May 7 11:29:22 opensips /usr/local/sbin/opensips[5969]: ERROR:core:db_check_api: module db_oracle does not export db_use_table function May 7 11:29:22 opensips /usr/local/sbin/opensips[5969]: ERROR:usrloc:mod_init: failed to bind database module May 7 11:29:22 opensips /usr/local/sbin/opensips[5969]: ERROR:core:init_mod: failed to initialize module usrloc May 7 11:29:22 opensips /usr/local/sbin/opensips[5969]: ERROR:core:main: error while initializing modules Help Help Help Plzz. Rgrds Abid Saleem ___ 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
[OpenSIPS-Users] FIFO very fragile
Hello List, So I've been doing some testing with the mi_fifo and found that it appears to be really fragile. Here's what I've done: mkfifo /tmp/my_fifo cat /tmp/my_fifo& echo -e ":address_dump:my_fifo\n\n" > /tmp/opensips_fifo *returns* 200 OK 48 <1.2.3.4,2, 0, 0, NULL, NULL> ** cat process ends cat /tmp/my_fifo& echo -e ":address_dump:my_fifo\n\n" > /tmp/opensips_fifo ** nothing At this point, I can't make the fifo work again until I restart opensips. If I detach from the fifo (kill the cat, so to speak), and reattach it doesn't work. Nothing seems to make it responsive again. At first I though something was horribly broken, but then I removed one of my \n from the fifo command and now it works "as expected". Two new-lines shouldn't break the fifo, right? Thanks! -Brett ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] db_oracle module not working
Hello, As far as I can see, the db_oracle module is exporting the use_table function. both in trunk and in the stable 1.6 releases. Are you sure you are using the proper sources ? Regards, -- Vlad Paiu OpenSIPS Developer On 05/07/2011 09:36 AM, Abid Saleem wrote: Hi, I have compiled db_oracle fine with OSIPS 1.6.X. Now when I change my opensipsctlrc file to connect to Oracle and load module db_oracle in opensips.cfg and then start opensips, it is giving me following error. Can somebody help me with this as quickly as possible. Here are the errors I receive in log file. May 7 11:29:22 opensips /usr/local/sbin/opensips[5969]: ERROR:core:db_check_api: module db_oracle does not export db_use_table function May 7 11:29:22 opensips /usr/local/sbin/opensips[5969]: ERROR:usrloc:mod_init: failed to bind database module May 7 11:29:22 opensips /usr/local/sbin/opensips[5969]: ERROR:core:init_mod: failed to initialize module usrloc May 7 11:29:22 opensips /usr/local/sbin/opensips[5969]: ERROR:core:main: error while initializing modules Help Help Help Plzz. Rgrds Abid Saleem ___ 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
[OpenSIPS-Users] Pjsip dialler with openIMS core
Hello everybody, I want to know main criteria or parameters which i have to fulfill if i want to register* pjsip dialer* with openIMS core. When i try to register pjsip dialler with openims core my server send does not send "Authorization " to pjsip in response and then 504 (request time out) in end. So any one can please help me in this. -- *Abid khan * ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
[OpenSIPS-Users] New CDRTool release 8.1.0
Hello, There is a new release of CDRTool with support for microseconds accuracy for datetime columns of OpenSIPS data source. cdrtool (8.1.0) unstable; urgency=low [ Rating Engine ] * Added microseconds accuracy for datetime storage columns See setup/radius/OpenSIPS/now_usec.readme * Skip printing data source names that are not going to be normalized * Removed pass by reference statements incompatible with PHP 5.3.3 * Added code 476 to SIP response codes For how to upgrade your installation see: http://cdrtool.ag-projects.com/wiki/Install Regards, Adrian ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
