Thank you, Bogdan
mhomed solved my problem. OpenIMS is based on SER but obviously the
parameter is available also there.
Regards
Kenneth
Bogdan-Andrei Iancu skrev:
Hi Kenneth,
not sure what this openims is, but if something from the OpenSIPS
family, the normal behaviour is to preserve the
Hi Chris,
yes, that is the right approach - you can force the outgoing socket via
the socket param.
Regards,
Bogdan
Chris Maciejewski wrote:
Sorry Bogdan,
Ignore my email below. I missed 'socket' option in 't_uac_dlg' MI
function, as described at:
Hi
I have a question that might be related. Honestly it's not an opensips
question, it happens when using openims but I get no answer from that
list so I thought it might be worth a try here. Please ignore this mail
if you think it doesn't belong to this list.
I have assigned two IP addresses
Hi Bogdan,
Thanks for info. I managed to bind to two different ports 5060 and
5566 just fine.
However it seems to me there is a problem with mi_xmlrpc module in
this scenario.
For example when I have Client 1 registered with my.domain:5566
('location' table shows correctly udp:my_ip:5566 in
El Lunes 08 Marzo 2010, Chris Maciejewski escribió:
Hi Bogdan,
Thanks for info. I managed to bind to two different ports 5060 and
5566 just fine.
However it seems to me there is a problem with mi_xmlrpc module in
this scenario.
For example when I have Client 1 registered with
Hi,
I know the answer to this question is probably no, but wanted to
check with you.
Is it possible to make one instance of opensips listen on two different ports?
Lets say if I wanted opensips to listen on UDP/TCP 5060 and UDP/TCP 5566?
Can this be done?
Best regards,
Chris
