Thanks Greger. I set debug to 9 and found the BYE inside the log file. It was seen by SER.
Now I have a trail on the culprit.
..mike..
At 11:24 AM 3/7/2008, Greger Viken Teigre wrote:
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 => gatewayGood 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@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers