Re: xmlrpc-callback syntax

25 views
Skip to first unread message

Richard Fuchs

unread,
Jul 14, 2023, 8:04:17 AM7/14/23
to rtpe...@googlegroups.com
On 11/07/2023 11.07, [EXT] Philippe Debreuil wrote:
> Hello,
>
> I am calling rtpengine_offer from kamailio.cfg
> with parameter string "replace-origin replace-session-connection "
> and wish to add " xmlrpc-callback=127.0.0.1:8080"
> to ask rtpengine to send an event when RTP timeout occurs
>
> my question : is my xmlrpc-callback correct ?
>
> thks a lot
>
> PS: I tried using rtpengine command option
> "b2b-url=http://127.0.0.1:8080" and it works
> but not when using xmlrpc-callback inside kamailio.cfg

The value for `xmlrpc-callback` is just an address, without port. It
will be replaced into the URL given as `b2b-url` wherever the %%
wildcard string appears. So something like `b2b-url=http://%%:8080` plus
`xmlrpc-callback=127.0.0.1` should work.

Cheers

Marcin Kowalczyk

unread,
Jul 23, 2025, 7:30:31 AMJul 23
to Sipwise rtpengine
Hi Richard,

 I have a question - in /etc/rtpengine/rtpengine.conf (quite old one: 12.5.1.9-1) I have 

b2b-url = http://%%:80/RPC

In kamailio rtpengine_manage I add  xmlrpc-callback=preprod-l725nnlsoaao2n3eruklhm9ri5c2s7xt.chte.ch  while capturing ng protcol xmlrpc-callback is there:

15:xmlrpc-callback48:preprod-l725nnlsoaao2n3eruklhm9ri5c2s7xt.chte.ch9:directionl3:ext3:inte5:flagsl18:SIP-source-address13:generate-RTCPe7:replacel6:origine7:call-id20:ic9nrabri32m0naod4c313:received-froml3:IP413:172.20.153.93e8:from-tag10:ahdt93p2906:to-tag13:F2jZ5BZt3Z3ZQ7:command6:answere


but in log I can see warning

Jul 23 11:22:44 rtpengine-eu-ireland-1 rtpengine[3452263]: WARNING: [mi48ragnjvia8ir1eujq]: [core] Failed to parse 'xmlrpc-callback' address 'preprod-l725nnlsoaao2n3eruklhm9ri5c2s7xt.chte.ch'

And callback is not executed.  Does preprod-l725nnlsoaao2n3eruklhm9ri5c2s7xt.chte.ch needs to IP address rather than domain? 

Richard Fuchs

unread,
Jul 23, 2025, 9:06:14 AMJul 23
to rtpe...@googlegroups.com
It does need to be an address, yes, even though now that you mention it, there really isn't a good reason for that requirement, since lookup would be handled by cURL anyway. Should be an easy change.

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/86b4658f-21c5-4346-994e-d5e0f39e5bcbn%40googlegroups.com.
Reply all
Reply to author
Forward
0 new messages