On Thu, Jul 22, 2010 at 2:13 PM, Nathaniel Watkins < [email protected]> wrote:
> Tim – I did this for a while (over a hear) I had sipx on gcgov.local – The > work around mentioned is under System -> Domain Domain Aliases (see attached > picture). Thanks for you response, this has helped me resolve the issue. Although I had already set up a domain alias, this got me thinking about how the alias is set up and my testing steps. To simplify things, I registered my external IP address as a domain alias and tested. Inbound SIP URI calls went through as expected via port 5060 using 2...@externalipaddress. I think I over complicated things. I realize now that this is actually very simple and I'm sure I'll be able to set this up correctly now using the public host name. Thanks to all who have helped me with this. XMPP federation is not required at this time, so I'm not to concerned about this. If I need it in the future, I'll look into changing the sipXecs machine name and using split DNS. Final question: Why are inbound SIP URI calls via port 5080 connected successfully? This worked even without having the domain alias set up correctly.
_______________________________________________ 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/
