Search results for query: *

It ended up being that the ports were not open on the firewall. Everything is working as designed now. Thanks for the help,

derfloh: Thanks for the tip. I tried that yesterday, as per dsm600rr, and did not see any activity in traceSBC. My requests were not even reaching the SBC. That's what led me to believe that it's a port issue on the customer firewall. I'm waiting for them to confirm open ports. Thanks again.

Hmmm, I see nothing when trying to navigate to those files which now leads me to believe that this is probably a port issue. I'll have to reach out to their IT and confirm that the ports I requested are actually open. Thanks.

Should I be able to browse to those files externally? HTTPS://<FQDN>/46xxsettings.txt and the other files I can only browse to while local. I’m assuming that’s why it will not register when remote without a local HTTP server serving those files. It looks like my reverse proxy are setup the...

I have a fully configured SBC with IPO SE 11.0.4. Workplace/Equinox registers fine through the SBC using TLS with the correct certs installed. I can also get my J phones to register remotely through the SBC if I use a local HTTP server for the 46xxsettings.txt file and WebRootCA.pem files. My...

Here's the release notes for the patch. The patch may fix the @ipaddress being displayed. It's not very specific. Core Critical Patch to fix: IPOFFICE-104954 - Multiple Call log issue on IP Office 9.1.5 Other fixes requested/incorporated for which there isn't currently a JIRA: N/A CP type...

Sorry. Only used PRIs at this customer. Don't have any info about the SIP trunks.

I had the same problem after upgrading to 9.1.5. If you have IPOSS you can open a SR with Avaya and they will provide a patch that fixes the call log issues. 9.1.5.6 is what they provide. I can confirm that it fixes the issues with the call log for hunt group calls.

Was there ever a resolution to this problem? I'm having the exact same issue, except I'm using IPO Server Edition with the latest release of Voicemail Pro version 9.0.2.0 build 41. We just upgraded from SP1 and are still having the issue. It's on random messages. Could be internal, external...