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/
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 acc
Can you turn on "SIP Capture" feature and compare the ladder diagrams
of each call in homer?
Diagnostics/SIP Capture/SIP Capture Web Interface
On Wed, Sep 5, 2012 at 2:09 PM, John Lightfoot wrote:
>
>
> No, the 8 is the default direct-to-voicemail prefix defined
> no the vm dp. So it's odd w
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
sipx-users@
Because there is no active dial plan entry for 8+ pointing to the exchange
system?
--
~~
Tony Graziano, Manager
Telephone: 434.984.8430
sip: tgrazi...@voice.myitdepartment.net
Fax: 434.465.6833
~~
Linked-In Profile:
http://www.linkedin.com/pub/tony-graziano/14/4a6/
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
On Wed, Sep 5, 2012 at 6:36 PM, John Lightfoot wrote:
>
>
> 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
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. Perhap
oops. I sent that for 4.4, for 4.6 refer to what george sent
On Wed, Sep 5, 2012 at 11:57 AM, George Niculae wrote:
> On Wed, Sep 5, 2012 at 2:54 PM, John Lightfoot wrote:
> >
> >
> > In response to Doug's question, I've tested with openssl
> > from the command line using the same certs and the
system>logging levels>advanced>trunking (which is sipxbridge)
set to debug and restart services as prompted
On Wed, Sep 5, 2012 at 7:54 AM, John Lightfoot wrote:
>
>
> In response to Doug's question, I've tested with openssl
> from the command line using the same certs and the TLS
> negotiates
On Wed, Sep 5, 2012 at 2:54 PM, John Lightfoot wrote:
>
>
> 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
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 for
On Wed, Sep 5, 2012 at 5:55 PM, Douglas Hubler wrote:
> On Tue, Sep 4, 2012 at 3:26 PM, John Lightfoot wrote:
>>
>>
>> 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,
On Tue, Sep 4, 2012 at 3:26 PM, John Lightfoot wrote:
>
>
> 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
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 e
15 matches
Mail list logo
