#30 Gracefully handle misuse of force_rtp_proxy

open
nobody
modules (91)
5
2009-04-24
2009-04-24
No

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.

Discussion


Log in to post a comment.