rtpengine-ng-client -- Connection Refused

[Abisai Matangira]

Good Day

I would like to do media forking on already existing used  rtpengine in use ,

 on trying to connect to it with rtpengine-ng-client i am getting  the following

Duplicate specification "sip-source-address" for option "sip-source-address"
Connection refused at /usr/lib64/perl5/vendor_perl/NGCP/Rtpengine.pm line 44.

The port is enabled on firewall and if i try access ng port with echo "{command:ping}" | nc -u z.y.x.78 2223 i can see it in  rtpengine log

There could there be something with rtpengine-ng-client release 12.4.1 causing the error

Is it possible to do call forking though ng-https  as a work around 

Best Regards

Abisai

[Richard Fuchs]

"Connection refused" simply means that the remote port wasn't open. The script tries to talk to localhost by default - if you don't have the port listening on that address, use the --proxy-address=... option to specify a different address.

I'm not sure where the warning about "sip-source-address" is coming from. I definitely don't see it myself on 12.4.1.

I don't understand your question about call forking.

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 on the web visit https://groups.google.com/d/msgid/rtpengine/3c0f5c6f-5256-4a65-9632-5055697b2172n%40googlegroups.com.

[Abisai Matangira]

Thank you  ,  adding --proxy-address=ip:port worked

I would like to do media forking is the   rtpengine-ng-client only way or i could do say through http ng

[Abisai Matangira]

Thanks for the reply 

Sorry I meant media forking through Https Ng on last question 

Let me try  your suggestion 

You received this message because you are subscribed to a topic in the Google Groups "Sipwise rtpengine" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/rtpengine/HuFjRc9O0uE/unsubscribe.
To unsubscribe from this group and all its topics, send an email to rtpengine+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/rtpengine/e46721f7-643d-4c01-8d87-21e15a581e5f%40sipwise.com.

[Richard Fuchs]

On 19/06/2024 09.54, Abisai Matangira wrote:
> Thank you  ,  adding --proxy-address=ip:port worked
>
> I would like to do media forking is the   rtpengine-ng-client only way
> or i could do say through http ng

The ng-client script is just a shell helper to talk the NG protocol to
rtpengine. You can use your own client and using any of the supported
transports just as well. JSON over HTTP(S) or Websocket might be the
easiest to implement from scratch.

Cheers