[Ekiga-devel-list] [Fwd: Re: [Callweaver-dev] Default to additional RTP payload type 2 handling for RFC3551-violating G.726 codec peers?]

[thomas schorpp <thomas schorpp googlemail com>]

see attachment.

y
tom

--- Begin Message ---

• From: Steve Underwood <steveu coppice org>
• To: thomas schorpp googlemail com, Developers Mailing List <callweaver-dev callweaver org>
• Subject: Re: [Callweaver-dev] Default to additional RTP payload type 2 handling for RFC3551-violating G.726 codec peers?
• Date: Mon, 10 Mar 2008 06:47:14 +0800

thomas schorpp wrote:

thomas schorpp wrote:

http://www.callweaver.org/ticket/344
1.2RC Revision: 4582

Silently failing calls with all peers still using payload type 2 for G.726 codec and log flooding with

NOTICE[xxxxxxxxxx] rtp.c: Unknown RTP codec 2 received
will occur without -DUSE_DEPRECATED_G726 compiler defined CW builds.

Please discuss adding configure switch defaulting to YES for -DUSE_DEPRECATED_G726. Tested OK here.

Any drawbacks?

y
tom

drawback #1: ekiga 2.0.11 sets up G.721 instead G.726 for payload type 2
if called.

That is not a drawback. G.721 is the same as G.726. This is the very reason why the change is being asked for. Ekiga is broken, and follows an ancient non-standard Cisco practice.

Steve

--- End Message ---