For more information on configuring an Exchange Server 2013, review this 3CX blog post.
To download this update, simply login to the 3CX Windows Management Console from Start, All Programs, 3CX Phone System, Windows Management Console and navigate to the 3CX Phone System Updates node > 3CX Service Packs / Updates. This service pack fixes several issues and also adds new features such as support for Windows 8, Windows Server 2012, and an all new IP Whitelist for the Anti-Hacking module. See if the 3102 shows as registered both at 3CX and the Info tab of the 3102, and post any 3CX Activity Log error messages you get when attempting calls.3CX is pleased to announce the release of Service Pack 2, build 27588.780 for 3CX Phone System 11. Given that you have set the FXO Impedance to "Global", I assume you are not located in North America. I'm hoping that there re not other SIP devices behind the same router, that may cause "no-audio" issues. There are voice ports involved as well, but I would leave that until you can get call working both ways. The local router at the 3102 end may need the SIP port forwarded. The public IP that it is behind along with it's local port will have to be used in the 3CX trunk (10000) settings so that 3CX Can send call to the 3102. Line 1 VoIP Caller Dialplan can be left at the default of "none" You can set Register Expires to 1700 or 1800, it doesn't have to be as low as 300. I don't use Authorization ID, or the outbound proxy with a remotely registered 3102. It will probably be required to have STUN enabled. You should have assigned the 3102 a static IP. The fact that you are attempting to use this remotely to the server may present some issues (it is not officially supported).
That said, is there some reason you are using local port 45060 rather than something like 5061 or 5062? It should be (S0) that's a zero after the S. Well right off the bat, Dialplan 8 is incorrect.
0 kommentar(er)
