Incorrect Substitution of IP address into B2B URL

[John Larsen]

Hi,

We're looking to upgrade our rtpengine deployments from 12.5 to 13.5, however during testing we've found that the IP address substitution into the `--b2b-url` argument no longer works as expected.

We use the following command line arguments ` --b2b-url=http://%%:5010/RPC2 --xmlrpc-format=1`. In 12.5, `%%` is correctly substituted for the IP address of the proxy, however in 13.5 the IP address and port of the proxy are being substituted, resulting in an invalid URL and the warning log:

`XMLRPC fault occurred: http://10.222.20.194:5009:5010/RPC2 URL using bad/illegal format or missing URL`

As a workaround, we tried adding `xmlrpc-callback` with the IP address to our NG command, it results in just the IP address being substituted. Unfortunately this is not an easy option for us to use in production deployments where we have multi-homed hosts and rely on the kernel to determine the source address for NG commands. Each rtpengine receives calls from many different proxies, so having a fixed address for xmlrpc-callback on the rtpengine command line is not an option either.

It appears this issue was introduced with "MT#55283 upgrade xmlrpc_callback to string". I suspect the fix might be to parse the address out of `created_from` in the case where an IP address is being substituted into `%%` of the b2b-url??

Thanks,

John Larsen

[Richard Fuchs]

Thanks for this, you're absolutely correct of course and this will be fixed ASAP.

Cheers

--
You received this message because you are subscribed to the Google Groups "Sipwise rtpengine" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rtpengine+...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/rtpengine/CAMzt1OqSG4NpGp%2Bpu2_Hv8HRE_uiZNMXiqYsvc5WjJxHwS9GgA%40mail.gmail.com.

[Richard Fuchs]

This has been fixed in all affected releases.

Cheers