Well I think you might have to compose your ACL's by hand and not use any of the auto ones.. Aggressive nat will break 302 processing along with transfers.

Can you paste your profile into the email you have now and email it to the list please.

/b


On May 24, 2010, at 3:24 PM, Oleg Khovayko wrote:

Maybe.. but, when I turn ON, I see fs_path-es for outer clients. If it is OFF, I never see fs_pathes.
Can you suggest, how to enforce "fs_path-es without aggressive-nat-detection"?

Also, I see another problem:
My friend in the Ukraine, uses phone behind NAT, too (situation like to Sipdroid - he also behind NAT).

There is his registration record:

Call-ID:        c4e76211@192.168.10.103
User:           1012@192.168.1.5
Contact:        "user" <sip:1012@192.168.1.136:1024;fs_nat=yes;fs_path=sip%3A1012%4091.207.244.1%3A1024>
Agent:          AcctonVoIP/2.5
Status:         Registered(UDP-NAT)(unknown) EXP(2010-05-24 17:49:15)
Host:           olegh.ath.cx
IP:             91.207.244.1
Port:           1024
Auth-User:      1012
Auth-Realm:     olegh.ath.cx
MWI-Account:    1012@192.168.1.5


When he calls me, everything is OK, we can talk each to other.
But, when I call him (from LAN), he receives RING signal, pick up handset -- and we both heard nothing.

Can you suggest, where to search?