At 09:20 PM 1/29/2004, Matt Hess wrote:
Ok here's another question:
off the same ser.cfg I sent earlier when dialing a number that would go to a pstn.. ie:
route(5) and then rewritehostport("172.16.0.5:5060"); t_relay(); break; I get
the following error messages:
Jan 29 06:06:31 tranquility /usr/local/ser/sbin/ser[22664]: ERROR: t_newtran: transaction
already in process 0x7c1ad7f0
Jan 29 06:06:31 tranquility /usr/local/ser/sbin/ser[22664]: ERROR: t_newtran: transaction
already in process 0x7c1ad7f0
You can't create a transaction for a message twice. You probably call some of
t_newtran or t_relay_* in a row for a single request somewhere in your script.
I must have a hole in my logic somewhere..?
Oh and I did move the setflag to be before record_route(); and I do get invites in the
database but don't receive any bye's.. I've got to be able to get both to do
proper cdr and billing.. yes?
I also get when placing a call to another registered user:
Jan 29 06:11:43 tranquility /usr/local/ser/sbin/ser[5017]: WARNING: t_reply: ACKs are not
replied
Jan 29 06:11:45 tranquility /usr/local/ser/sbin/ser[14527]: WARNING: t_reply: ACKs are not
replied
Jan 29 06:11:48 tranquility /usr/local/ser/sbin/ser[25400]: WARNING: t_reply: ACKs are not
replied
Jan 29 06:11:48 tranquility /usr/local/ser/sbin/ser[14527]: ERROR: t_reply: cannot send a
t_reply to a message for which no T-state has been established
Jan 29 06:11:48 tranquility /usr/local/ser/sbin/ser[14527]: ERROR: t_reply: cannot send a
t_reply to a message for which no T-state has been established
Jan 29 06:11:50 tranquility /usr/local/ser/sbin/ser[6559]: ERROR: t_reply: cannot send a
t_reply to a message for which no T-state has been established
Jan 29 06:11:50 tranquility /usr/local/ser/sbin/ser[6559]: ERROR: t_reply: cannot send a
t_reply to a message for which no T-state has been established
Jan 29 06:11:53 tranquility /usr/local/ser/sbin/ser[5017]: ERROR: t_reply: cannot send a
t_reply to a message for which no T-state has been established
Jan 29 06:11:53 tranquility /usr/local/ser/sbin/ser[5017]: ERROR: t_reply: cannot send a
t_reply to a message for which no T-state has been established
I suppose that the thing happened which the log tells you: you tried to generate a
stateful
reply (t_reply action) without having decided to process the transaction statefuly before
(t_newtran action).
I suppose you did not have a specific reason to use stateful replying, in which case you
will
be better off with stateless replies. They take easier scripts and consume less memory,
so
they ought to be the default choice. Simply replace t_reply with sl_send_reply.
It is hard to tell details without seeing the complete script though.
-jiri