New trixbox appliance
Submitted by wrc1045 on Wed, 04/23/2008 - 4:06am.
Hello we have a new trixbox/call center install. This is our first install and the hardware does not seem plug and play as they state. First the sales person said the 4 port built in switch was already supposed to be configured to dhcp and should do the phones that way. Can I ask if that is now possible or how do you implement this? Also is dhcp enabled on the WAN port of the appliance? I find now real good info on the documents. The install manual gives relatively simple info but no real step by step instuctions on them. Maybe I am looking in the wrong place. Please help provide some insight to these issues. Thanks for your time.
If you are using trixbox Pro
Thu, 04/24/2008 - 2:15pm
If you are using trixbox Pro you will get a prompt during the activation process asking you "Do you want to use the secondary interface as a phone-provisioning network" (or something along those lines). This will enable DHCP on the 4-port router interface.
DHCP is not a configurable option for the primary interface.
You can setup DHCP on the
Fri, 04/25/2008 - 6:01am
You can setup DHCP on the system fairly easily. I will assume the second network card is configured for 192.168.25.1 which is the default configuration, then follow these steps:
1. nano /etc/dhcpd.conf
2. Insert these lines:
ddns-update-style interim;
ignore client-updates;
subnet 192.168.25.0 netmask 255.255.255.0 {
option routers 192.168.5.1;
option subnet-mask 255.255.255.0;
option nis-domain "tdp.local";
option domain-name "tdp.local";
option domain-name-servers 192.168.25.1;
option time-offset -28800;
option ntp-servers 192.168.25.1;
option tftp-server-name "192.168.25.1";
range dynamic-bootp 192.168.25.10 192.168.25.254;
default-lease-time 43200;
max-lease-time 86400;
}
ddns-update-style none;
class "phone" {
match substring(hardware,1,3);
}
# Polycom
subclass "phone" 00:04:f2
{
authoritative;
option tftp-server-name "tftp://192.168.25.1";
}
subclass "phone" 00:90:7a { # Polycom
option tftp-server-name "tftp://192.168.25.1";
}
subclass "phone" 00:e0:75 { # Polycom SoundStation IP
option tftp-server-name "tftp://192.168.25.1";
}
subclass "phone" 00:08:5d { # Aastra
option tftp-server-name "192.168.25.1";
}
subclass "phone" 00:10:bc { # Aastra Telecom
option tftp-server-name "192.168.25.1";
}
3. Save the file
4. chkconfig dhcpd on
5. service dhcpd start
Well, it certainly wont work
Fri, 04/25/2008 - 6:12am
Well, it certainly wont work if the network card isn't working. You will need to call whoever you bought it from in order to help you through getting the network up. You should then find someone with a basic linux knowledge to provide support service for you for things like this. You can also buy support from us and we will get in and fix it all up.
If you disable the DHCP
Fri, 04/25/2008 - 6:33am
If you disable the DHCP server on your existing network then you could use the same basic information above to enable the DHCP server on the working network port. Again, you will need someone with a basic understanding of Linux to do this for you if you can't follow the instructions that were given.
I had the same problem with
Sun, 04/27/2008 - 1:22pm
I had the same problem with my appliance. I've re-installed PRO multiple times with no resolution to that. I eventually just went to every phone and made them have static IP's. I did not see anywhere during installation asking me if I wanted to make the second card do anything. I've had 2 appliances as of today (during the last 60 days) because I thought the card was bad. The only time that has ever worked was when the 1st system came and had CE installed.
Pro boxes
Sun, 04/27/2008 - 4:56pm
I think there is a problem with the original install from voipsupply...... I had several of my programmers look at it and that is what they concluded? or maybe a buggie program? the tech manual and the way they explain things really needs updated. appearently we received a ce manual with our pro install on the trixbox. do the os come already installed to voipsupply? or do they install them st their facilities? at least put the right manual and login/password info with the correct box. pro boxes only allow you to config using cp.trixbox.com. if we would have know that in advance we would have not opted for this configuration/software. what happens if trixbox/fonality go out of business or their server goes down permanently. our client has no solution? at a minimum we should have an option at setup to do local configs.
I also had this same issue
Mon, 04/28/2008 - 7:40am
I also had this same issue on one of our appliances. Although after talking with one of the support guys we found a resolution for this issue.
First I did not get a prompt asking to configure dhcp for the second interface. After install I did an ifconfig and noticed that I did not have a eth1 showing up. If you type in ifconfig -a you will see that eth1 is actually there. Also you can type in lspci and you should see 2 realtek Ethernet network cards are recognized.
I then browesed to the /etc/sysconfig/network-scripts directory and noticed that I didnt have an ifcfg-eth1 file.
So what you need to do is manually create this ifcfg-eth1 file and add your ip address info. I use nano ifcfg-eth1 and then enter:
DEVICE=eth1
ONBOOT=yes
IPADDR=192.168.25.1
NETMASK=255.255.255.0
BOOTPROTO=static
NETWORK=192.168.25.0
BROADCAST=192.168.25.255
Now save the file. Then follow the instructions provided by Kerry to setup DHCP and now everything should be working.
Also if you still do not have any info on the LCD, just a blank cursor flashing. I found out that this is a driver issue. I did not get all the information on what support did to fix this issue. But it has to do with the lcd4linux driver not starting when you boot up. This driver sits in /etc/rc*.d
I would like to know for future reference how this was resolved.
I had the same problem and
Tue, 05/06/2008 - 5:23pm
I had the same problem and also purchased from VoIPSupply.com. However, no one was able to help me like in this thread. I ended up just giving ALL of my phones static IP's which was a huge hassle but it worked. I also have my phones/computers sharing a network in which I did not want to happen... but had no choice because no one could give me an answer. In fact, VoIPSupply actually shipped me another unit with the same "problem". I did multiple fresh installs and it never once gave me the option to initiate the DHCP. So that's where I'm currently at. I'm not very good with Linux and think that this should be done by Trixbox themselves considering I purchased an applicance for the 'user friendly compatible hardware' and still can't use it properly because of their software and their supplier.
So if you're listening Trixbox, take the advice given on this forum and correct my internal LAN issue!
Jeff you could always pay
Wed, 05/07/2008 - 11:39am
Jeff you could always pay and have your local reseller send a tech out and get you up and running. If your in the Dallas area, I would be glad to come by and get that working for you.
I know it sucks that you buy a box that doesnt come up and work the way you expect. If you have support, TB support should be able to get this working. Fonality doesnt make these forums priority because they do not make any money from them although they do help as much as they can here.
If you try to learn just a little linux, you should be able to get your box working correctly with all the info in this thread.
ddavidson -
It's working..
Wed, 05/07/2008 - 12:21pm
ddavidson -
It's working.. and working fine.. My only point was that I have an extra server (3 times as powerful also) I could have thrown this software on and saved my $1750 if I wanted to troubleshoot and figure out things on my own. I even pay for their Call Center Edition but still get no support with that either. I'm slowly working on my Linux. I can do little things but it's a production server and even though I own the company, I'd prefer not to make an error and take the system offline for any period of time.
You've helped me on a lot of my issues and I do appreciate that and I use the forum for as much help, advice, and ideas as I possibly have time to read. Again, it just sucks when you pay almost 2k for a free open source system just so you can have "100% compatible system guaranteed to work" and you still have to troubleshoot problems such as these that should be working from jump.
I wish I had more time to learn more Linux and read the forum more but as stated before I own my company and we are a really busy group of folks and that's just the reason that I purchased the appliance rather than putting it on one of my servers.
P.S. I'm in Atlanta.
Shorelet is a turd.
Wed, 05/07/2008 - 12:39pm
Shoretel is a turd. Proprietary endpoints using MGCP, must use "Shoretel Certified" SIP providers and buy a SIP license, minimal 3rd party endpoint support and no tech support on 3rd party endpoints.
This list goes on and on.
I agree with the other posters. Get some help from a local reseller or buy a support block from Fonality. Buying the server insures that the NIC's and other hardware will be supported by the software, in your case it sounds like money well spent.
Good luck.
Scott
Very bad advice. "buying the
Wed, 05/07/2008 - 1:35pm
Very bad advice. "buying the server insures that the NICS's and other hardware will be supported by the software"... that makes me laugh... why does it matter if the hardware is supported by the software if it doesn't work?!?
I don't care about SIP licences... I use PRI... I wouldn't want 3rd party endpoints because their phones are fine...
The NIC most likely works
Wed, 05/07/2008 - 2:03pm
The NIC most likely works fine, it just needs a little configuration done to make it work the way you want. I had the exact same issue with one of my appliances. And I agree, it should have recognized the NIC and asked for DHCP on bootup, but for whatever reason there was a bug and this did not happen.
If you can log into root, type in: lspci
if you see something similar to this, then your NIC card is being recognized by the Server(You should see 2 Ethernet controllers listed).
02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8101E PCI Express Fast Ethernet controller (rev 01)
03:01.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10)
Quote:
Very bad advice.
No,
Wed, 05/07/2008 - 3:20pm
Quote:
Very bad advice.
No, not bad advice. If you want a monolithic proprietary system that forces you to do everything the Shoretel way then by all means go out an buy it.
Take a look at a support contract for Shoretel and then tell me what you think.
From my perspective you could not figure out how to do this yourself, you did not want to pay somebody who knows how to do to take care of the problem and then you complain.
From my perspective you want something for nothing. You either pay somebody to do it or you learn it yourself.
Scott
Something for nothing? If i
Wed, 05/07/2008 - 4:14pm
Something for nothing? If i wanted something for nothing I would have put the FREE software on my existing server and wouldn't be paying monthly for the Call Center Edition...
$1750 - Prebuilt Trixbox appliance (fancy green case)
$ 230 - 15 users on ACD (monthly)
= Something for nothing...
That's the best math i've seen in years!
P.S. The only problem I am complaining about is the problem that a lot of other users are complaining about... buying a prebuilt system that comes with a card directly from the vendor and it doesn't work like it should. If that's wanting something for nothing, then half of this forum that requests Trixbox support do something must feel the same way.
Until this thread, no one could figure out my problem, not even YOU or Kerry G. I've posted numerous threads requesting the same help and the only person that fixed the problem was ddavidson in this thread. Therefore, I was trying to learn how to fix it and i refuse to pay some company a penny to come look at my system if the creators could not correct it.
2nd, if i were to buy a proprietary system and something of their pre-integrated hardware didn't work right with their software, they would give free support or replace the product with a working unit (i've talked to Cisco and Shoretel using this example)... It's not like this was a system I bought 12 months ago, it was a system i bought 6 weeks ago and have been posting the question since day one.
I am always interested in
Wed, 05/07/2008 - 5:08pm
I am always interested in opinions/motivations, I appreciate the candid reply.
Quote:
not even YOU or Kerry G.
I support CE so if I accidentally posted to another of your threads on Pro I apologize.
Quote:
Therefore, I was trying to learn how to fix it and i refuse to pay some company a penny to come look at my system if the creators could not correct it.
This is the point I am trying to work through with you and why I replied to this thread. You don't see the value in paying for my time (an example) nor Fonality support by the hour.
Your configuration is one that requires a bit of customization. If I purchase a $50,000 Cisco ASA and can't get my VPN talking to network XYZ then I know that security support from Cisco is $250/hr. and up.
Networking services in Linux is documented ad nauseum on the Internet. There is nothing special or proprietary about the network stack.
Ok, so I get that the value proposition on the appliance doesn't do anything for you, I understand. The real value is in the delta between what you spent and what closed system would cost. You mentioned the Shoretel. I know both Shortel resellers in my market and they do not work for free.
I have cleaned up many a mess after a principal in a business decides they are going to maintain their own phone system. I don't care how smart you are if you don't do it every day, immersed in the process of telecom you can't be proficient.
Quote:
(i've talked to Cisco and Shoretel using this example)... It's not like this was a system I bought 12 months ago, it was a system i bought 6 weeks ago and have been posting the question since day one.
This is not accurate, in the Cisco example if you bought a Smartnet contract they would offer limited assistance with configuration. Since you can't purchase direct from Cisco you would be buying from a reseller. Resellers make 90% of their profit on services, they would not do the config for free, certainly not setting up DHCP on a dual homed Call Manger.
The key to all this is the perception of value for professional services. Information is a valuable commodity, communicating that value is a daily struggle.
Scott
I get all of that. I truly
Wed, 05/07/2008 - 9:17pm
I get all of that. I truly do. In fact, I am in the telecommunication industry but this is our first IP based system. We mainly do data and voice with Nortel Systems and we are in the beginning stages of working with IP based systems. Mainly the only reason we purchased the Trixbox for our office was for the branding setting so we can begin reselling and wanted to begin trialing in our office prior to bringing to market so we can overcome these issues.
I do not agree with your Cisco ASA system analogy. If you were to buy that system and the port that your vpn connected to did not work, Cisco, or your retailer, would replace that part with a working part. You can not deny that.
It, in my eyes, should be automatically corrected if it is a software issue on a factory system. It's not like I added this card after purchasing the system and now I'm asking for assistance. All i'm asking is that the system that I purchased function properly. You keep leaning towards me paying for support on a system that comes "preconfigured" to work with the parts that was sold with the system. My configuration shouldn't require "a bit of customization". It's no different that what is offered with their system. That's what I'm trying to get through to you. I bought this system appliance, their recommended endpoints, and tried to put it on a segmented network which is also recommended. I'm not changing any settings or asking for anything that is not "sold" to me while purchasing the system.
Again, I would completely agree with you if I were adding additional cards to this system and asking for free assistance. However, I'm only asking for what was sold to me to work properly with the software. If Trixbox didn't want to use these LAN cards or support them if they don't work properly from the get-go, they shouldn't sell them with THEIR appliance but rather offer them as an add-on that can be configured for an additional fee.
Jeff,
Wed, 05/07/2008 - 10:34pm
Jeff,
Thanks for the thoughtful reply.
I just reread the thread to try and get my arms around it.
I was speaking in generalities with regard to paying for support I think you get my drift.
I am a bit out of my element because I do not know anything about Pro, we are a small regional ITSP and use CE as a customer premise solution. The hybid/hosting thing blows my revenue model.
What is surprising to me is that something that is scripted and so easy to do in CE could be complicated in Pro. DHCP listens on all active interfaces by default. I never pay much attention to what the setup script does because it is an intuitive process for me to address the interfaces, set up the routing and then edit dhcpdc.conf.
After revisiting all of this I understand your position.
All I can speak to is what I have seen around here and that is Kerry & company respond to issues quite quickly, I remember something that happened with them and they opened all the stock and did whatever it took to make it right (it was awhile ago hence the sketcy details).
The principal is that Pro or CE the value is so clear to me that the a little work does not matter.
Truth be told I only got involved in this thread because I happened to notice Shoretel's name. I compete against them all the time so I have a fairly good "why Shoretel sucks" story.
With regard to Shoretel and the ASA analogy. You would have to work very hard to buy either of these products without some professional services. Resellers can't risk their reputation with end users botching the install to sell boxes for a few points above cost. The manufacturers are not set up for any end user support, period.
Anyway, did you try ddavidson's instructions?
Regards.....Scott
Okay so here is the deal on
Thu, 05/08/2008 - 8:57am
Okay so here is the deal on "How DHCPD is supposed to work with trixbox Pro".
First, we NEVER enable dhcpd on the primary interface, why you might ask? This comes down to statistics. Before the release of trixbox Pro the question was asked of me. I responded with a bit of science, being the man behind the installation of a few thousand PBXtra systems information in front of me was vast and startling: Only a dozen out of THOUSANDS of installations wanted to use the PBXtra for DHCP services.
Having two DHCP servers on a network is a very, very bad thing. Hence we went for the obvious solution and omitted from enabling dhcpd on eth0 on all trixbox Pro installations (this includes trixbox). This however does not include special replies used for auto provisioning of most Aastra and some Polycom phones (success depends on firmware versions).
So, during the boot process you are asked "Do you want to use the secondary interface as a phone provisioning network?". This will enable dhcpd on eth1, with Option 66 and a NAT'd interface.
Since all appliances come 'un activated' from Fonality - this boot option happens at either the distributor (ie:VoIP Supply) OR at the end customer when they type 'activate' and enters a Server ID - wrc, did you perform this action?.
It is clear to me that this option was not selected in the boot process in this case. The semantics of solving the problem is a trivial Linux engineering exercise of setting up dhcpd.conf and starting dhcpd on boot.
Now, wrc - the problem here is that if I swooped in and 'fixed' dhcpd on your system I would risk bringing down your entire network. This sort of setup is less about the Linux setup and more about knowing exactly how the network is supposed to be setup to avoid very bad things. Ddavidson's instructions look good - those are along the lines of things that get done when you select the "use secondary interface as a phone provisioning network" on boot. Did they work out for you?
I hope this clears things up for everyone.
Thanks,
Mike
That clears up everything
Thu, 05/08/2008 - 9:29am
That clears up everything just as it has throughout this thread. I get that it's not autoenabled because everyone has a different approach to their installs. However, the problem that WRC and I both had was during the install, it DID NOT ask to set up the 2nd card. In fact, as per Kerry's request, I reinstalled this software about 8 times in 2 days. Never had that question asked of me. 2nd, I then called VoIPSupply and demanded a new appliance with Pro preinstalled before leaving their warehouse. They complied and I received the box the next day. I was excited because I thought that this problem would be fixed... however to my dismay, I still did not get asked that question about the 2nd NIC card.
That's all this thread is trying to get to. I've installed 8 different times on one appliance and had VoIPSupply send me another appliance with Pro preinstalled (just incase I was skipping that one step 8 times in a row) and I still did not get presented with the question.
That's all I wanted you to look in to. Nothing more.
Mike...
Please keep in mind
Thu, 05/08/2008 - 9:41am
Mike...
Please keep in mind that I don't want to use Trixbox DHCP for my network. I only want to use it for my phones so they can autoprovision and they do not have to travel on the same network as my servers/computers. I agree having 2 DHCP is very bad, but again, I don't want it for that. I would like to have a segmented network rather than a single network with servers/computers/printers/phones on it.
Currently, that is house it is set up. If you were to correct the DHCP in my system, it would not affect anything because nothing is plugged in to that 4-Port LAN card because it doesn't work...
Wow, makes me glad I built
Sat, 05/10/2008 - 7:17pm
Wow, makes me glad I built my own server, I agree with Jeff, this thing should work out of the box, that is way too may hoops to jump through.
I just recently setup PRO on my own "Unsupported" hardware and had nowhere near the problems you did, now keep in mind I am not using the 4 port switch nor the sangoma card at this time, but the bios setup was the biggest struggle I had on mine.
So you ran seperate cables for your phone system? I am going to be running mine on the same network using a netgear layer 3 switch and possible vlans.
Voipsupply
Sun, 05/11/2008 - 5:33am
Hello,
It sems to me that the vendor might want to ask how the lan setup will be. This would end some user grief on the installers aprt. Or have those settings readily available and easy to use. We received the wrong manual and wrong password with our system. The vendor also said they was having trouble with the install of Pro 2.0. Not very promissing from a vendor that says they sell several hundred every month. I wish there was a way to do local configurations at least temporarily or until the networks from Fonality come up. Sometimes it is a pain to make changes if there is no internet or Fonality goes down.
Thank you, Unkyjoe! Finally,
Mon, 05/12/2008 - 7:27am
Thank you, Unkyjoe! Finally, another person to see it how i do!
Most of my office already came with dual drops and all we had to do was install cubes and we went ahead and did dual drops there too. If i didn't already pay the money for the switches months before deciding to go with Trixbox, I would have set it up with VLAN's to make my life easier since this has become such an issue.
We replaced a Polycom system with a SIP exchange 4.6 system
Mon, 05/12/2008 - 8:42am
We replaced a home brewed call center with the trixbox and aastra system. They had dual drops. I can say that our client is totally happy with the trixbox system. however there are some small details that need to be addressed. which we hope to resolve on the forum. We have sold 2 more systems that are pending review by our other clients. Once the details are sorted out I think we can do another 20-30k in wholesale trixbox solutions. Voipsupply has been a little help. I do not think they are as knowledgable as they lead on. It takes several days to come to a solution which did not work. We bought a box solution from them also. Kind of disappointing to be in this position as we would have liked to have known up front, then it would not be an issue.
You know I am all for
Mon, 05/12/2008 - 8:10pm
You know I am all for CERTIFIED Hardware, I have run into too many problems before trying to get any LINUX based system installed reliably on multiple systems, Windows of course is more forgiving, and frankly most new hardware is written with Windows and not Linux in mind.
Now I am not flaming or anything, however when you pay for a box designed and built "I assume" by Fonality it should be tested and working out of the box, PERIOD!
If I want to futz with a system I will build my own, which is what I will do, that being said I will have no-one to blame but me when that system starts to give me problems. But Jeff I can feel your pain, everyone seems to be missing the issue that you should not have had this pain with the install.
Is this an isolated case, more than likely as I cant seem to find a lot of threads with this issue, however when this sort of thing happens to people who purchase a system from and approved vendor, and then things dont work properly there should be some recourse or support for getting the vendor supplied equipment to work.
If Dell sold me a computer with Windows XP or Vista, and had not loaded and checked the sound drivers I would be upset and expect support for free as well :)
Just me ranting :)
or a better analogy... Dell
Tue, 05/13/2008 - 8:33am
or a better analogy... Dell sold you a computer with windows vista, during the initial configuration Dell says there was an option to turn the sound on/off and that option was never presented. Now, rather than Dell just fixing the solution with their remote software (or VPN), they recommend you "edit the registry" in which doing so could potentially harm your system. -- Shame on them!!
Member Since:
2008-04-20