Hello Everyone.
Can anyone give some words of wisdom as to how to include the negotiated codec in my MySQL accounting records?
I'm thinking about something like a new column in the acc table.
Regards, Paul
__________________________________ Do you Yahoo!? The all-new My Yahoo! - What will yours do? http://my.yahoo.com
That's a good idea for trouble shooting fax issues. But it would actually need to store 2 codec values because Asterisk can receive a call on one codec but then can send out the bridging call on another and transcode. I agree, just adding a column and a few lines of code should be it. I'll take a look at it over the weekend.
----------------------------------------
Michael Shuler, C.E.O. BitWise Communications, Inc. (CLEC) And BitWise Systems, Inc. (ISP) 682 High Point Lane East Peoria, IL 61611 Office: (217) 585-0357 Cell: (309) 657-6365 Fax: (309) 213-3500 E-Mail: mike@bwsys.net Customer Service: (877) 976-0711
-----Original Message----- From: serusers-bounces@lists.iptel.org [mailto:serusers-bounces@lists.iptel.org] On Behalf Of Java Rockx Sent: Friday, December 03, 2004 9:04 AM To: ser users Subject: [Serusers] MySQL Accounting - How To Record Negotiated CODEC?
Hello Everyone.
Can anyone give some words of wisdom as to how to include the negotiated codec in my MySQL accounting records?
I'm thinking about something like a new column in the acc table.
Regards, Paul
__________________________________ Do you Yahoo!? The all-new My Yahoo! - What will yours do? http://my.yahoo.com
Serusers mailing list serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
Hi All.
I got the thinking about this and now I'm not so sure it's as easy as I once thought.
At what point in SER do we actually know which CODEC the caller has finally chosen? I mean if CallerA sends an original INVITE to CalleeB and SDP payload of
m=audio 1234 RTP/AVP 97 101 a={iLBC} a={G729} a={GSM} a={ULAW}
and CalleeB replies with 200 OK and the following SDP
m=audio 54324 RTP/AVP 18 101 a={G729} a={ULAW} a={speex} a={iLBC}
Is there anyway to know which CODEC CallerA will really begin sending RTP with? The way RFC3261 reads to me is that CallerA is not obligated to honor G729 as stated in the "200 OK" from CalleeB because the RFC says that CallerA *SHOULD* use G729 but may use any CODEC common to both parties.
So at what point do we actually know the real CODEC that is used?
Also, accounting seems to become difficult because I would rather only account for INVITE and BYE messages because of the shear number of ACKs and other types that clutter our CDR table.
Thoughts anyone?
Regards, Paul
--- Michael Shuler mike@bwsys.net wrote:
That's a good idea for trouble shooting fax issues. But it would actually need to store 2 codec values because Asterisk can receive a call on one codec but then can send out the bridging call on another and transcode. I agree, just adding a column and a few lines of code should be it. I'll take a look at it over the weekend.
Michael Shuler, C.E.O. BitWise Communications, Inc. (CLEC) And BitWise Systems, Inc. (ISP) 682 High Point Lane East Peoria, IL 61611 Office: (217) 585-0357 Cell: (309) 657-6365 Fax: (309) 213-3500 E-Mail: mike@bwsys.net Customer Service: (877) 976-0711
-----Original Message----- From: serusers-bounces@lists.iptel.org [mailto:serusers-bounces@lists.iptel.org] On Behalf Of Java Rockx Sent: Friday, December 03, 2004 9:04 AM To: ser users Subject: [Serusers] MySQL Accounting - How To Record Negotiated CODEC?
Hello Everyone.
Can anyone give some words of wisdom as to how to include the negotiated codec in my MySQL accounting records?
I'm thinking about something like a new column in the acc table.
Regards, Paul
__________________________________ Do you Yahoo!? The all-new My Yahoo! - What will yours do? http://my.yahoo.com
Serusers mailing list serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
__________________________________ Do you Yahoo!? Yahoo! Mail - 250MB free storage. Do more. Manage less. http://info.mail.yahoo.com/mail_250
On Dec 04, 2004 at 19:27, Java Rockx javarockx@yahoo.com wrote:
Hi All.
I got the thinking about this and now I'm not so sure it's as easy as I once thought.
At what point in SER do we actually know which CODEC the caller has finally chosen? I mean if CallerA sends an original INVITE to CalleeB and SDP payload of
m=audio 1234 RTP/AVP 97 101 a={iLBC} a={G729} a={GSM} a={ULAW}
and CalleeB replies with 200 OK and the following SDP
m=audio 54324 RTP/AVP 18 101 a={G729} a={ULAW} a={speex} a={iLBC}
Is there anyway to know which CODEC CallerA will really begin sending RTP with? The way RFC3261 reads to me is that CallerA is not obligated to honor G729 as stated in the "200 OK" from CalleeB because the RFC says that CallerA *SHOULD* use G729 but may use any CODEC common to both parties.
The only way is to catch the rtp and match the codec no. with the codec numbers advertised in the sip messages.
Andrei