Wasn't a new 4.2.1 released yesterday? That is the one I used.
I do a bare-bones linux install before I install sipx. I have used the
same method for 4.0.4, 4.2.0, and 4.2.1. Something about 4.2.1 (8/17
version at least) seems to not work for me. Is there a package, utility,
or something similar sipx uses to determine the hostname to put it in
the config file?
If I'm the only one in the world this happens to, then sobeit. I can't
think of anything I'm doing that could cause this in anyway.
Again, mine is CentOS 5.5, 64 Bit, with a fresh install of the most
recent 4.2.1 version of Sipx.
I would be more than happy to install the latest 4.3.0 version if anyone
thinks it would be of any benefit.
On 8/18/2010 3:31 PM, Michael Picher wrote:
I just built a server on 4.2.1 last week and this all worked once the
Polycom Firmware device files were loaded up.
Mike
On Wed, Aug 18, 2010 at 4:06 PM, Matthew Kitchin (public/usenet)
<mkitchin.pub...@gmail.com <mailto:mkitchin.pub...@gmail.com>> wrote:
I'm far from an expert here, but I assume from looking at the file
that it is telling the phone where to retrieve the files from. If
that is the case, nothing along the lines of local, localhost2, or
anything like that is going to work. Obviously it has to be
something the phone can resolve and access.
If I'm completely wrong about how the phone processes that file,
then ignore above.
On 8/18/2010 3:00 PM, Tony Graziano wrote:
I believe something along the lines of needing localhost2 needed
to be in the hosts file with an update with ACD roles selected. I
think these two are somewhat related and "relevant".
On Wed, Aug 18, 2010 at 3:58 PM, Matthew Kitchin (public/usenet)
<mkitchin.pub...@gmail.com <mailto:mkitchin.pub...@gmail.com>> wrote:
On 8/18/2010 2:48 PM, Douglas Hubler wrote:
> I'm surprised you didn't error starting up sipxecs if host
name wasn't
> right. Is there a check that should be added?
This has to be incorrect in the original sipx install/rpm,
right? There
is nothing I did that should have caused this (that I can
think of). The
server was never named that. I did 2 installs from scratch and it
occurred on both. I'm assuming whatever generates that file
has a bug in
it and put local instead of the hostname. My setup is fine
now, but I
assume this is going to happen to anyone who uses the rpm
install (64
bit version at least, not sure if it occurs on 32 bit also)
on a fresh
install.
_______________________________________________
sipx-users mailing list
sipx-users@list.sipfoundry.org
<mailto:sipx-users@list.sipfoundry.org>
List Archive: http://list.sipfoundry.org/archive/sipx-users/
--
======================
Tony Graziano, Manager
Telephone: 434.984.8430
sip: tgrazi...@voice.myitdepartment.net
<mailto:tgrazi...@voice.myitdepartment.net>
Fax: 434.984.8431
Email: tgrazi...@myitdepartment.net
<mailto:tgrazi...@myitdepartment.net>
LAN/Telephony/Security and Control Systems Helpdesk:
Telephone: 434.984.8426
sip: helpd...@voice.myitdepartment.net
<mailto:helpd...@voice.myitdepartment.net>
Fax: 434.984.8427
Helpdesk Contract Customers:
http://www.myitdepartment.net/gethelp/
Why do mathematicians always confuse Halloween and Christmas?
Because 31 Oct = 25 Dec.
_______________________________________________
sipx-users mailing list
sipx-users@list.sipfoundry.org <mailto:sipx-users@list.sipfoundry.org>
List Archive: http://list.sipfoundry.org/archive/sipx-users/
--
There are 10 kinds of people in this world, those who understand
binary and those who don't.
mpic...@gmail.com <mailto:mpic...@gmail.com>
blog: http://www.sipxecs.info
call: sip:mpic...@sipxecs.info <mailto:sip%3ampic...@sipxecs.info>
_______________________________________________
sipx-users mailing list
sipx-users@list.sipfoundry.org
List Archive: http://list.sipfoundry.org/archive/sipx-users/