I did a clean OS/app install of the 4.6 build from last
night. Setup went fine but I get a 404 when I launch the
web interface (/sipxconfig/app Not Found). There are a slew
of Mongo-related errors in the sipxconfig.log (attached).
Do we know if there's a problem with this build?
sipxconfig.log
I enabled SIP capturing and left all the config at defaults
but I'm not seeing anything captured in the Homer interface.
Is there something else I need to do to turn it on?
To your question, though, when I do a tcpdump filtered on
port 5061 and call either 8-200 (dir to ext 200 vm) or 101
(vm
Oh, it was just restricting me to one file. Here's the
other openssl pcap...
ssl_handshake_test.pcap
Description: Binary data
___
sipx-users mailing list
sipx-users@list.sipfoundry.org
List Archive: http://list.sipfoundry.org/archive/sipx-users/
In response to Doug's question, I've tested with openssl
from the command line using the same certs and the TLS
negotiates fine. I also had it configured pretty much
identically in 4.4 and the Sipx cert was sent. Oh and I
tried with the self-signed cert as well and got the same
results.
As
a little more info...
I had been testing by calling the pilot number on the
voicemail dialplan (x101). I hadn't gotten as far as
turning voicemail from internal to external for a user.
When I did enable a user for Exchange, all calls rolled to
internal voicemail no matter the settings.
Sure. For the certs, I installed a StartSSL-issued
certificate for my Sipx and two intermediate CAs from
Microsoft. I edited the Voicemail dial plan with
Exchange Voicemail Server in the type field and the FQDN
of the Exchange Online gateway in the address. I added a SIP
Trunk gateway with the
No, the 8 is the default direct-to-voicemail prefix defined
no the vm dp. So it's odd when I get the internal voicemail
greeting when I timeout on a call to extension 200 but get
the TLS attempt when I dial 8200.
___
sipx-users mailing list
I thought I'd put some effort into getting 4.6 to work with
Exchange Online UM which requires TLS transport with a
non-self-signed SSL certificate. Right out of the gate, the
TLS handshake fails when Exchange requests Sipx's client
certificate and Sipx returns a handshake message with the
cert
with Microsoft TAC). My email should be publicly visible.
John Lightfoot
___
sipx-users mailing list
sipx-users@list.sipfoundry.org
List Archive: http://list.sipfoundry.org/archive/sipx-users/
