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

Aniella Juverdeanu Aniella.Juverdeanu at telus.com
Fri Aug 23 21:42:43 UTC 2013


Hi,

The payload type 18 is standard by RFC 3551 and doesn't need to be declared - payload 18 will always be G.729. Only the dynamic values have to be declared.

PT   encoding    media type  clock rate   channels
                    name                    (Hz)
               ___________________________________________________
               0    PCMU        A            8,000       1
               1    reserved    A
               2    reserved    A
               3    GSM         A            8,000       1
               4    G723        A            8,000       1
               5    DVI4        A            8,000       1
               6    DVI4        A           16,000       1
               7    LPC         A            8,000       1
               8    PCMA        A            8,000       1
               9    G722        A            8,000       1
               10   L16         A           44,100       2
               11   L16         A           44,100       1
               12   QCELP       A            8,000       1
               13   CN          A            8,000       1
               14   MPA         A           90,000       (see text)
               15   G728        A            8,000       1
               16   DVI4        A           11,025       1
               17   DVI4        A           22,050       1
               18   G729        A            8,000       1

Aniella

From: discussion-bounces at sipforum.org [mailto:discussion-bounces at sipforum.org] On Behalf Of anand kumar Vijayan
Sent: August 20, 2013 11:41 PM
To: discussion at sipforum.org; discussion-bounces at sipforum.org
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 :
[cid:image002.png at 01CEA00F.04A922B0]
Sucessful call
[cid:image004.png at 01CEA00F.04A922B0]
Please help us.

Regards
Anand Kumar V
919650930689
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://sipforum.org/pipermail/discussion/attachments/20130823/b5a9ca39/attachment-0002.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.png
Type: image/png
Size: 157340 bytes
Desc: image002.png
URL: <http://sipforum.org/pipermail/discussion/attachments/20130823/b5a9ca39/attachment-0004.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image004.png
Type: image/png
Size: 155021 bytes
Desc: image004.png
URL: <http://sipforum.org/pipermail/discussion/attachments/20130823/b5a9ca39/attachment-0005.png>


More information about the discussion mailing list