Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Submitted By: Brett Nemeroff (brettnem)
Assigned to: Nobody/Anonymous (nobody)
Summary: Gracefully handle misuse of force_rtp_proxy
Right now, if you call force_rtp_proxy twice on the same message, "weird stuff happens" like the c= address getting mangled. Instead of this behavior either:
1. Ignore the second call to force_rtp_proxy()
2. Output an ERROR to syslog indicating the scripting error
3. Both 1&2
I've seen this question a number of times and it's not obvious that it's a scripting error. Point here is to enable users to find this scripting error and fix it without needing to consult the list.