Newbie Observations and Questions...

[mhorwood]

First I would like to say thank you to the Originators and Participants in this and other PBXIAF sites. Without these resources I would not be having near as much success as I have with Asterisk and SIP PBX's.

Also if I am out of form here, please excuse my ignorance, and slap my hand, as this is the first "support forum" I have ever participated in.

Some background on me: I am a 50+ year old self employed low voltage contractor.. That is to say I install Data & Voice Wiring, Windows Servers, Windows Workstations, Background Music, Whole house Automation, etc... i like to think of myself as "One-Stop-Technology" shopping for your new business start up. My core clientele are small to mid-size Doctor and Dental offices. Many in my client base find merging of resources necessary to be competitive, so many doctors are running more than 1 office and dividing time between locations. Merging of the "networks and communication" for these offices is desired to avoid duplication of labor. Consequently I have been pushed into wide area networking of data and phone systems.

What led me here: Recently my phone systems manufacturer of choice was bought out by one of the big name conglomerates. I have 5 locations using one of their newest (post merger) offerings which is a hybrid PBX with some IP capability that allows networking of multiple sites. Long story shortened... Networking works fine... Just cant hear the conversation coming through the analog CO trunks. I've stopped selling them... Something inside the "Box" appears to be distorting the voice-path to the point that any background noise, "Sidetone" in interconnect speak, renders the caller VERY difficult to hear. I have the exact same complaint on all 5 locations, located in 5 different towns. Yes I have checked the lines in all 5 locations, voltage, loop current, etc.. The analog CO lines are fine... Most are textbook. I'm convinced the manufacturer has designed a lemon.. Lucky me...

My first challenge will to be to do a warranty replacement of systems in two locations that are networked. The "No-1" location has 16 extensions with 5 analog trunks. The "No-2" location has 8 extensions with 3 analog trunks. They share 4 IP trunks that are point to point from locations 1 to 2. Both locations have a range of static WAN IP addresses, with no VPN between locations.

As you've guessed I am changing brands...Asterisk will no doubt do the job. Mostly overkill. I have been working on learning PBXIAF by building two systems on the bench and using them in my own office. I have installed PBXIAF Bronze as per website recommendations. I have found Grandstream phones to interface and work out of the box. I have found Aastra phones (6757i) to be harder to configure, but for now it seems to be staying connected. (Had to change a timer to get it to stick)..Thank you to the geniuses that made FreePBX and Linux Webmin, as i would not have succeeded without them..

I applaud Ward Mundy for his attention to security. (My reason for choosing PBXIAF) I agree that any computer system that touches the internet MUST be hardened. (wish I could do that with windows)

So here is question 1: I will be using analog trunks. Should I install a hardware VPN from location 1 to location 2, so as to keep both of the Asterisk boxes completely behind the firewall ? This would also necessitate VPN connections from the Doctors homes to the office. This would seem to be the most secure setup. I do see that GeekUno has found a way to connect to SIP trunk providers outbound through NAT, but for inbound extensions, the only way I see is to open a port for sip. Anyone have experience with an exposed SIP port? Is PBXIAF / Centos secure enough to keep the hackers out with just strong passwords?

Question 2: I think the SIP port could be moved to a "Non-Standard" port to slow down hack attempts, but UDP ports 10,000 to 20,000 also get opened, and the docs say not to relocate them because of "performance" issues. Should I be concerned? Makes me kinda nervous opening this many ports, even if it is a Centos Box... Can the UDP range also be relocated ?

Question 3: Can someone send me the link syntax for centos, to wget the current Aastra 57i firmware from their site. WM's article "The World's Best Asterisk Phone" is dated and the links in the article point to files that are zero bytes. I can get to them in a windows browser and download the newer files to windows, but the same links do not work in a wget on centos. Newbie frustration. I guess I could install samba and move the downloaded files that way, but that seems like cheating...

Question 4: To my ears (that have a 25% hearing loss), the Grandstream phones seem to have just as good a sound quality as the Aastra phone. Short of me getting WM's fancy features working on the Aastra 57i, I do not see an advantage to spending double on the 57i. Epically when this will be a warranty replacement,(Upgrade ?). I'm not used to having 200+ options to choose from.. With prices ranging from $59 to $800.. How is an installer to know ? Most of my clients just want to be able to hear the caller and have a "pretty" phone on their desk! Cisco has name recognition, but do they play well with PBXIAF ? Ultimately I will present a few brands to the customer and let the customer decide. Based on web research, I have tried the Aastra 57i and the Grandstream GXP2000 and the GXP280. Does anyone have a broad experience with different phone instruments that could lend their 2 cents on phone choices?

Question 5: Is there anyone interested in doing paid phone / remote support for this newbie? When/If I jump into this and install "Live" systems, my clients will want it to work.. NOW... I will do a bench install of the software, and will pre-configure and test the servers before I deploy them. Problems in the field will require a FAST resolution. As well as compensating for my lack of knowledge. Yes I know I can buy $150/hr professional support, but that is hard to absorb seeing that I only charge $90/hr for myself ! (I am located in Michigan, which has yet to crawl out of the recession) I could barter with SIP phones that I will have remaining in inventory! Anyone Interested ?

Question 6: Does anyone know of anyone that will sell a custom configuration as a backup/restore...? Seems that there might be a market for someone to cater to people like me that are transitioning into IP/Computer based phones from the interconnect market that are working for paying customers. I know that I know just enough to be dangerous.. and would be willing to pay for an "expertly" done custom configuration that included a 30-day install-support pack. Having someone covering my lack of knowledge would give me a warm fuzzy confidence that I do not currently have. Is there anything like this out there short of buying a whole "canned" configured box, that I would have to custom configure anyway?

Observation 1: (this might better be posted elsewhere ?) If you install PBXIAF bronze AND use Digum TDM400p FXO cards, you will need to manually run dahdi_genconf from the command line after the PBXIAF install and then reboot. Took me 2 days, 4 loads, on 2 machines, to realize that PBXIAF was not using Zap-tel drivers, and another day to find the dadhi configuration files were missing.. DaaaaaaDhi... Yes, you Linux guru's can laugh. I chuckle NOW too.. I AM getting re-acquainted with the term Newbie. Been a while since I had to print hundreds of pages of Doc's and actually study them. This tip could save someone else hours of hunting...

Not that this is the end to my list of questions... But I fear to be banned from this forum for being too wordy... and too newbie... So I will thank you in advance, I will sit and take whatever flak, (er suggestions) you choose to shoot my way... I only ask that you be kind, as I do not move, (or think) as fast as I used to... Now that I have joined the over 50 crowd ! (At least now I have an Excuse!) Thanks !

Mike Horwood
Owner HCCLLC

 

[euser4life]

Welcome to the forums. As you've stated there are a number of different combinations. I've sent you a pm.

 

[Linetux]

question 1:

Yes, you can do this. It helps if your doctors' homes have static IP's. If not, perhaps the ISP has a range you can stick to... a small one, preferably. You can restrict extensions from registering except from specific IP's, which is a big + if you have to open them up.

Failing that, you can setup VPN's between the offices, even using consumer-grade VPN/router devices like Linksys, Netgear, etc. Watch the upstream bandwidth, it's a conversation killer.

I run a private 'hotline' over the internet and expose port 5060 to the world. I rely on strong SIP passwords (50+ characters) and IP authentication.

Question 2: That will cause more headaches than it will solve. If you can't VPN the traffic, don't bother going with non-standard ports.

You shouldn't have to worry about the RTP ports (10000-20000) security-wise. It's just to carry the conversation, not for authentication.

Question 3: Install the Aastra scripts - if you follow the directions, it will have you download the firmware RPM: http://pbxinaflash.com/community/threads/aastra-xml-2-3-0-scripts.7712/?t=7712

If you want to do it directly, it'd be:

wget http://nerdvittles.dreamhosters.com...a-xml-2.3.0/aastra-ipphone-2.6.0-2.noarch.rpm

(then "rpm -Uvh aastra-ipphone-2.6.0-2.noarch.rpm")

Question 4: I don't much care for Grandstream. Most everyone will tell you they're trash.

If you're looking for a good, basic office phone, check out Yealink. I know people that have these installed in call centers by the 1000's on Asterisk systems - people who have been doing this for a very long time and know what's what. If Aastra isn't your speed, Polycom is too expensive/complex, I'd say Yealink is a great alternative.

http://www.yealink.com/index.php/Products/lists/classid/2

Question 5: I do consulting from time to time, but the situation has to fit. PM me if you want to talk more.

Question 6: Yes, but it can get complicated. You can buy from folks like Rhino, and they'll sell you professional looking hardware that'll work great (there are others as well). I've done a bit of work around this same concept, as I have a number of remote locations that I keep regular backups of "just in case" - but you know what? The only time I've had to step foot on-site was when I decided to upgrade the software on the box - not because there was a problem.

To your observation: I would suggest staying away from Digium hardware if you want trouble-free installs. Just a suggestion.

 

[atsak]

I deal with Question 1 this way:
There is a hardware VPN between offices. I use Juniper SSG's, but anything that's stable should be fine. Junipers have a nice GUI I can handle as a Windows guy. For the home installs, I have them run dynamic DNS on their home firewall or computer, and then have a firewall rule that permits traffic (5060 and UDP) from those dynamic DNS names.

Question 3. Use winscp if you run into this hassle; secure copy the files from your desktop.

Question 4. I think it's probably splitting hairs. I have had trouble with every kind of phone (but only little things, broken handset on occasion etc).

Question 5. I have done this in the past; it depends on whether I have enough knowledge to help. I have been at VOIP for a while first on Nortel but only have a half dozen field installs. PM me if interested.

Question 6 - several things out there; do some searches, but the Rhino one is probably good. I always offer customers a second "backup" system that has a copy of their base install duplicated on it. Since most offices can run on $300 servers, it's often worth it.

Hope that helps.

 

[jroper]

Hi

Welcome to the forums, all good advice above. What you will learn is that this job is about 80% networking, and 20% is everything else.

A properly designed network, independent of any outside influences, such as windows DHCP servers stopping working, DNS servers failing, PC NIC card in broadcast storm state, will make your life easier, as the phone system is always displays the first symptoms of network issues, and therefore gets the blame.

Also site survey for network and power is a must. Preparation on the bench beforehand is useful, remember the 7 P's. Proper Planning and Preparation Prevent P1ss Poor Performance. It reduces the time to deploy by a good margin.

Joe

 

[wardmundy]

 

[mhorwood]

Atsak,

Being a Net-nerd, I regularly use Dyndns. Can "DNS Names" be used in the scripts? IF so then you could lock down the incoming to exactly one name. Would be pretty secure, as the attacker would have to know the DNS lookup in addition to the password.

Not sure what WinScp is... Will google it.

A half dozen installs is a half dozen more than I have under my belt.. but I have gotten bold.. I did my first quote for my wife's office today... They know I am on a learning curve, and I do not think they will fire me if I goof up a little... So I guess I am not too far out on a limb...

A backup system is a good idea, especially with the cost of hardware so low... Hardware failure is a "when", and not an 'if'... I think I read that WM has a backup system in some of his offerings that will clone the current status of the system. (If I understand it correctly). Should be a quick restore to other hardware from there.. Might not even loose too much...

From a "Salesman" perspective I feel lacking in my knowledge of how various trunk services interact on SIP. My challenge will be that the current customers have existing published numbers that the will want to keep. All inbound traffic will go to those numbers. I will find it difficult to talk them directly out of their hard-lines. My thought is to get "Local" numbers on the sip trunks, so I can "Closet Phone" forward to the sip trunks, like in the old modem days where we would hop from one exchange to the other to avoid LD charges. Sip or internet go down, and I can un-forward and get calls. I'm sure there must be a more modern approach to this, and still preserve some hard-lines to fail to.

Thanks for the ideas... Mike H

 

[mhorwood]

Joe, So happens networking is one of my stronger points. Own lots of Toys, (er, tools) including protocol analyzers, cable certification equipment, etc.. HP Procurve switches have been my friend for years.. A good switch will head off lots of issues, and with procurve I can do QOS. (Not that I have had a need until now)

My new Fluke NetTool will do VOIP Latency measurements so I should have a way to help diagnose issues..

Some opinions i have read say that a separate net for VOIP is the way to go... Seems overkill for 3-16 users, even if the channels were "Toll Quality" that is only 64kbits per call. Doesn't add up to a problem on any of my networks. Will just have to get the VOIP packets to go to the head of the line.... and then only on a heavily loaded lan segment. BTW A2Billing looks impressive... Can't think that big... yet.
Thanks Mike H

 

[mhorwood]

Lorne, My newbie is showing. I've tried file manager without success. Someplace I am not connecting the dots..

I finally got my 57i to stay connected. Found somewhere that a timer inside the phone SW,(don't remember which one) that was set to 4000, needed a "Bigger" number. Set it to 8000 and now all seems happy. Bothers me when I fix something and do not understand what did the fix..

The picture of the 57i with all the LCD populated in WM's article, makes my Geek tingle.. Sometimes a little software feature will trip the fancy of a customer, and get the sale..

My 57i is out on "Show and Tell", so I will have to work on the scripts when I get it back next week...

Current hurdle will be sound quality, at least on the next 5 installs I see coming... I seem to have seen in FreePBX some settings on TX - RX Gain... I'm hoping there are tweaks inside just in case I run into issues. Haven't read of horror stories re sound quality with Asterisk, In fact some have touted SIP as better than Analog.. The Interconnect industry is still shying away from SIP, maybe because we do not understand it.... Thanks. Mike H

 

[jroper]

Some opinions i have read say that a separate net for VOIP is the way to go... Seems overkill for 3-16 users

Hi
The first sentence is my opinion, if it can easily be implemented, and depending who is in charge of the rest of the network.

Problems I have experienced, which resulted in loss of customer confidence in the phone system are:-

New wifi router added, which dished out it's own range of IP addresses, and killed the windows server DHCP, resulting in phones not being able to contact the PBX. PBX blamed.

Router reconfigured to issue a DHCP range which issued duplicate addresses to the phones on .201 upwards. PBX blamed.

Local DNS server failed, therefore SIP trunks failed on PBX.

Windows PC NIC card failed resulting in broadcast storm, PBX blamed.

And my favourite, "Fridge failed, is it anything to do with the phone system?"

So the less prone you can make the system to outside influences, and general numptyism, particularly if another IT person is involved, (who may try to blame the phone system for his problems) then the quieter your life, and the more reliable the system.

Joe

 

[jmullinix]

Joe,
So True.

 

[mhorwood]

Being a network tech, I get the "More than 1 DHCP" server issue regularly. Usually a wireless router being installed in the CEO office for WiFi access. Connection to the LAN port puts the internal DHCP server on the LAN along with the one that is usually already there. Nobody wins...

In this business you are either a Hero when it is fixed or the Villain when it isn't.