Is pkg_malloc some sort of memory management thing?
I mean, do I have to clean up, or does something come in and clean
up behind me?
Is there a parent/child memory mallocator available? It
would make freeing easier. A single free of the parent
rather than keeping track myself.
I just don't want to be the source of a memory leak.
---greg
thx for the help so far, but the adventure continues:
compiled latest ser from CVS on sol8 from scratch..
and still using the same ser.cfg
but can't start ser anymore, that's what the log shows:
0(15264) loading module /usr/local/lib/ser/modules/mysql.so
0(15264) loading module /usr/local/lib/ser/modules/sl.so
0(15264) loading module /usr/local/lib/ser/modules/tm.so
0(15264) loading module /usr/local/lib/ser/modules/rr.so
0(15264) loading module /usr/local/lib/ser/modules/maxfwd.so
0(15264) loading module /usr/local/lib/ser/modules/usrloc.so
0(15264) loading module /usr/local/lib/ser/modules/registrar.so
0(15264) loading module /usr/local/lib/ser/modules/auth.so
0(15264) find_param_export: found <db_mode> in module usrloc [/usr/local/lib/ser/modules/usrloc.so]
0(15264) find_param_export: found <calculate_ha1> in module auth [/usr/local/lib/ser/modules/auth.so]
0(15264) find_param_export: found <password_column> in module auth [/usr/local/lib/ser/modules/auth.so]
0(15264) find_export: found <mf_process_maxfwd_header> in module maxfwd_module [/usr/local/lib/ser/modules/maxfwd.so]
0(15264) find_export: found <sl_send_reply> in module sl_module [/usr/local/lib/ser/modules/sl.so]
0(15264) find_export: found <sl_send_reply> in module sl_module [/usr/local/lib/ser/modules/sl.so]
0(15264) find_export: <rewriteFromRoute> not found
0(15264) parse error (79,19-20): unknown command, missing loadmodule?
0(15264) find_export: found <www_authorize> in module auth [/usr/local/lib/ser/modules/auth.so]
0(15264) find_export: found <www_challenge> in module auth [/usr/local/lib/ser/modules/auth.so]
0(15264) find_export: found <save> in module registrar [/usr/local/lib/ser/modules/registrar.so]
0(15264) find_export: found <lookup> in module registrar [/usr/local/lib/ser/modules/registrar.so]
0(15264) find_export: found <sl_send_reply> in module sl_module [/usr/local/lib/ser/modules/sl.so]
0(15264) find_export: found <t_relay> in module tm [/usr/local/lib/ser/modules/tm.so]
0(15264) find_export: found <sl_reply_error> in module sl_module [/usr/local/lib/ser/modules/sl.so]
ERROR: bad config file (1 errors)
0(15264) INFO: signal 15 received
0(15264) Memory status (pkg):
0(15264) qm_status (72d38):
0(15264) heap size= 1022872
0(15264) used= 0, used+overhead=25704, free=997168
0(15264) max used (+overhead)= 25704
0(15264) dumping all allocked. fragments:
0(15264) dumping free list stats :
0(15264) hash= 521. fragments no.: 1
0(15264) -----------------------------
anyone a pointer to what i have missed?
tia again
-k
i was messing around with the postgres build over the last couple of days.
I've rebuilt it several times. A few make installs later I went back
to edit my ser.cfg file, it was overwritten by the new installation.
ouch...
---greg
Greg Fausak
Hi,
Is anyone aware of any IPv6 compliant SIP softphone? When will sipsak implement
this feature?
Jaime
*******************************************************************************
Important.
Confidentiality: This communication is intended for the above-named person and
may be confidential and/or legally privileged. Any opinions expressed in this
communication are not necessarily those of the company. If it has come to you
in error you must take no action based on it, nor must you copy or show it to
anyone; please delete/destroy and inform the sender immediately.
Monitoring/Viruses
Orange may monitor all incoming and outgoing emails in line with current
legislation. Although we have taken steps to ensure that this email and
attachments are free from any virus, we advise that in keeping with good
computing practice the recipient should ensure they are actually virus free.
Orange PCS Limited is a subsidiary of Orange SA and is registered in England No
2178917, with its address at St James Court, Great Park Road, Almondsbury Park,
Bradley Stoke, Bristol BS32 4QJ.
*******************************************************************************
I load the auth.so and the default config.
Uncomment those to use auth.so
But when I call up two user agents not register in the database.
The only difference is there a warning for registration.
They are still calling each other. Why?
Has anybody started on support for Postgres?
I've checked out the layering and it seems
to be a fairly modular project. I haven't coded
in C for quite some time, but I think I can handle
it. Any hints? Should I even try?
The only thing I can see having problems with is
the build/configure system. How do I hook in a new
module? How are include directories and new libraries
added? I was pretty good with make, gmake, imake in my day
but I can't seem to find the head of the Make tree!
---greg
Greg Fausak
I'm trying to understand stateful vs. stateless transactions.
A stateless 'transaction' simply lasts as long as it takes to process
the current sip request. It is then forgotten.
However, a stateful transaction I'm having a little problem grasping.
For instance, if I t_relay() an INVITE, logically the transaction is
started....so when the response comes it isn't delivered to the main
route {} block, but instead it is delivered to the awaiting stateful
t_relay(), probably keyed by callid. So, for instance:
INVITE <-
401 Unauthorized ->
Is this entire sequence a transaction? Right after this the UA sends
an ACK, this is a transaction unto itself?
ACK <-
The UA then sends :
INVITE <-
100 Trying ->
180 Ringing ->
200 OK ->
All of these messages are a 'transaction' handled by t_relay()? The next
transaction is:
ACK <-
Finally, the last transaction would be (as an example):
BYE <-
200 OK ->
So the ser route{} block would need to recognize and handle
INVITE
ACK
BYE
in this context. Is that correct? If I was running 'statelessly'
I would need to handle and send every single message listed?
---greg
Thanks a lot. It seems that the log line
> 5(391) authorize(): Invalid nonce value received, very suspicious !
is the key -- Jan will probably handle that better than myself.
Are you sure you applied the solaris/digest patch?
(See nonce validation in ISSUES on SER's website. See also
the topmost solaris-specific issue -- better take SER sources
and recompile them without DBG_QM_MALLOC in Makefile.defs)
If things don't work then, send me please captured SIP messages too.
(Use tools like "ngrep port 5060" to record them.)
Thanks,
-Jiri