That was indeed the problem, didn't have a wildcard so quickly bought one for
the sipx server and it went in fine.
Thanks again.
On Sun, 2 May 2010 19:41:57 -0500, m...@grounded.net wrote:
> Could someone post how they went about installing godaddy ssl certs on
> their 4.2 server.
>
> Trying j
I guess I don't have a wildcard cert. Off to buy another one for now.
On Sun, 2 May 2010 20:44:14 -0500, m...@grounded.net wrote:
> Ok, thanks again, that worked just fine this time around.
>
> Mike
>
>
> On Sun, 02 May 2010 20:04:23 -0500, Josh Patten wrote:
>> No, you don't have to worry abou
A few weeks ago, I built a CentOS 5.4 64 bit version of sipXecs 4.0.4
on a VMware server.
I configured this server to match my existing sipXecs installation and
moved the VMware image to production.
This week, I installed the sipXecs 4.2 CentOS 5.2 32 bit ISO on my
original standalone server (2
Maybe something is still left over. Checking by connecting gives me,
sx.mydomain.com:8443 uses an invalid security certificate.
The certificate is only valid for the following names:
www.mydomain.com , mydomain.com
(Error code: ssl_error_bad_cert_domain)
Yet, should work as the domain is co
Ok, thanks again, that worked just fine this time around.
Mike
On Sun, 02 May 2010 20:04:23 -0500, Josh Patten wrote:
> No, you don't have to worry about it. All you have to do is upload the
>
> .key and .crt files and sipXconfig will restart with the new certificate
> in place.
>
> On 05/02/2
No, you don't have to worry about it. All you have to do is upload the
.key and .crt files and sipXconfig will restart with the new certificate
in place.
On 05/02/2010 08:03 PM, m...@grounded.net wrote:
>> If you have the key and cert then you don't need to worry about the CSR.
>> That's the
> If you have the key and cert then you don't need to worry about the CSR.
> That's the beauty of having both.
>
> The CSR is the certificate signing request and that generates a private key
> for you. If you already have the private key then you don't need to do a
> CSR.
>
> http://en.wikipedia.
If you have the key and cert then you don't need to worry about the CSR.
That's the beauty of having both.
The CSR is the certificate signing request and that generates a private
key for you. If you already have the private key then you don't need to
do a CSR.
http://en.wikipedia.org/wiki/Ce
Yes, I have both, it comes in a zip file.
Problem is, I might have a slightly different CSR and can't find the note on
when I created it.
Can I just upload the CSR file in order to generate that first, then my godaddy
files should import.
Mike
On Sun, 02 May 2010 19:41:08 -0500, Josh Patten wr
With a wildcard cert you have to have the .key that came with the
certificate. Other than that it should work fine.
On 05/02/2010 06:52 PM, m...@grounded.net wrote:
> I have a cert which is www.domain.com and *.domain.com which is being used on
> a web server which has the same domain name as th
Is there any way in 4.2 of preventing the web structure overwrite upon
reboot/restart?
___
sipx-users mailing list sipx-users@list.sipfoundry.org
List Archive: http://list.sipfoundry.org/archive/sipx-users
Unsubscribe: http://list.sipfoundry.org/mailma
Thanks, I'll dig up more info on it. Wanted to check as I saw several threads
on that.
Mike
On Sun, 2 May 2010 19:54:43 -0400, Picher, Michael wrote:
> Yes for the wildcard cert, and yes it is easier (from what I
>
> understand).
>
>> -Original Message-
>> From: sipx-users-boun...@lis
Yes for the wildcard cert, and yes it is easier (from what I
understand).
> -Original Message-
> From: sipx-users-boun...@list.sipfoundry.org [mailto:sipx-users-
> boun...@list.sipfoundry.org] On Behalf Of m...@grounded.net
> Sent: Sunday, May 02, 2010 7:53 PM
> To: sipx-users
> Subject: [
I have a cert which is www.domain.com and *.domain.com which is being used on a
web server which has the same domain name as the sipx server does. Could I
install this cert on sipx safely or should I purchase another cert? And, in
4.2, are ssl certs easier to install?
Thanks.
Mike
__
rpm -qa | grep 'sipx*'
On Sun, May 2, 2010 at 4:45 PM, Tony Graziano
wrote:
> I've seen issues with ftp not uninstalling the previous version
>
> If you don't have it
>
> grep for "sipx" instead
>
> Install it with
>
> yum install sipxconfig-ftp
>
>
>
> Tony Grazia
I've seen issues with ftp not uninstalling the previous version
If you don't have it
grep for "sipx" instead
Install it with
yum install sipxconfig-ftp
Tony Graziano, Manager
Telephone: 434.984.8430
Fax: 434.984.8431
Email: tgrazi...@myitdepartment.net
LAN/Tele
Dear Mr. Graziano,
Thank you for the heads up. For whatever reason, when I check my
list of installed packages I only see the 4.2 version. I searched for it
two different ways:
Search string = sipx
sipx-freeswitch
sipx-freeswitch-codec-passthru
Be sure your ipsec filter at each end is set to alow both tcp and udp
traffic too.
Tony Graziano, Manager
Telephone: 434.984.8430
Fax: 434.984.8431
Email: tgrazi...@myitdepartment.net
LAN/Telephony/Security and Control Systems Helpdesk:
Telephone: 434.984.8426
Fax: 43
I tend to think of the one contact advantage of not using the
subdomain... that way my email, sip phone number and IM can all be the
same address...
Mike
> -Original Message-
> From: sipx-users-boun...@list.sipfoundry.org [mailto:sipx-users-
> boun...@list.sipfoundry.org] On Behalf Of Na
Thanks for the reply - that all makes sense. Hopefully I'll make up my mind
soon...
From: Tony Graziano [mailto:tgrazi...@myitdepartment.net]
Sent: Sunday, May 02, 2010 1:39 PM
To: Nathaniel Watkins
Cc: sipx-users@list.sipfoundry.org
Subject: Re: Routable domain setup - recommendation
The only
The only reason I stated to use a subdomain was as follows:
1. I didn't want to change to Openfire for my already "in-place" IM system.
I prefer google for IM for too many personal reasons, and Pidgin or Spark
and Openfire don;t give me the flexibility without additional resources and
setup to mak
I'm getting ready to re-install 4.2 and change my SIP domain so it it publicly
addressable (primarily for xmpp server federation). Tony had recommended
putting this on a sub-domain (ie sipx.voice.domainname.com).
Is there a compelling reason to not have it on the main domain? The only
reason
To clarify this, if all your sip traffic is happening over vpn's sipx won't
care to know its behind nat. Only when its behind nat and handling siptrunks
via sipxbridhe as an sbc or handling remote users via the internet (without
vpn).
Tony Graziano, Manager
Telephone: 4
If you are not using sipxbridge, server behind nat is not needed.
What kind of phone is it? Bootrom and firmware is important too.
A siptrace of that call will be helpful.
Tony Graziano, Manager
Telephone: 434.984.8430
Fax: 434.984.8431
Email: tgrazi...@myitdepartme
They are registered using the private address at the far end
sip:3...@domain.com
sip:3...@domain.com
They are also using a DNS locl to them (the far end router/ipsec device)
My server settings are checked "Server is behind nat" (because that's needed
because I'm behind a pfsense firew
On Sun, 2010-05-02 at 07:03 -0400, Justin Menga wrote:
> Just thought I'd give an update as I ran into this issue yet
> again and it stumped me for a little bit.
>
> The fix is simple - in my case my voice gateway was sending
> INVITE with the To header in the format of
> @ - by default,
> SIPXec
Look at your registrations..
Do they show registered at the ipsec address or the public address with the
private contact address the phone is using? or are they registered at the
private address at the far end (should be).
They should also be set to use a DNS (local to them or the sipx dns server)
I only have "Server Behind NAT" checked and they are using the remote site
VPN's DNS... I can make calls out with no issues I just cant receive calls...
would that still be DNS?
-Original Message-
From: "Tony Graziano" [tgrazi...@myitdepartment.net]
Date: 05/02/2010 07:45 AM
To: "Jerm
Please ensure "Internet Calling" is disabled. The VPN phones also need to
resolve your SIP server as an internal address. What DNS are they using?
On Sun, May 2, 2010 at 7:04 AM, Jermaine Pinder <
jpin...@pinderconsulting.com> wrote:
> (Basically I can't receive calls on my remote VPN phones, but
You may have certain type of call sequences that might give you problems
using IP on the gateway. You should determine how to properly configure your
gateway to use the sipdomain/srv records instead of an IP address.
On Sun, May 2, 2010 at 7:03 AM, Justin Menga wrote:
>
> Content-Type: text/plai
(Basically I can't receive calls on my remote VPN phones, but I can call out
and I can call any extension)
IPSec VPN and Sipx 4.2
Greetings,
I have a few sites that has an IPSec VPN setup between them. I also have a few
phones at the remote
VPN locations that registers OK and can make calls ou
Content-Type: text/plain;
charset="utf-8"
Content-Transfer-Encoding: 8bit
Organization: SipXecs Forum
In-Reply-To: <9cc99a440912291623l2b34c1fcr63abc8e30312e...@mail.gmail.com>
X-FUDforum: 08063afcdd00a6e76393c5b9527381e8 <45944>
Message-ID:
Just thought I'd give an update as I ran into this
IPSec VPN and Sipx 4.2
Greetings,
I have a few sites that has an IPSec VPN setup between them. I also have a few
phones at the remote
VPN locations that registers OK and can make calls out but I can't receive a
call in. I get the message the
user is not available but the phone is register with
33 matches
Mail list logo
