Hi,
In 2.1 the protocols are loaded as modules and there is no disable param at all.
So just set the tcp listener and do loadmodule proto_tcp.so .
Note many parameters related to protocols were changed or moved and the docs
were not yet updated.
Regards,
Bogdan
Sent from Samsung Mobile
Hi all,
I noticed that someone alreay asked same question, what he got is :
because it is against RFC3261 - 6xx reply means global failure and no
further forking is allowed.
http://lists.sip-router.org/pipermail/sr-users/2008-May/017415.html
But i still want to know how others handle this
Hi,
It works like a charm!
Thanks,
Dani
On Sat, Feb 28, 2015 at 2:25 AM, Bogdan-Andrei Iancu bog...@opensips.org
wrote:
Hi Dani,
The socket you set may be ignore if not compatible from proto perspective
with the protocol required by the SIP destination (RURI or DU). If the RURI
requires
OK, in the source tree, i only see proto_tls and proto_sctp
directors under modules. Searching proto_tcp lead me to net directory
which indeed has proto_tcp and proto_udp directories however, there is
no so file, so i guess these protos not compiled by default, however
interestingly they also
Hello,
how or where can i check this?
Thank you
Regards
El 01/03/2015 a las 12:29, Bogdan-Andrei Iancu escribió:
is the presence status of that device correctly visible
___
Users mailing list
Users@lists.opensips.org
The key log is:
Feb 27 14:27:58 sip1 /sbin/opensips[31967]: DBG:pua:send_publish_int:
request for a publish with expires 0 and no record found
But this is harmless - it says it does not want to send an un-PUBLISH
for a presentity already terminated .
The question for you is - is the
