Hello,
in the first phase add the socket as an attribute for each gateway.
At some point we should look at making some of the attributes as dedicated fields (columns), but I would prefer to make it at once for all attributes that should be split out.
Cheers,
Daniel
On 31/10/14 11:37, Federico Cabiddu wrote:
Hi all,after fighting in the last days with dispatcher and the socket used to send pings and dispatch requests, I'm thinking in adding to the module the support for configuring the sending socket. Specifically what I'm thinking is:
1) add the sending socket as a gateways' parameter2) add an avp to store the gateways' send socket, to be used for load balancing failover3) add a module parameter "ds_send_socket" to define a global socket
The logic to select the sending socket would be:
1) if the gateway has send socket configured, use it2) else, if configured, use the socket specified in ds_send_socket3 else use the socket corresponding to the first listen directive (current behaviour)
What do you think about? Do you find that this would be generally useful?About adding the send socket per gateway: how do you think it should be configured? In a dedicated column (db or file) or in the attrs parameter (just adding another attributes)?
Looking forward to your feedback.
Cheers,
Federico
_______________________________________________ sr-dev mailing list sr-dev@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev
-- Daniel-Constantin Mierla http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
_______________________________________________
sr-dev mailing list
sr-dev@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev