Fire up the console and check the debug output when the call first comes in. Look for any references to an acl because that's where you'll see if the call is authing or not...
-MC
Hello,
In debugging that previous problem I noticed another problem.
How do I get freeswitch to authenticate incomming calls? As far as I
can tell it is not working:
483.970655 192.168.87.13 -> 202.173.153.98 SIP/SDP Request: INVITE
sip:9999@202.173.153.98, with session description
483.972989 202.173.153.98 -> 192.168.87.13 SIP Status: 100 Trying
484.180018 202.173.153.98 -> 192.168.87.13 SIP/SDP Status: 200 OK,
with session description
484.208932 192.168.87.13 -> 202.173.153.98 SIP Request: ACK
sip:9999@202.173.153.98:5060;transport=udp
490.634429 192.168.87.13 -> 202.173.153.98 SIP Request: BYE
sip:9999@202.173.153.98:5060;transport=udp
490.637862 202.173.153.98 -> 192.168.87.13 SIP Status: 200 OK
Yet the setting is appears to be enabled:
<param name="auth-calls" value="true"/>
--
Brian May <brian@microcomaustralia.com.au>
_______________________________________________
FreeSWITCH-users mailing list
FreeSWITCH-users@lists.freeswitch.org
http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
http://www.freeswitch.org