On 1/18/2010 12:14 PM, Scott Lawrence wrote:
> On Mon, 2010-01-18 at 11:31 -0600, [email protected] wrote:
>
>> On 1/18/2010 11:13 AM, Scott Lawrence wrote:
>>
>>> Frankly, I wouldn't invest much in getting externally generated keys
>>> working in a 4.0 system. There turn out to be many potential pitfalls,
>>> and it's clear that feature really wasn't ready for prime time. We're
>>> investing a fair amount of effort in this for 4.2...
>>>
>>>
>> Is it just the setup process that wasn't ready for prime time, or
>> something else? Assuming the import worked, is it safe to assume there
>> are no more pitfalls? I just moved to a internal company generated cert
>> using an internal Microsoft licensing server. It was relatively painless
>> once I figured out how to tell Microsoft is was an Apache request as
>> opposed to something Microsoft. There aren't any long term issues I
>> should expect are there? Once I realized my users would need the web
>> interface for forwarding, I needed to get rid of those ssl cert warning
>> screens. They used to be no big deal in older versions of IE, but
>> current versions are sure to generate a call to our help desk no matter
>> how much we explain the messages are ok.
>>
> If things are working, then you're probably fine. The problems are sort
> of all-or-nothing.
>
>
Mine appeared to work, but then I ran into PIN change problems. It looks
like it was because the sipx server couldn't find my internal windows
CA. Is there a single place in sipx where I would need to add the CA
certificate for my internal server, or is this a 'wait for 4.2' issue?
Some of the documentation I found seems a little dated.
_______________________________________________
sipx-users mailing list [email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-users
Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users
sipXecs IP PBX -- http://www.sipfoundry.org/
