If what you've done so far is to have your ITSP use your public IP
address as the target of incoming calls, you may be able to make it
work by adding that public IP address as a domain alias (System ->
Domain screen).
Thanks Scott. That appears to have solved my problem!
Jeff
P.S. I wanted to append a response from another generous list member
(thanks Tony) that explains more clearly how one would properly set up
a split DNS arrangement, for the benefit of other list members:
Ok three things:
Your ZONE is in charge. In this, example.com is the zone.
example.com internally is resolved by DNS server 10.0.0.1, then
10.0.0.1 needs to have the proper DNS records internally that point
to sipx.example.com at 10.0.0.2 (private ip address). sipx should be
configured to use 10.0.0.1 as its dns resolver. 10.0.0.1 could also
be the dns server and the sipx server if you setup sipx to be a dns
server instead at installation.
example.com externally (public internet) is resolved by server
66.66.66.66, then 66.66.66.66 needs to have the proper DNS records
internally that point to sipx.example.com at 77.77.77.77 (public Ip
address).
Independently your ITSP might need to resolve by name, or just by
static IP. I think this example would be called split dns, but the
dns in both instances does not need to be internally on sipx if you
specified another dns internally for sipx to use so it can properly
resolved itself and its records. The public dns for your domain can
be hosted anywhere so long as it can be configured for the record
types needed.
your public IP should have the appropriate firewall or sbc settings
to pass through sip in the method you are sending/receiving it for
remote workers and/or itsp needs (independent sbc, sipxbridge, etc.).
_______________________________________________
sipx-users mailing list [email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-users
Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users
sipXecs IP PBX -- http://www.sipfoundry.org/
