7 Mar
2008
7 Mar
'08
12:09 p.m.
Easy answer: none.
If there is a packet on a port SER is listening to, it will try to parse
it. If you don't see it with xlog, there should be an error log message
or it is dropped in a firewall.
g-)
Mike Trest - Personal wrote:
Hi,
I have see recent discussions on this topic among developers
but I am trying to ask a general question without getting into
ser.cfg and 0.9x vs 2.x comparisons.
My Question:
What are the practical reasons why SER 2.0 would simply ignore "BYE"
messages sent to it from a gateway when the user terminates a call?
user => gateway => ser => gateway
Good connection and conversation. When the user hangs up
Gateway sends BYE message. SER does not reply or forward
to destination gateway. SER never even sees it.
I see the BYE message on tshark but it does not appear in ser.cfg
with xlog() statements right at the top or route{}.
Anyone with an opinion or suggestion to offer?
..mike..
_______________________________________________
Serusers mailing list
Serusers(a)lists.iptel.org
http://lists.iptel.org/mailman/listinfo/serusers