On 4/20/10 12:00 PM, Scott Lawrence wrote:
If they send a call to you on port 5060, that call will 'work', but
transfers of that call will not. If they send it to you on port 5080,
the call will work and will be transferable. You cannot distinguish
these except by looking at the network packets.
Thanks. After work, I will change them back to static and do some
packet dumps ON THE OUTSIDE OF THE FIREWALL (just in case)
I opened a JIRA on the VOIP.MS template issue (I assume a typo in the
xml on the config? anyone know what I can look? Maybe I can fix it?)
The registration to voip.ms directs the calls to port 5080, so if you
use that method and they obey what it tells them to do, then all will be
well. If you use a static route, then that static route must be to port
5080.
--
Michael Scheidell, CTO
Phone: 561-999-5000, x 1259
> *| *SECNAP Network Security Corporation
* Certified SNORT Integrator
* 2008-9 Hot Company Award Winner, World Executive Alliance
* Five-Star Partner Program 2009, VARBusiness
* Best Anti-Spam Product 2008, Network Products Guide
* King of Spam Filters, SC Magazine 2008
______________________________________________________________________
This email has been scanned and certified safe by SpammerTrap(r).
For Information please see http://www.secnap.com/products/spammertrap/
______________________________________________________________________
_______________________________________________
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/
