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
No reason that I know of to move up. New phones being shipped come with
firmware 3.3 or later and there is a manula downgrade procedure. You can
still register the phones, etc., but they boot up with an error message on
the screen of the phone (at least the ones I had seen) and thought perhaps
it w
Ah -- the Send Profiles to the server seems to have fixed things up. I saw
that part of the process in the job status screen was to regenerate IMDB. I
can also create other new users and things work as expected now.
I did do a yum update prior to configuring but not prior to the initial setup
Log shows
"2012-09-04T20:53:44.422175Z":261:AUTH:ERR:sipxt.vt.messiah.edu:SipRegistrarServer:7f78e2522700:SipRegistrar:"Unable
to get credentials for '1...@vt.messiah.edu', realm='vt.messiah.edu',
user='1910/0004f21b526d'"
Questions:
1.) Did you run
yum update
after installing
Are you running above 3.2.7 firmware on the phone?
--
~~
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/7a4
Ask about our Internet Fax s
I'm thinking I am missing something stupid here but didn't figure it out quite
yet. I have been unsuccessful at getting a Polycom 335 to register with a 4.6
test server. Attached is an interesting snippet from sipregistrar.log that
sounds like some kind of database lookup problem perhaps. Thi
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
same here, got it
On Wed, Sep 5, 2012 at 11:08 AM, George Niculae wrote:
> Getting attachs
>
> On Wed, Sep 5, 2012 at 11:04 AM, Douglas Hubler wrote:
> > testing attachments
> >
> > On Tue, Sep 4, 2012 at 10:05 PM, Todd Hodgen
> wrote:
> >> Are attachments going through?
> >>
> >> I see my res
Getting attachs
On Wed, Sep 5, 2012 at 11:04 AM, Douglas Hubler wrote:
> testing attachments
>
> On Tue, Sep 4, 2012 at 10:05 PM, Todd Hodgen wrote:
>> Are attachments going through?
>>
>> I see my response to your email went through. However, one that I had sent
>> that has a small attachment
testing attachments
On Tue, Sep 4, 2012 at 10:05 PM, Todd Hodgen wrote:
> Are attachments going through?
>
> I see my response to your email went through. However, one that I had sent
> that has a small attachment hasn't yet. It was sent prior to my response to
> your test message.
>
> -Ori
19 matches
Mail list logo
