| Author |
|
Jalal
Vetran
Joined: April 24 2006
Location: Iran
Posts: 188
|
| Posted: April 09 2007 at 2:51am | IP Logged
|
|
|
Hi,
When we tried to add G729A or iLBC_20_Ms to the supported codecs with SetAudioMediaFormats function, we encountered SipBadAudioDataType error result. This problem does not exists when working with G729 or iLBC_30_Ms. These codecs work with SetAudioMediaFormat but does not work with SetAudioMediaFormats.
I think this is a bug. Please tell me if I am wrong.
Thanks
Jalal Abedinejad
|
| Back to Top |
|
| |
support
Administrator
Joined: January 26 2005
Location: United States
Posts: 1666
|
| Posted: April 17 2007 at 4:52pm | IP Logged
|
|
|
Hi Jalal,
We will look into it. We have a utility engineering multiline soft phone here that does what you are saying. We will verify to make sure things are working as expected.
Hold on...
Support
|
| Back to Top |
|
| |
support
Administrator
Joined: January 26 2005
Location: United States
Posts: 1666
|
| Posted: April 19 2007 at 1:01pm | IP Logged
|
|
|
Jalal,
Hmm.. We do not see the error here. The only way you would get that error is if the enumeration values for the MEDIA_FORMAT_AUDIO data type are incorrect. Enumeration values should be in the integer range of 0-9. Is it possible the MEDIA_FORMAT_AUDIO values you are passing are corrupt?
Let us know if you are still seeing this error.
Support
|
| Back to Top |
|
| |
Jalal
Vetran
Joined: April 24 2006
Location: Iran
Posts: 188
|
| Posted: May 02 2007 at 12:29am | IP Logged
|
|
|
Hi,
We spend more time on this topic, and we have found following:
1- G729,G729A can not be set simultanously as MEDIA_FORMAT_AUDIO to SetAudioMediaFormats function. (I think this is becuase they have equal output but different algorithms).
2- iLBC_20Ms, iLBC_30Ms can not be set simultanously as MEDIA_FORMAT_AUDIO to SetAudioMediaFormats function. (Again I think this is becuase they have equal output but different algorithms).
3- When we set G729A without G729 then in INVITE SIP message G729 was listed instead of G729A. The same issue exists for iLBC_20 and iLBC_30.
I think you could explain these on your Software Developer's Guide.
Regards,
Jalal
|
| Back to Top |
|
| |
support
Administrator
Joined: January 26 2005
Location: United States
Posts: 1666
|
| Posted: May 02 2007 at 8:50am | IP Logged
|
|
|
Hi Jalal,
Item 1:
Yes. This is correct. G729 and G729A are bit for bit compatible over the wire (i.e. the data that is carried in the RTP payloads).
Also:
Another reason G729 and G729A cannot be specified at the same time is because the session description (using sdp) in the SIP INVITE that gets transmitted for the call can only specify the G729 media payload type. Take a look at a SIP log for a call that uses G729 and then for one that uses G729A. The session setup will all specify G729 as the media payload type. G729A is used to reduce the CPU load in the app relative to using original G729.
Item 2:
Only one iLBC media type can be specified in the outgoing SIP INVITE. This is because the difference in iLBC interchange is not a codec difference but a mode difference of the same codec. See the INVITE sdp for each type of call. One will use mode=30 and the other will use mode=20 in the sdp of the INVITE.
Item 3:
SIP calls using G729A negotiates the same as if the call uses G729A. It’s the same data over the wire.
Support
|
| Back to Top |
|
| |
support
Administrator
Joined: January 26 2005
Location: United States
Posts: 1666
|
| Posted: May 02 2007 at 10:06am | IP Logged
|
|
|
Also:
<<< You
I think you could explain these on your Software Developer's Guide.
Support >>>
You are correct. We will do this. Thanks.
Support
|
| Back to Top |
|
| |
Active Topics 
Member List 
Search 
Help 
Register 
Login
LanScape Support Forum -> LanScape VOIP Media Engine™ - Technical Support
Topic: SetAudioMediaFormats G729A, iLBC_20_Ms problem
