Hi Ronald!
Please send your emails always Cc: to the mailing list.
Your ser.cfg is very strange, because your loading and configuring the modules several times - this sould be done only once!
regarding the loose_route block - this is here:
# loose-route processing if (loose_route()) {
--> setflag(9);
t_relay(); break;};
try adding setflag(9) before t_relay!
klaus
Hi,
I added that line and I test a call but I ended the call and looked at acc table, I still can't see BYE, only ACK and INVITE.
-----Original Message----- From: Klaus Darilion [mailto:klaus.mailinglists@pernau.at] Sent: Thursday, May 06, 2004 10:02 PM To: Ronald Ramos Cc: Serusers Subject: Re: [Serusers] mysql accounting problem
Hi Ronald!
Please send your emails always Cc: to the mailing list.
Your ser.cfg is very strange, because your loading and configuring the modules several times - this sould be done only once!
regarding the loose_route block - this is here:
# loose-route processing if (loose_route()) {
--> setflag(9);
t_relay(); break;};
try adding setflag(9) before t_relay!
klaus
huhh, now it's getting harder!
maybe the BYE transaction fails and is therefore not accounted. use ethereal to verify that the BYE transaction really passes ser and that it is successful.
There is also a module parameter (acc\README) which enables accounting also of failed transactions. Maybe this works.
Otherwise I'm running out of solutions :-(
klaus
Ronald Ramos wrote:
Hi,
I added that line and I test a call but I ended the call and looked at acc table, I still can't see BYE, only ACK and INVITE.
-----Original Message----- From: Klaus Darilion [mailto:klaus.mailinglists@pernau.at] Sent: Thursday, May 06, 2004 10:02 PM To: Ronald Ramos Cc: Serusers Subject: Re: [Serusers] mysql accounting problem
Hi Ronald!
Please send your emails always Cc: to the mailing list.
Your ser.cfg is very strange, because your loading and configuring the modules several times - this sould be done only once!
regarding the loose_route block - this is here:
# loose-route processing if (loose_route()) {
--> setflag(9);
t_relay(); break;};
try adding setflag(9) before t_relay!
klaus
U 216.49.197.25:5060 -> 203.87.131.194:5060 BYE sip:00639209061208@203.87.131.194;ftag=ca3e6d17c4a4d565;lr=on SIP/2.0..Max-Forwards: 70..Route: <sip:2009@202.78.69.2 20:46480>..To: "Ronald" sip:2009@203.87.131.194;tag=ca3e6d17c4a4d565..From: sip:00639209061208@203.87.131.194;tag=329 2844558-337267..Call-ID: cbcbe5e5c5b83eaa@192.168.200.2..CSeq: 2 BYE..Via: SIP/2.0/UDP 216.49.197.25:5060;branch=9aca47dc 70c4215f01bf6f206697a827..Contact: sip:25050#639209061208@216.49.197.25:5060..Content-Length: 0.... # U 203.87.131.194:5060 -> 202.78.69.220:46480 BYE sip:2009@202.78.69.220:46480 SIP/2.0..Record-Route: sip:00639209061208@203.87.131.194;ftag=3292844558-337267;lr=on. .Max-Forwards: 69..To: "Ronald" sip:2009@203.87.131.194H;tag=ca3e6d17c4a4d565..From: sip:00639209061208@203.87.131.194 ;tag=3292844558-337267..Call-ID: cbcbe5e5c5b83eaa@192.168.200.2..CSeq: 2 BYE..Via: SIP/2.0/UDP 203.87.131.194;branch=z9hG 4bK773f.26a11ec1.0..Via: SIP/2.0/UDP 216.49.197.25:5060;branch=9aca47dc70c4215f01bf6f206697a827..Contact: sip:25050#63920 9061208@216.49.197.25:5060..Content-Length: 0.... # U 216.49.197.25:5060 -> 203.87.131.194:5060 BYE sip:00639209061208@203.87.131.194;ftag=ca3e6d17c4a4d565;lr=on SIP/2.0..Max-Forwards: 70..Route: <sip:2009@202.78.69.2 20:46480>..To: "Ronald" sip:2009@203.87.131.194;tag=ca3e6d17c4a4d565..From: sip:00639209061208@203.87.131.194;tag=329 2844558-337267..Call-ID: cbcbe5e5c5b83eaa@192.168.200.2..CSeq: 2 BYE..Via: SIP/2.0/UDP 216.49.197.25:5060;branch=9aca47dc 70c4215f01bf6f206697a827..Contact: sip:25050#639209061208@216.49.197.25:5060..Content-Length: 0....
Hi,
I captured this using ngrep and it shows that there is a BYE. It's just that it didn't account it to the database.
Thank you
Ronald
-----Original Message----- From: Klaus Darilion [mailto:klaus.mailinglists@pernau.at] Sent: Thursday, May 06, 2004 11:41 PM To: Ronald Ramos Cc: serusers@lists.iptel.org Subject: Re: [Serusers] mysql accounting problem
huhh, now it's getting harder!
maybe the BYE transaction fails and is therefore not accounted. use ethereal to verify that the BYE transaction really passes ser and that it is successful.
There is also a module parameter (acc\README) which enables accounting also of failed transactions. Maybe this works.
Otherwise I'm running out of solutions :-(
klaus
Ronald Ramos wrote:
Hi,
I added that line and I test a call but I ended the call and looked at
acc table, I still can't see BYE, only ACK and INVITE.
-----Original Message----- From: Klaus Darilion [mailto:klaus.mailinglists@pernau.at] Sent: Thursday, May 06, 2004 10:02 PM To: Ronald Ramos Cc: Serusers Subject: Re: [Serusers] mysql accounting problem
Hi Ronald!
Please send your emails always Cc: to the mailing list.
Your ser.cfg is very strange, because your loading and configuring the modules several times - this sould be done only once!
regarding the loose_route block - this is here:
# loose-route processing if (loose_route()) {
--> setflag(9);
t_relay(); break;};
try adding setflag(9) before t_relay!
klaus
http://iptel.org/cgi-bin/fom?file=107
-jiri
At 01:45 AM 5/7/2004, Ronald Ramos wrote:
U 216.49.197.25:5060 -> 203.87.131.194:5060 BYE sip:00639209061208@203.87.131.194;ftag=ca3e6d17c4a4d565;lr=on SIP/2.0..Max-Forwards: 70..Route: <sip:2009@202.78.69.2 20:46480>..To: "Ronald" sip:2009@203.87.131.194;tag=ca3e6d17c4a4d565..From: sip:00639209061208@203.87.131.194;tag=329 2844558-337267..Call-ID: cbcbe5e5c5b83eaa@192.168.200.2..CSeq: 2 BYE..Via: SIP/2.0/UDP 216.49.197.25:5060;branch=9aca47dc 70c4215f01bf6f206697a827..Contact: sip:25050#639209061208@216.49.197.25:5060..Content-Length: 0.... # U 203.87.131.194:5060 -> 202.78.69.220:46480 BYE sip:2009@202.78.69.220:46480 SIP/2.0..Record-Route: sip:00639209061208@203.87.131.194;ftag=3292844558-337267;lr=on. .Max-Forwards: 69..To: "Ronald" sip:2009@203.87.131.194H;tag=ca3e6d17c4a4d565..From: sip:00639209061208@203.87.131.194 ;tag=3292844558-337267..Call-ID: cbcbe5e5c5b83eaa@192.168.200.2..CSeq: 2 BYE..Via: SIP/2.0/UDP 203.87.131.194;branch=z9hG 4bK773f.26a11ec1.0..Via: SIP/2.0/UDP 216.49.197.25:5060;branch=9aca47dc70c4215f01bf6f206697a827..Contact: sip:25050#63920 9061208@216.49.197.25:5060..Content-Length: 0.... # U 216.49.197.25:5060 -> 203.87.131.194:5060 BYE sip:00639209061208@203.87.131.194;ftag=ca3e6d17c4a4d565;lr=on SIP/2.0..Max-Forwards: 70..Route: <sip:2009@202.78.69.2 20:46480>..To: "Ronald" sip:2009@203.87.131.194;tag=ca3e6d17c4a4d565..From: sip:00639209061208@203.87.131.194;tag=329 2844558-337267..Call-ID: cbcbe5e5c5b83eaa@192.168.200.2..CSeq: 2 BYE..Via: SIP/2.0/UDP 216.49.197.25:5060;branch=9aca47dc 70c4215f01bf6f206697a827..Contact: sip:25050#639209061208@216.49.197.25:5060..Content-Length: 0....
Hi,
I captured this using ngrep and it shows that there is a BYE. It's just that it didn't account it to the database.
Thank you
Ronald
-----Original Message----- From: Klaus Darilion [mailto:klaus.mailinglists@pernau.at] Sent: Thursday, May 06, 2004 11:41 PM To: Ronald Ramos Cc: serusers@lists.iptel.org Subject: Re: [Serusers] mysql accounting problem
huhh, now it's getting harder!
maybe the BYE transaction fails and is therefore not accounted. use ethereal to verify that the BYE transaction really passes ser and that it is successful.
There is also a module parameter (acc\README) which enables accounting also of failed transactions. Maybe this works.
Otherwise I'm running out of solutions :-(
klaus
Ronald Ramos wrote:
Hi,
I added that line and I test a call but I ended the call and looked at
acc table, I still can't see BYE, only ACK and INVITE.
-----Original Message----- From: Klaus Darilion [mailto:klaus.mailinglists@pernau.at] Sent: Thursday, May 06, 2004 10:02 PM To: Ronald Ramos Cc: Serusers Subject: Re: [Serusers] mysql accounting problem
Hi Ronald!
Please send your emails always Cc: to the mailing list.
Your ser.cfg is very strange, because your loading and configuring the modules several times - this sould be done only once!
regarding the loose_route block - this is here:
# loose-route processing if (loose_route()) {
--> setflag(9);
t_relay(); break;};
try adding setflag(9) before t_relay!
klaus
Serusers mailing list serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
-- Jiri Kuthan http://iptel.org/~jiri/
In your dump I see 2 BYE messages sent to the SIP proxy. So the BYE message is retransmitted. Further I don't see a 200 OK reply to the BYE message. I guess this causes the problems.
Klaus
Ronald Ramos wrote:
U 216.49.197.25:5060 -> 203.87.131.194:5060 BYE sip:00639209061208@203.87.131.194;ftag=ca3e6d17c4a4d565;lr=on SIP/2.0..Max-Forwards: 70..Route: <sip:2009@202.78.69.2 20:46480>..To: "Ronald" sip:2009@203.87.131.194;tag=ca3e6d17c4a4d565..From: sip:00639209061208@203.87.131.194;tag=329 2844558-337267..Call-ID: cbcbe5e5c5b83eaa@192.168.200.2..CSeq: 2 BYE..Via: SIP/2.0/UDP 216.49.197.25:5060;branch=9aca47dc 70c4215f01bf6f206697a827..Contact: sip:25050#639209061208@216.49.197.25:5060..Content-Length: 0.... # U 203.87.131.194:5060 -> 202.78.69.220:46480 BYE sip:2009@202.78.69.220:46480 SIP/2.0..Record-Route: sip:00639209061208@203.87.131.194;ftag=3292844558-337267;lr=on. .Max-Forwards: 69..To: "Ronald" sip:2009@203.87.131.194H;tag=ca3e6d17c4a4d565..From: sip:00639209061208@203.87.131.194 ;tag=3292844558-337267..Call-ID: cbcbe5e5c5b83eaa@192.168.200.2..CSeq: 2 BYE..Via: SIP/2.0/UDP 203.87.131.194;branch=z9hG 4bK773f.26a11ec1.0..Via: SIP/2.0/UDP 216.49.197.25:5060;branch=9aca47dc70c4215f01bf6f206697a827..Contact: sip:25050#63920 9061208@216.49.197.25:5060..Content-Length: 0.... # U 216.49.197.25:5060 -> 203.87.131.194:5060 BYE sip:00639209061208@203.87.131.194;ftag=ca3e6d17c4a4d565;lr=on SIP/2.0..Max-Forwards: 70..Route: <sip:2009@202.78.69.2 20:46480>..To: "Ronald" sip:2009@203.87.131.194;tag=ca3e6d17c4a4d565..From: sip:00639209061208@203.87.131.194;tag=329 2844558-337267..Call-ID: cbcbe5e5c5b83eaa@192.168.200.2..CSeq: 2 BYE..Via: SIP/2.0/UDP 216.49.197.25:5060;branch=9aca47dc 70c4215f01bf6f206697a827..Contact: sip:25050#639209061208@216.49.197.25:5060..Content-Length: 0....
Hi,
I captured this using ngrep and it shows that there is a BYE. It's just that it didn't account it to the database.
Thank you
Ronald
-----Original Message----- From: Klaus Darilion [mailto:klaus.mailinglists@pernau.at] Sent: Thursday, May 06, 2004 11:41 PM To: Ronald Ramos Cc: serusers@lists.iptel.org Subject: Re: [Serusers] mysql accounting problem
huhh, now it's getting harder!
maybe the BYE transaction fails and is therefore not accounted. use ethereal to verify that the BYE transaction really passes ser and that it is successful.
There is also a module parameter (acc\README) which enables accounting also of failed transactions. Maybe this works.
Otherwise I'm running out of solutions :-(
klaus
Ronald Ramos wrote:
Hi,
I added that line and I test a call but I ended the call and looked at
acc table, I still can't see BYE, only ACK and INVITE.
-----Original Message----- From: Klaus Darilion [mailto:klaus.mailinglists@pernau.at] Sent: Thursday, May 06, 2004 10:02 PM To: Ronald Ramos Cc: Serusers Subject: Re: [Serusers] mysql accounting problem
Hi Ronald!
Please send your emails always Cc: to the mailing list.
Your ser.cfg is very strange, because your loading and configuring the modules several times - this sould be done only once!
regarding the loose_route block - this is here:
# loose-route processing if (loose_route()) {
--> setflag(9);
t_relay(); break; };
try adding setflag(9) before t_relay!
klaus
----- Original Message ----- From: "Klaus Darilion" klaus.mailinglists@pernau.at To: Ronald Ramos ron@silverbackasp.com Cc: serusers@lists.iptel.org Sent: Friday, May 07, 2004 05:28 PM Subject: [Serusers] mysql accounting problem
In your dump I see 2 BYE messages sent to the SIP proxy. So the BYE message is retransmitted. Further I don't see a 200 OK reply to the BYE message. I guess this causes the problems.
Klaus
Ronald Ramos wrote:
U 216.49.197.25:5060 -> 203.87.131.194:5060 BYE sip:00639209061208@203.87.131.194;ftag=ca3e6d17c4a4d565;lr=on SIP/2.0..Max-Forwards: 70..Route: <sip:2009@202.78.69.2 20:46480>..To: "Ronald" sip:2009@203.87.131.194;tag=ca3e6d17c4a4d565..From: sip:00639209061208@203.87.131.194;tag=329 2844558-337267..Call-ID: cbcbe5e5c5b83eaa@192.168.200.2..CSeq: 2 BYE..Via: SIP/2.0/UDP 216.49.197.25:5060;branch=9aca47dc 70c4215f01bf6f206697a827..Contact: sip:25050#639209061208@216.49.197.25:5060..Content-Length: 0.... # U 203.87.131.194:5060 -> 202.78.69.220:46480 BYE sip:2009@202.78.69.220:46480 SIP/2.0..Record-Route: sip:00639209061208@203.87.131.194;ftag=3292844558-337267;lr=on. .Max-Forwards: 69..To: "Ronald" sip:2009@203.87.131.194H;tag=ca3e6d17c4a4d565..From: sip:00639209061208@203.87.131.194 ;tag=3292844558-337267..Call-ID: cbcbe5e5c5b83eaa@192.168.200.2..CSeq: 2 BYE..Via: SIP/2.0/UDP 203.87.131.194;branch=z9hG 4bK773f.26a11ec1.0..Via: SIP/2.0/UDP 216.49.197.25:5060;branch=9aca47dc70c4215f01bf6f206697a827..Contact: sip:25050#63920 9061208@216.49.197.25:5060..Content-Length: 0.... # U 216.49.197.25:5060 -> 203.87.131.194:5060 BYE sip:00639209061208@203.87.131.194;ftag=ca3e6d17c4a4d565;lr=on SIP/2.0..Max-Forwards: 70..Route: <sip:2009@202.78.69.2 20:46480>..To: "Ronald" sip:2009@203.87.131.194;tag=ca3e6d17c4a4d565..From: sip:00639209061208@203.87.131.194;tag=329 2844558-337267..Call-ID: cbcbe5e5c5b83eaa@192.168.200.2..CSeq: 2 BYE..Via: SIP/2.0/UDP 216.49.197.25:5060;branch=9aca47dc 70c4215f01bf6f206697a827..Contact: sip:25050#639209061208@216.49.197.25:5060..Content-Length: 0....
Hi,
I captured this using ngrep and it shows that there is a BYE. It's just that it didn't account it to the database.
Thank you
Ronald
-----Original Message----- From: Klaus Darilion [mailto:klaus.mailinglists@pernau.at] Sent: Thursday, May 06, 2004 11:41 PM To: Ronald Ramos Cc: serusers@lists.iptel.org Subject: Re: [Serusers] mysql accounting problem
huhh, now it's getting harder!
maybe the BYE transaction fails and is therefore not accounted. use ethereal to verify that the BYE transaction really passes ser and that it is successful.
There is also a module parameter (acc\README) which enables accounting also of failed transactions. Maybe this works.
Otherwise I'm running out of solutions :-(
klaus
Ronald Ramos wrote:
Hi,
I added that line and I test a call but I ended the call and looked at
acc table, I still can't see BYE, only ACK and INVITE.
-----Original Message----- From: Klaus Darilion [mailto:klaus.mailinglists@pernau.at] Sent: Thursday, May 06, 2004 10:02 PM To: Ronald Ramos Cc: Serusers Subject: Re: [Serusers] mysql accounting problem
Hi Ronald!
Please send your emails always Cc: to the mailing list.
Your ser.cfg is very strange, because your loading and configuring the modules several times - this sould be done only once!
regarding the loose_route block - this is here:
# loose-route processing if (loose_route()) {
--> setflag(9);
t_relay(); break; };
try adding setflag(9) before t_relay!
klaus
_______________________________________________ Serusers mailing list serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
-- www.bembang.com
Hi everyone,
I am new in ser and im confuse about the configuration, i also read the documentations but i would like to ask if anyone can post a configuration for mysql accounting, im my syslog i could see 200 replies, what script should i add in the ser.cfg thanks.
----- Original Message ----- From: "Klaus Darilion" klaus.mailinglists@pernau.at To: Ronald Ramos ron@silverbackasp.com Cc: serusers@lists.iptel.org Sent: Friday, May 07, 2004 05:28 PM Subject: [Serusers] mysql accounting problem
In your dump I see 2 BYE messages sent to the SIP proxy. So the BYE message is retransmitted. Further I don't see a 200 OK reply to the BYE message. I guess this causes the problems.
Klaus
Ronald Ramos wrote:
U 216.49.197.25:5060 -> 203.87.131.194:5060 BYE sip:00639209061208@203.87.131.194;ftag=ca3e6d17c4a4d565;lr=on SIP/2.0..Max-Forwards: 70..Route: <sip:2009@202.78.69.2 20:46480>..To: "Ronald" sip:2009@203.87.131.194;tag=ca3e6d17c4a4d565..From: sip:00639209061208@203.87.131.194;tag=329 2844558-337267..Call-ID: cbcbe5e5c5b83eaa@192.168.200.2..CSeq: 2 BYE..Via: SIP/2.0/UDP 216.49.197.25:5060;branch=9aca47dc 70c4215f01bf6f206697a827..Contact: sip:25050#639209061208@216.49.197.25:5060..Content-Length: 0.... # U 203.87.131.194:5060 -> 202.78.69.220:46480 BYE sip:2009@202.78.69.220:46480 SIP/2.0..Record-Route: sip:00639209061208@203.87.131.194;ftag=3292844558-337267;lr=on. .Max-Forwards: 69..To: "Ronald" sip:2009@203.87.131.194H;tag=ca3e6d17c4a4d565..From: sip:00639209061208@203.87.131.194 ;tag=3292844558-337267..Call-ID: cbcbe5e5c5b83eaa@192.168.200.2..CSeq: 2 BYE..Via: SIP/2.0/UDP 203.87.131.194;branch=z9hG 4bK773f.26a11ec1.0..Via: SIP/2.0/UDP 216.49.197.25:5060;branch=9aca47dc70c4215f01bf6f206697a827..Contact: sip:25050#63920 9061208@216.49.197.25:5060..Content-Length: 0.... # U 216.49.197.25:5060 -> 203.87.131.194:5060 BYE sip:00639209061208@203.87.131.194;ftag=ca3e6d17c4a4d565;lr=on SIP/2.0..Max-Forwards: 70..Route: <sip:2009@202.78.69.2 20:46480>..To: "Ronald" sip:2009@203.87.131.194;tag=ca3e6d17c4a4d565..From: sip:00639209061208@203.87.131.194;tag=329 2844558-337267..Call-ID: cbcbe5e5c5b83eaa@192.168.200.2..CSeq: 2 BYE..Via: SIP/2.0/UDP 216.49.197.25:5060;branch=9aca47dc 70c4215f01bf6f206697a827..Contact: sip:25050#639209061208@216.49.197.25:5060..Content-Length: 0....
Hi,
I captured this using ngrep and it shows that there is a BYE. It's just that it didn't account it to the database.
Thank you
Ronald
-----Original Message----- From: Klaus Darilion [mailto:klaus.mailinglists@pernau.at] Sent: Thursday, May 06, 2004 11:41 PM To: Ronald Ramos Cc: serusers@lists.iptel.org Subject: Re: [Serusers] mysql accounting problem
huhh, now it's getting harder!
maybe the BYE transaction fails and is therefore not accounted. use ethereal to verify that the BYE transaction really passes ser and that it is successful.
There is also a module parameter (acc\README) which enables accounting also of failed transactions. Maybe this works.
Otherwise I'm running out of solutions :-(
klaus
Ronald Ramos wrote:
Hi,
I added that line and I test a call but I ended the call and looked at
acc table, I still can't see BYE, only ACK and INVITE.
-----Original Message----- From: Klaus Darilion [mailto:klaus.mailinglists@pernau.at] Sent: Thursday, May 06, 2004 10:02 PM To: Ronald Ramos Cc: Serusers Subject: Re: [Serusers] mysql accounting problem
Hi Ronald!
Please send your emails always Cc: to the mailing list.
Your ser.cfg is very strange, because your loading and configuring the modules several times - this sould be done only once!
regarding the loose_route block - this is here:
# loose-route processing if (loose_route()) {
--> setflag(9);
t_relay(); break; };
try adding setflag(9) before t_relay!
klaus
_______________________________________________ Serusers mailing list serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
-- www.bembang.com
-
Jiri Kuthan -
Klaus Darilion -
Ronald Ramos -
wiggler