[OpenSIPS-Users] OpenSIPs Dispatcher checking different ports for Activeness
rmundkowsky at ets.org
Fri Sep 29 11:00:14 EDT 2017
Use ds_set_state to manually mark as active and inactive, or if your backend support SIP OPTIONS, you can use probing to have it automatically enable and disable.
The MI command (ds_set_state) can be sent via command line tool (opensipsctl) or other ways (XML rpc,…).
From: Users [mailto:users-bounces at lists.opensips.org] On Behalf Of Richard Parker
Sent: Thursday, September 28, 2017 5:55 PM
To: users at lists.opensips.org
Subject: [OpenSIPS-Users] OpenSIPs Dispatcher checking different ports for Activeness
This may sound convoluted and I am somewhat at a loss as to how to go about this.
I have a device that is on a old Windows platform that has a SIP Stack on it.
It is fronted by OpenSIPs (which does very well I might add).
I have 4 UDP SIP ports that I am using on the Windows box to dispatch to.
The SIP Stack brings up these 4 ports at boot up. (5060, 5070, 5080 and 5090).
The SIP Stack hands off to another app which takes a LONG time to come up (Various libraries).
When this app is up, it advertises on 4 other UDP ports (5064, 5074, 5084, 5094) another UDP SIP to be able to make sure that all is well.
The problem is, I need to know how to make all dispatched ports as “Inactive” to send to the common ports (5060, 5070, 5080, 5090) UNTIL the Checked ports (5064, 5074, 5084, 5094) are up.
Has anyone done this before?
This e-mail and any files transmitted with it may contain privileged or confidential information. It is solely for use by the individual for whom it is intended, even if addressed incorrectly. If you received this e-mail in error, please notify the sender; do not disclose, copy, distribute, or take any action in reliance on the contents of this information; and delete it from your system. Any other use of this e-mail is prohibited.
Thank you for your compliance.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Users