Newbie Guide to Asterisk Pitfalls
Labels: Asterisk, Hardware, IT Management, Networking, Trixbox, VoIP
Labels: Asterisk, Hardware, IT Management, Networking, Trixbox, VoIP
Labels: Networking
Prohibited Users of HSI. You agree not to use HSI for operation as an Internet service provider, a server site for ftp, telnet, rlogin, e-mail hosting, "Web hosting" or other similar applications for any business enterprise, or as an end-point on a non-Comcast local area network or wide area network.
You agree to indemnify, defend and hold harmless Comcast and its affiliates, supplies, and agents against all claims and expenses (including reasonable attorney fees) arising out of any breach of this Section including, but not limited to, any claims based on or arising out of any material violation of any applicable law.
ADDITIONAL PROVISIONS APPLICABLE TO HIGH-SPEED INTERNET SERVICE
Comcast will provide you with dynamic Internet protocol ("IP") address(es) as a component of HSI, and these IP address(es) can and do change over time. You will not alter, modify or tamper with dynamic IP address(es) assigned to you or any other customer. You agree not to use a dynamic domain name server or DNS to associate a host name with the dynamic IP address(es) for any commercial purpose.
Labels: Networking
Formula for the best remote telecommuter Experience
- Use T1 internet access at the main location, not DSL or Cable.It’s worth the additional expense in order to ensure good, steady performance at your main location.
- If your routers and/or firewalls support QoS features, activate them. Give priority to the SIP and RTP protocols. Consider replacing equipment that lacks VoIP-aware QoS features. See Also: How do I use QoS on my network?
- Consider using one of our Suggested Routers with QoS on both ends of your connection.
- If your QoS solution allows you to limit total bandwidth, set the limit to slightly less than the line speed of your internet connection. Use a DSL line speed test to determine where you should set your limits. Setting it about 5-10 Kb below your maximum speed will keep the packet buffers from filling up on your DSL/Cable modem. This will yield better overall performance.
- Consider having two internet connections… one for your existing data application, and one for your VOIP phone and trixbox Pro servers. You can use this approach in your main location, as well as your remote locations. If you use this approach, you may not need any QoS capable equipment.
- If possible, connect your main office and your remote office using the same internet provider. Usually performance on the same provider’s network is superior to the performance when traffic needs to traverse multiple internet backbone networks.
- If possible, remove NAT devices between the trixbox Pro system, and the remote telecommuters.
- If you must use a NAT configuration, consider using a “DMZ Host/Server” configuration rather than port forwarding. This uses less CPU power in the router/firewall and yields optimal performance.
- At the main location, the setting will forward all unknown packets to your trixbox Pro server.
- At the remote locations, the setting will forward all unknown incoming packets to the IP Phone.
- Reserve the phone’s IP address in DHCP or give the phone a static IP Address on your private network in the remote location so the IP Address does not change. If you use a static IP Address, pick one outside of your dynamic DHCP IP Address range.
- For mission critical remote employees, consider using a fractional T1 internet service at the remote office instead of a Cable/DSL connection.
Labels: Asterisk, Networking, Trixbox, Videoconferencing, VoIP
C:\netsh firewall show state
Firewall status:
-------------------------------------------------------------------
Profile = Domain
Operational mode = Enable
Exception mode = Enable
Multicast/broadcast response mode = Enable
Notification mode = Enable
Group policy version = Windows Firewall
Remote admin mode = Disable
Ports currently open on all network interfaces:
Port Protocol Version Program
-------------------------------------------------------------------
1052 UDP IPv4 C:\WINDOWS\system32\spoolsv.exe
26675 TCP IPv4 (null)
67 UDP IPv4 (null)
135 TCP IPv4 C:\WINDOWS\system32\inetsrv\inetinfo.exe
137 UDP IPv4 (null)
139 TCP IPv4 (null)
138 UDP IPv4 (null)
3389 TCP IPv4 (null)
38293 UDP IPv4 (null)
443 TCP IPv4 C:\WINDOWS\system32\inetsrv\inetinfo.exe
443 UDP IPv4 (null)
445 TCP IPv4 (null)
37674 UDP IPv4 (null)
37675 UDP IPv4 (null)
37674 TCP IPv4 (null)
2869 TCP IPv4 (null)
1900 UDP IPv4 C:\WINDOWS\system32\svchost.exe
2967 UDP IPv4 (null)
990 TCP IPv4 F:\Program Files\Microsoft ActiveSync\rapimgr.exe
Additional ports open on Local Area Connection:
Port Protocol Version
-------------------------------------------------------------------
427 UDP Any
C:\
Labels: Networking, Resources, Tech_Friday, Windows
...[I]n practice we have found that router based clients just don't provide the same level of reliability and user experience as software clients. For this reason, our current recommendation is that customers use a software client whenever possible, even if their router has a DDNS client built into it and even if that DDNS client has been certified by us.Using the command line version of inadyn, I tried the following which does a one-time update:
C:\DynDNS_Client>inadyn --username myname --password mypass --alias mydnsname.gotdns.com
INADYN: Started 'INADYN version 1.96.2' - dynamic DNS updater.
I:INADYN: IP address for alias 'mydnsname.gotdns.com' needs update to '24.61.26.209'
I:INADYN: Alias 'mydnsname.gotdns.com' to IP '24.61.26.209' updated successful.
Labels: Networking, Windows