[asterisk-bugs] [JIRA] (ASTERISK-27386) asterisk seems to miss udp port change in ok message

[Joshua Colp (JIRA)]

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

Joshua Colp commented on ASTERISK-27386:
----------------------------------------

Thank you for taking the time to report this bug and helping to make Asterisk better. Unfortunately, we cannot work on this bug because your description did not include enough information. Please read over the Asterisk Issue Guidelines [1] which discusses the information necessary for your issue to be resolved and the format that information needs to be in. We would be grateful if you would then provide a more complete description of the problem. At a minimum, we need:

1. The specific steps or actions you took that caused you to encounter the problem.
2. The behavior you expected and the location of documentation that led you to that expectation.
3. The behavior you actually encountered.

To demonstrate the issue in detail, please include Asterisk log files generated per the instructions on the wiki [2]. If applicable, please ensure that protocol-level trace debugging is enabled, e.g., 'sip set debug on' if the issue involves chan_sip, and configuration information such as dialplan and channel configuration.

Thanks!

[1] https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines

[2] https://wiki.asterisk.org/wiki/display/AST/Collecting+Debug+Information

In this particular case we also need to see the Asterisk logs as well.

> asterisk seems to miss udp port change in ok message
> ----------------------------------------------------
>
>                 Key: ASTERISK-27386
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-27386
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>    Affects Versions: 13.17.2
>         Environment: freepbx distro
>            Reporter: Joe Pruett
>         Attachments: ast.pcap
>
>
> i'm attaching a pcap file that shows that the rtp udp port starts at 10474, then goes to 10476 (which asterisk copes with), then in the ok message it switches back to 10474, but asterisk keeps talking to 10476. there are a few icmp unreachables in the mix that don't make sense, but i see those for calls that work, so i'm ignoring them for now.
> backstory:
> on a new test system i was putting together i was having issues where outgoing calls had no audio in either direction. no firewalls or nat were involved. using a sangoma phone with current freepbx. it had been working for months and then stopped working. i was in the middle of dealing with a fire (literal fire) at our office, so i ignored it and am not sure if this was coincident with an update or not.
> after digging into packet dumps, i think i found the problem. the trunk we are using is coming off an adtran and through some copy/paste i had enabled 'ringback override 180' which makes the adtran produce a ring waveform rather than a ring sip message. while doing that it seems to switch the udp ports for the rtp traffic and asterisk misses the last udp change in the ok message and keeps trying to use the port that the ringing comes from (at least that is my theory of what the port change is about).
> an old trixbox system needed the ringback override and it copes with the port changing ok. when i changed the config for the new freepbx to not use the ringback override, then calls started working again.



--
This message was sent by Atlassian JIRA
(v6.2#6252)