asterisk users - Feb 2004 - codec negotiation prob solved?

FYI - bug 1043 has been fixed on Feb 18:

"From my log, below, you will see that ast_rtp_bridge is not comparing 
the codecs properly. Asterisk is currently comparing the integers, and 
not the bits of the codec. 

In the below example codec0 = 260. That means Codec0 allows both 256 
(g729) and 4 (uLaw). So that would mean that Codec0 and Codec1 do have a 
"Codec Match". 

Asterisk needs to do a bit compare, and not a int compare in this case."

-- SIP/dialnet-8bac answered SIP/chris0-df00 
-- Attempting native bridge of SIP/chris0-df00 and SIP/dialnet-8bac 
Feb 16 11:27:48 WARNING[68889520]: rtp.c:1204 ast_rtp_bridge: codec0 = 
260 is not codec1 = 256, cannot native bridge. 
Feb 16 11:27:50 NOTICE[68889520]: rtp.c:264 process_rfc3389: RFC3389 
support incomplete. Turn off on client if possible 
Feb 16 11:27:50 NOTICE[68889520]: rtp.c:293 process_rfc3389: Don't know 
how to handle RFC3389 for receive codec 256