Hi,
yes you did it correctly. In the time I prepared the option, I did not
put it into the flags, as you then have to recompile all the modules
(they are used to match the core-module version).... but anyway if you
compile core, you can compile the modules too... so I'll put it there.
Did it help?
I don't have any obvious clue for the log message no UAC support.
Michal
On Ne, 2007-06-03 at 11:58 +0545, KUMAR wrote:
Thanks Michal,
I tried to recompile SER with HONOR_MADDR. Can you please tell me how
do I do it. I changed the Makefile.defs to include -DHONOR_MADDR, and
compiled, but I'm not sure if the option is actually included. Here's
what i get when I do a ser -V
version: ser 2.0.0-rc1 (i386/linux)
flags: STATS: Off, USE_IPV6, USE_TCP, USE_TLS, TLS_HOOKS,
DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MEM, SHM_MMAP, PKG_MALLOC,
DBG_QM_MALLOC, FAST_LOCK-ADAPTIVE_WAIT, USE_DNS_CACHE,
USE_DNS_FAILOVER, USE_DST_BLACKLIST
ADAPTIVE_WAIT_LOOPS=1024, MAX_RECV_BUFFER_SIZE 262144, MAX_LISTEN 16,
MAX_URI_SIZE 1024, BUF_SIZE 65535
poll method support: poll, epoll_lt, epoll_et, sigio_rt, select.
@(#) $Id: main.c,v 1.228.2.2 2007/03/01 13:53:37 andrei Exp $
As you can see, there's no HONOR_MADDR, though it showed up while
compiling. I have attached the Makefile.defs that I've used. Do I need
to do something else to compile with this option? Also, what I failed
to mention last time is that when I log on using M$ client, I get the
message
Warning: run_failure_handlers: no UAC support (0, 0)
Can you please tell me what is this supposed to mean?
Thank you
Kumar
On 5/31/07, Michal Matyska <michal(a)iptel.org> wrote:
Hi,
the M$ messenger is know to misuse maddr parameter in the uri. You can
check your message if it does contain maddr and then try compile ser
with HONOR_MADDR option. It should work; if not attach network capture
of the sip traffic.
Michal
On Čt, 2007-05-31 at 11:32 +0545, KUMAR wrote:
hi all,
I've started using SER 2.0 rc1 and am having a bit of problems with UA
behind NAT. I'm using Windows Messenger 5.1 as the UA. Everything
works fine when both UAs are not behind NAT. But when I place one of
the UAs behind NAT, then, here's what happens, in this order
UA Behind Nat ----------MESSAGE------>UA outside NAT..............ok
UA outside NAT-----------MESSAGE------->UA behind NAT.............OK
UA behind NAT------------MESSAGE------->UA outside
NAT.............message is stored by msilo module and sent after some
time.
The log shows: MSILO: the downstream UA doesn't support MESSAGEs
Notice that this only happens once a message from outside of NAT is
sent to UA inside NAT. I am using RTP Proxy for NAT solution which is
on the same system as SER.
Moreover, I also cannot signout using the Windows Messenger.
However, when I tested using XLite, None of the above mentioned
problems arose. Can anyone please suggest me as to where the problem
might be.
The ser.cfg that I'm using is the one from the iptel site, the one
with NAT & RTPproxy. I am also attaching the ser.cfg.
Thank you in advance.
Kumar
_______________________________________________
Serusers mailing list
Serusers(a)lists.iptel.org
http://lists.iptel.org/mailman/listinfo/serusers
_______________________________________________
Serusers mailing list
Serusers(a)lists.iptel.org
http://lists.iptel.org/mailman/listinfo/serusers