PWDasterisk thanks for your help
1.
>did you do a tracert (windows) or traceroute (linux) from outside your network against your IPcop reported WAN IP address to verify the dyndns service is resolving correctly? this will eliminate internet routing as an issue.when i do a
tracert i get
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
c:\tracert myfpxsmeserver.dnsalias.com
Tracing route to myfpbsmeserver.dnsalias.com [41.133.125.129]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms test.gateway [10.0.10.10]
2 29 ms 29 ms 29 ms 41-133-124-1.dsl.iworld.co.au [41.133.124.1]
3 34 ms 40 ms 38 ms tengig-0-0-0-100.vic-ipc-2.iworld.co.au [196.22.163.206]
4 32 ms 39 ms 39 ms ccb-ap2522-1-gw.iworld.net [196.22.163.209]
5 40 ms 38 ms 43 ms 41-133-66-1.dsl.iworld.co.au [41.133.66.1]
6 60 ms 59 ms 59 ms 41-133-225-179.dsl.iworld.co.au [41.133.125.129]
Trace complete.
2.
>did you test the ZOIPER client internally to your network to those SAME extensions in FreePBX to make sure the IAX protocol and extensions are setup correctly before trying remote access? this will eliminate SME & FreePBX LAN issues as a source of the problems.Zoiper Client Internally on the Lan works fine infact when i vpn into the network remotely both sip and iax can be used with the zoiper client without any problems
3.
>are the remote clients also behind a firewall and do you know or can you control the remote networks setup?yes they are behind a firewall but that can easly be resolved, no problem there
any ideas?
