3 Dec
2004
3 Dec
'04
3:03 p.m.
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
3 Dec
3 Dec
3:24 p.m.
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(a)bwsys.net
Customer Service: (877) 976-0711
-----Original Message-----
From: serusers-bounces(a)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(a)lists.iptel.org
http://lists.iptel.org/mailman/listinfo/serusers
5 Dec
5 Dec
3:27 a.m.
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(a)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(a)bwsys.net
Customer Service: (877) 976-0711
__________________________________
Do you Yahoo!?
Yahoo! Mail - 250MB free storage. Do more. Manage less.
http://info.mail.yahoo.com/mail_250
-----Original Message-----
From: serusers-bounces(a)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(a)lists.iptel.org
http://lists.iptel.org/mailman/listinfo/serusers
6 Dec
6 Dec
2:21 p.m.
On Dec 04, 2004 at 19:27, Java Rockx <javarockx(a)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
7163
days inactive
7166
days old
3 comments
3 participants
participants (3)
-
Andrei Pelinescu-Onciul -
Java Rockx -
Michael Shuler