RTP goes to the address in =o attribute or the address that the sip invite was sent to in some calls about rtpengine HOT 7 CLOSED

Please post the full log from rtpengine for one such call.

from rtpengine.

Hi Richard.

Thank you very much for the response. Would it be possible for me to send you this directly to avoid posting our ip addresses and sip domain names in a public forum? I really appreciate you taking a look at it.

All the best.

Will Ferrer

from rtpengine.

Hi Richard

Sorry for the confusion, what we have to send right now is the sip capture. We have logging turned way down on our deploy boxes.

I will talk my partner that manages that aspect of the servers and see what we can get you (may be able to dial it up for a bit and use our logging software to pick out a call where the issue occured)

In the mean time would the sip capture be useful to look at?

Thanks again for your assistance,

All the best

Will Ferrer

from rtpengine.

SIP capture may help if it includes the SDP both in incoming and outgoing forms. My email address is in my profile.

from rtpengine.

PS: Even better would be if it included the control messages between the SIP proxy and rtpengine

from rtpengine.

Closing this as it was discussed offline. The problem is suspected to originate in the peers.

from rtpengine.

Hi Richard

Thanks again for the assistance.

In order to update the thread, it seems the issue is on our carriers side.
Adding the flag ICE=remove didn't resolve the issue our carriers are having
but it did reduce the occurrences of the issue significantly.

Happy holidays.

Will Ferrer

Switchsoft Inc

On Wed, Dec 17, 2014 at 9:52 AM, Richard Fuchs [email protected]
wrote:

Closing this as it was discussed offline. The problem is suspected to
originate in the peers.

—
Reply to this email directly or view it on GitHub
#45 (comment).

from rtpengine.