Hi!
I'm running ser-0.9.6, on FreeBSD 6.1-stable, database backend
is postgresql version 8.1.3.
Today I got errors in logfiles, saying:
messages.2.bz2:May 29 14:35:03 <XXX> /usr/local/sbin/ser[51448]:
ERROR:avpops:dbrow2avp: dbrow contains NULL fields
The similar problem reported in:
http://lists.iptel.org/pipermail/serusers/2005-May/019681.html
with much more detailed description of error, database contents
and config samples.
Patch is trivial, and looks more like a fix to copy'n'paste error:
in mysql/val.c function str2val states:
if (!_s) {
memset(_v, 0, sizeof(db_val_t));
VAL_TYPE(_v) = _t;
VAL_NULL(_v) = 1;
return 0;
}
VAL_NULL(_v) = 0;
and the last line mentions that 'well, that's value is not NULL'.
In postgresql/db_val.c, line 182, function str2valp, the same statement is the:
if (!_s) {
DLOG("str2valp", "got a null value");
VAL_TYPE(_v) = _t;
VAL_NULL(_v) = 1;
return 0;
}
without explicit notification that this is not-NULL value.
More than, nowhere else in this function VAL_NULL(_v) not set to 0.
So, if a value _v.val contained anyting but 0 at the function start,
resulting value will be threated as NULL despite the fact, that _s is NOT NULL.
Patch is obvious, just add VAL_NULL(_v)=0; after cited block (line 188) and
everyting will be ok.
At least for me it's ok for some hours :)
Hi ,
I tried to call from one nokia sip (E61 and other models )phone to another nokia sip phone. The call works fine. The problem comes only when I call from Phone A to Phone B and then immediately cancel the call(from Phone A). The Phone A will hangup the call as it sent CANCEL but the SER will ignore this CANCEL and still send INVITE to Phone B resulting in a ghost call situation.
I tried to capture a log of message and found that Phone A "CANCEL" message is received on SER even before any provisional response from Phone B. Therefor SER doesnot relay this CANCEL request to Phone B. I even checked RFC which clearly says that UAC should not send CANCEL untill it receives any provisional response. I talked to Nokia expert and they said the 100 Trying message from your server is considered as provisional response, therefor behaviour of client is absolutely correct.
Is there any way I can stop 100 Trying message and still run statefull SER, so that I can verify what nokia said. Any ideas suggestions are welcome.
Thanking you all in advance.
Best Regards,
Abdul Qadir
---------------------------------
Don't be flakey. Get Yahoo! Mail for Mobile and
always stay connected to friends.
Hi,
I encountered the following error:
Jun 15 08:57:21 rd ser[12680]: ERROR: slow timer too slow: overflow (7997 - 6974 = 1023)
Jun 15 08:57:24 rd last message repeated 46 times
Could you please point me what could be the reason?
Thanks in advance.
Tomasz
Guys,
thanks to your support (both Bogdan and Daniel), I found out that
there was nothing wrong with the server and t_onreply handling, but
the INVITE was taking another routing three than the one I was
checking and therefore never hit the t_on_reply section I wanted.
This being said, I consider this issue resolved.
Cheers,
Dan
Hi all,
There are modules that are using default values for AVPs.
What will happen if another module is reusing the same AVP?
Or if the AVP is redefined inside the script?
Is this completely orthogonal?
Should I worry about this while using AVPs?
Regards,
Ovidiu Sas
hi guys!
can somebody explain me how SEMS works with SER/OpenSER.
As I conceive proxy sends requests to SEMS via unix socket. Then SEMS
needs constructs reply or new request and ask proxy to send it. But
where reply come to proxy? into onreply_route[0] block? is it possible
to use t_on_reply() function when initial request writing to SEMS to ask
proxy to use specific onreply_route[] block?
Thanks for advise!
--
CU,
Victor Gamov
The Wikipedia article of OpenSER is subject of a deletion request. The
reasons can be found in this text on the discussion page of "Miconda"
"Notability of OpenSER
A tag has been placed on OpenSER, requesting that it be speedily deleted
from Wikipedia. This has been done because the article appears to be
about a person, group of people, band, club, company, or web content,
but it does not indicate how or why the subject is notable: that is, why
an article about that subject should be included in an encyclopedia.
Under the criteria for speedy deletion, articles that do not assert the
subject's importance or significance may be deleted at any time. Please
see the guidelines for what is generally accepted as notable.
If you think that you can assert the notability of the subject, you may
contest the deletion by adding {{hangon}} to the top of the page (just
below the existing speedy deletion or "db" tag), coupled with adding a
note on the article's talk page explaining your position, but be aware
that once tagged for speedy deletion, if the article meets the criterion
it may be deleted without delay. Please do not remove the speedy
deletion tag yourself, but don't hesitate to add information to the
article that would confirm the subject's notability under Wikipedia
guidelines.
For guidelines on specific types of articles, you may want to check out
our criteria for biographies, for web sites, for bands, or for
companies. Feel free to leave a note on my talk page if you have any
questions about this. Calltech 11:29, 25 July 2007 (UTC)
"
If someone could take care of the article and possibly join the deletion
discussion
(http://en.wikipedia.org/wiki/Wikipedia:Articles_for_deletion/OpenSER) ?
/Klaus
Hello,
I am capturing requirements for MediaProxy 2.0. This is a complete
rewrite based on a new design that allows for better security and end-
point mobility, higher scalability on a per node basis and new
functionality.
If you would like to see new functionality included in MediaProxy
2.0, now is a good moment to describe it.
Regards,
Adrian
Hey everyone,
When I'm doing sequential forking I'm seeing that for each gateway that
doesn't answer and I move forward
in the list of available gateways to forward the INVITE to, openser adds an
"a=nortpproxy:yes" into the SDP
so what happens is that the final gateway which is alive receives the sip
header with multiple lines
of "a=nortpproxy:yes" repeating themselves in the SDP and throws away the
packet.
>From my browsing in nathelper's code I see the only place that writes a
"a=nortpproxy:yes" string to
the SDP is the fix_nated_sdp function, and I'm actually not using it in my
cfg but rather using
fix_nated_register and fix_nated_contact which from what the README says are
not handling
the SDP part.
And so I'm asking, where could it be coming from?
And also, it would be easier if I can insert a piece of code that can do
some regular expression
miracles with the SIP header and remove any duplicate lines of the
"nortpproxy" string.
I'm running on openser 1.1.1
Thanks,
Lir.