I'm writing a utility that uses the sofia-sip.
I have not clear to me phenomenon - API call nua_set_params() does not
change the parameter NUTAG_URL.
Initially, I set the default settings.
appl->nua = nua_create (appl->root,
app_callback,
appl,
/* tags as necessary ...*/
NUTAG_URL ("sip:0.0.0.0:0"),
...
TAG_NULL ());
In the future, I change the address to which the program listens for
incoming connections.
int
sip_listen (char *str)
{
if (*str != '\0') {
strncpy (listn, str, sizeof (listn) - 1);
sprintf (buff, "sip:%s", listn);
nua_set_params (appl->nua,
NUTAG_URL (buff),
TAG_END ());
}
printf ("Listen on: '%s'\n", listn);
return (0);
}
However, after running this function, a set of interfaces that are
listening on ports of the program is not changed. ( In this particular
case, the function run with an argument "192.168.1.15:0")
% sockstat -l4
USER COMMAND PID FD PROTO LOCAL ADDRESS FOREIGN ADDRESS
root sipcc 43186 12 udp4 192.168.31.10:36695 *:*
root sipcc 43186 13 tcp4 192.168.31.10:36695 *:*
root sipcc 43186 14 udp4 192.168.1.15:36695 *:*
root sipcc 43186 15 tcp4 192.168.1.15:36695 *:*
root sipcc 43186 16 udp4 127.0.0.1:36695 *:*
root sipcc 43186 17 tcp4 127.0.0.1:36695 *:*
...
%
(Among other things, option NUTAG_PROXY, switchable similarly, does not
change too.)
What am I doing wrong. How do I fix this?
Ogogon.
------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure
contains a definitive record of customers, application performance,
security threats, fraudulent activity, and more. Splunk takes this
data and makes sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-novd2d
_______________________________________________
Sofia-sip-devel mailing list
Sofia-sip-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sofia-sip-devel
