[SIPForum-discussion] In Invite calls are Not sending the proper rtpmap entry for G.729 Codec.

Saurabh Shah saurabh.shah at matrixcomsec.com
Sat Aug 24 04:20:33 UTC 2013


Dear Anand, 


rtpmap is optional when you use static payload number. 
In your both cases, 18 is used for G.729 which is ok. 

----- Original Message -----

From: "anand kumar Vijayan" <anandkumar4n at gmail.com> 
To: discussion at sipforum.org, discussion-bounces at sipforum.org 
Sent: Wednesday, August 21, 2013 12:11:02 PM 
Subject: [SIPForum-discussion] In Invite calls are Not sending the proper rtpmap entry for G.729 Codec. 



Hi All 

We are seeing two types of behavior in INVITE Messge 

In some calls are receving the media information with G.729 and are also sending rtpmap entry for G.729 codec in the 183 Session Progress message But in few other calls are not sending rtpmap entry for G.729 Codec. 

Kindly find attached ethereal trace as well as snapshot for your reference 
How to fix the issue to send proper rtpmap, due to that what kind of issue will happen. 
Problemati call : 

Inline image 1

Sucessful call 
Inline image 2

Please help us. 



Regards 
Anand Kumar V 
919650930689 
_______________________________________________ 
This is the SIP Forum discussion mailing list 
TO UNSUBSCRIBE, or edit your delivery options, please visit http://sipforum.org/mailman/listinfo/discussion 
Post to the list at discussion at sipforum.org 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://sipforum.org/pipermail/discussion/attachments/20130824/6a945248/attachment-0002.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 40454 bytes
Desc: not available
URL: <http://sipforum.org/pipermail/discussion/attachments/20130824/6a945248/attachment-0004.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 46750 bytes
Desc: not available
URL: <http://sipforum.org/pipermail/discussion/attachments/20130824/6a945248/attachment-0005.png>


More information about the discussion mailing list