[asterisk-bugs] [Asterisk 0011428]: incorrectly recognized codecs capabilities of windows mobile 6 device

[noreply at bugs.digium.com]

The following issue has been RESOLVED. 
====================================================================== 
http://bugs.digium.com/view.php?id=11428 
====================================================================== 
Reported By:                pj
Assigned To:                oej
====================================================================== 
Project:                    Asterisk
Issue ID:                   11428
Category:                   Channels/chan_sip/CodecHandling
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     resolved
Asterisk Version:            SVN 
SVN Branch (only for SVN checkouts, not tarball releases):  trunk 
SVN Revision (number only!): 89551 
Disclaimer on File?:        N/A 
Request Review:              
Resolution:                 no change required
Fixed in Version:           
====================================================================== 
Date Submitted:             11-30-2007 10:41 CST
Last Modified:              12-04-2007 10:22 CST
====================================================================== 
Summary:                    incorrectly recognized codecs capabilities of
windows mobile 6 device
Description: 
Native voip/sip client (RTC/1.5) from windows mobile 6, reports in sdp,
that supports codecs:
siren,g722,alaw,ulaw,red 
asterisk this offer recognizes, but in further negotiation it interprets
as folowing capabilities:
peer - audio=0xc1c (ulaw|alaw|g726|ilbc|g726aal2)
combined - 0x400 (ilbc)
call fails, because ilbc is not supported in windows mobile and codec ilbc
isn't even offered in sdp from windows mobile device

====================================================================== 

---------------------------------------------------------------------- 
 oej - 12-04-07 10:22  
---------------------------------------------------------------------- 
Already resolved. Thanks for reporting this bug. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
12-04-07 10:22  oej            Resolution               open => no change
required
12-04-07 10:22  oej            Note Added: 0074755                          
======================================================================