[asterisk-bugs] [JIRA] (ASTERISK-23251) G729:60 packet size not being set correctly in SIP Invite

[Jarrod Sears (JIRA)]

    [ https://issues.asterisk.org/jira/browse/ASTERISK-23251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=215092#comment-215092 ] 

Jarrod Sears commented on ASTERISK-23251:
-----------------------------------------

We are not using realtime peers. 

We are using realtime for the extensions/dialplan functionality to dynamically create variable IVRs. There is nothing in our /etc/asterisk/extensions.conf file except the switch directly into realtime.

I will try it outside of realtime as a comparison. I'll also try again with a realtime peer configured and show you the sip show peer result.

Thanks
                
> G729:60 packet size not being set correctly in SIP Invite
> ---------------------------------------------------------
>
>                 Key: ASTERISK-23251
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-23251
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Channels/chan_sip/CodecHandling, Codecs/General, Core/CodecInterface
>    Affects Versions: 1.8.11.1, 11.7.0
>         Environment: CentOS release 6.5 (Final) x64
> MySQL Database
> Dell R320 Server and Dell R210II Server
>            Reporter: Jarrod Sears
>            Assignee: Jarrod Sears
>            Severity: Critical
>         Attachments: g729_issue.log, sip.conf
>
>
> Incoming calls to the server correctly negotiate to g729:60.
> The sip.conf is set to:
> disallow=all
> allow=g729:60
> The outbound leg of the server then sends a SIP invite out specifying g729:20.
> I've tried setting up specific SIP peers and also using the general codec settings, both experience the same issue.
> I have also tried using the SET(SIP_CODEC=G729:60) command, which does not work.
> I have tried using the a server with Digium's g729 codec. I've also tried on a server without a g729 codec. Both experience the same issue.
> I originally experienced the issue on the 1.8.11.1 (Asterisk 1.8.11-cert1) version that we are using generally for production. I recently installed a new copy of Asterisk 11.7.0 and have the same problem.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.asterisk.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira