Mario,<br><br>Try doing "sofia global siptrace on" when your system is in this state. It will definitely turn on sip trace for every profile on your system. It looks like these are failed outbound registrations, correct? Are you using domain names or IP addresses for these gateways? I'm just curious. I've seen situations where FS could not resolve the domain name for some odd reason.<br>
<br>-MC<br><br><div class="gmail_quote">On Mon, Oct 25, 2010 at 3:26 PM, Mario <span dir="ltr"><<a href="mailto:mario_fs@mgtech.com">mario_fs@mgtech.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
I really need help on this as I have weeks into this problem. I thought I had it nailed but I guess not. After 5.5 hours I get:<br>
2010-10-25 15:05:43.407272 [WARNING] sofia_reg.c:387 mguuid Failed Registration, setting retry to 15 seconds.<br>
2010-10-25 15:05:49.557478 [NOTICE] sofia_reg.c:342 Registering mvuuid<br>
2010-10-25 15:05:59.206273 [NOTICE] sofia_reg.c:342 Registering mguuid<br>
2010-10-25 15:06:04.923157 [WARNING] sofia_reg.c:387 mynum777 Failed Registration, setting retry to 30 seconds.<br>
2010-10-25 15:06:05.358321 [WARNING] sofia_reg.c:387 mvuuid Failed Registration, setting retry to 15 seconds.<br>
2010-10-25 15:06:16.125060 [WARNING] sofia_reg.c:387 mguuid Failed Registration, setting retry to 15 seconds.<br>
2010-10-25 15:06:21.151240 [NOTICE] sofia_reg.c:342 Registering mvuuid<br>
2010-10-25 15:06:33.060421 [NOTICE] sofia_reg.c:342 Registering mguuid<br>
2010-10-25 15:06:35.392655 [NOTICE] sofia_reg.c:342 Registering mynum777<br>
<br>
and no way to make/get calls until I restart FS. I did this:<br>
1. log 7<br>
2. sofia profile xxxx siptrace on for each profile/gateway<br>
3. restarted router<br>
<br>
All three did not solve the problem. The trace and log produced no additional lines which is why I am wondering if FS has a problem since the trace shows no SIP activity.<br>
<br>
3 gateways with 2 ITSPs<br>
2 DSL/WAN lines, 1 static and 1 dynamic<br>
I am using autonat:1.2.3.4 in internal and external profiles. 1.2.3.4 is the external static ip.<br>
sofia status profile ... has the right ext ip<br>
nat_map status shows the dynamic (wrong) IP<br>
I tried starting with -nonat but that was worse<br>
the only way to fix is restart FS.<br>
<br>
I read the wiki on external nat, auto_nat and everything else many times.<br>
Thanks Mario<br>
<br>
<br>
_______________________________________________<br>
FreeSWITCH-users mailing list<br>
<a href="mailto:FreeSWITCH-users@lists.freeswitch.org">FreeSWITCH-users@lists.freeswitch.org</a><br>
<a href="http://lists.freeswitch.org/mailman/listinfo/freeswitch-users" target="_blank">http://lists.freeswitch.org/mailman/listinfo/freeswitch-users</a><br>
UNSUBSCRIBE:<a href="http://lists.freeswitch.org/mailman/options/freeswitch-users" target="_blank">http://lists.freeswitch.org/mailman/options/freeswitch-users</a><br>
<a href="http://www.freeswitch.org" target="_blank">http://www.freeswitch.org</a><br>
</blockquote></div><br>