[sr-dev] git:sr_3.0: seas: use set_force_socket()

Module: sip-router Branch: sr_3.0 Commit: 710b07269cc63a7ddf7323d68bcb619bd4d63816 URL: http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=710b072… Author: Andrei Pelinescu-Onciul <andrei(a)iptel.org> Committer: Andrei Pelinescu-Onciul <andrei(a)iptel.org> Date: Thu Nov 5 15:17:15 2009 +0100 seas: use set_force_socket() - use set_force_socket() instead of msg->force_send_socket --- modules_k/seas/seas_action.c | 4 +++- 1 files changed, 3 insertions(+), 1 deletions(-) diff --git a/modules_k/seas/seas_action.c b/modules_k/seas/seas_action.c index 15e4030..2b7335a 100644 --- a/modules_k/seas/seas_action.c +++ b/modules_k/seas/seas_action.c @@ -817,7 +817,9 @@ int ac_sl_msg(as_p the_as,char *action,int len) }else{ uri = GET_RURI(my_msg); } - my_msg->force_send_socket=grep_sock_info(&my_msg->via1->host,my_msg->via1->port,my_msg->via1->proto); + set_force_socket(my_msg, grep_sock_info(&my_msg->via1->host, + my_msg->via1->port, + my_msg->via1->proto) ); /* or also could be: my_msg->force_send_socket=the_as->binds[processor_id].bind_address; not sure which is better...