Am 26.05.2011 01:48, schrieb Joegen Baclor:
I think this jira issue is a duplicate. NAT compensation is handled
by TLS now. Can you confirm that it isn't using bria or anything else
that could register? I tried using my Polycom just now and I am
getting the same result. Polycom ignores the
Content-Type: text/plain;
charset="utf-8"
Content-Transfer-Encoding: 8bit
Organization: SipXecs Forum
In-Reply-To:
X-FUDforum: 08063afcdd00a6e76393c5b9527381e8 <60203>
Message-ID:
Also, we did have the SRV records in place. Initially, we
tried the new style SRV record ("_sips._tcp.carrieri
I think this jira issue is a duplicate. NAT compensation is handled by
TLS now. Can you confirm that it isn't using bria or anything else that
could register? I tried using my Polycom just now and I am getting the
same result. Polycom ignores the custom cert. Is there anything that
changed
you still need to manually e sure the sip tls srv record is made at the dns
server and onboard to sipx.
this is more problematic in an ha environment.
I don't think until the JIRA is closed it makes sense to try tls in a remote
user environment.
On May 25, 2011 6:46 PM, "andrewpitman" wrote:
>
>
Content-Type: text/plain;
charset="utf-8"
Content-Transfer-Encoding: 8bit
Organization: SipXecs Forum
In-Reply-To: <4d5d0a33.1040...@ezuce.com>
X-FUDforum: 08063afcdd00a6e76393c5b9527381e8 <60175>
Message-ID:
Joegen Baclor wrote on Thu, 17 February 2011 06:44
> You need to make sure that the
I know we are running 4.4 in EZuce currently. Can an EZucer try to
replicate this with the existing Polycoms with a recent firmware? Was
able to test this with an SP 335.
On Thursday, 24 February, 2011 05:21 PM, Lars Schiller wrote:
> Am 17.02.2011 12:44, schrieb Joegen Baclor:
>> You need to
Am 17.02.2011 12:44, schrieb Joegen Baclor:
> You need to make sure that the custom CA and not the built-in polycom CA
> is the one sent by the Polycom phone. Instructions how to activate the
> custom cert is discussed in the wiki just in case you haven't seen it yet.
>
> http://wiki.sipfoundry.or
You need to make sure that the custom CA and not the built-in polycom CA
is the one sent by the Polycom phone. Instructions how to activate the
custom cert is discussed in the wiki just in case you haven't seen it yet.
http://wiki.sipfoundry.org/display/sipXecs/Polycom+Phone+using+sipXecs+TLS+t
Hi
I'm having issues getting the TLS to work with Polycom phones. I've exported
the CA certificate from SipX and installed it on the phones. The phone display
says that the
certificate is successfully accepted and installed. However, looking in
wireshark as the TLS handshake is happening, I sti
