Just noticed that MD5 numbers for 3.11.4 and 3.11.7 don't match
those found in the separate respective .md5 files. I have checked
my md5 calculator on the stable 3.10.1 dist and .md5 files and they
agree. Also noted that 3.11.7 .md5 file is dated two days later than the
ISO. Since I'm having trou
s? Something like:
>
> wget -P /etc/yum.repos.d xx
> yum update --enablerepo=sipx-development
>
> Can I yum up to 11.5 or 6 ? is there any reason or way to target a specific
> 3.11.x unstable release - or is it just get the latest nightly build?
>
>> On Tue, 2008-09-
reason or way to target a specific
3.11.x unstable release - or is it just get the latest nightly build?
> On Tue, 2008-09-02 at 16:14 -0700, Charles McParland wrote:
>
>> any feeling for how stable 11.5 is at
>> present?
>>
>
> Not at all stable. That'
w.sipfoundry.org/pub/sipXecs/sipxecs-stable-fc.repo
then
yum update --enablerepo=sipx-development
This should work on the Centos from the 3.11 ISO, I assume.
Thanks again,
Chuck
>
>
> On Tue, Sep 2, 2008 at 6:11 PM, Charles McParland <[EMAIL PROTECTED]
> <mailto:[EMAIL PROTECTE
.11.5 system
> to log in if using a standard account.
>
> http://sipx-wiki.calivia.com/index.php/SipXbridge_Overview_and_Configuration
>
> Quoting Charles McParland <[EMAIL PROTECTED]>:
>
> > All,
> > I've seen several postings about this; but have not s
All,
I've seen several postings about this; but have not seen a response.
A pointer to a tutorial or thread (have searched the wiki) would be
greatly appreciated.
I have a 3.11 Centos Sipx install running. Phones register correctly
and dns srv records can find the system. Not trivial, but
New to this list, so please advise if this should be directed
elsewhere.
Have played with older SipX and Asterisk ISO installs and
would now like to set up a real production system. Have
burned and verified both the 3.10.1 and 3.10.2 Centos ISO
image several times (Nero and ISO Recorder) and all
