Michael McNamara
technology, networking and IP telephony
Avaya Communication Server 1000 6.0 SIP Trunking with Bell Canada
Aug 21st
Avaya has released another technical configuration guide (application note) from their interoperability testlab regarding how to properly configure the Avaya Communication Server 1000 release 6.0 for SIP (PSTN) trunking with Bell Canada.
I figured I’d better not skip the Bell Canada document for fear of upsetting my Canadian readers. ;)
I’m really excited to see Avaya providing this information to both their resellers and customers. I’d like to thank those that wrote and lobbied for these documents within Avaya. It’s extremely encouraging to see Avaya willing to empower their users so they can leverage their products and investments to their fullest.
Cheers!
References;NN10000-132_1.0_ CS1000_R5.5_Bell_SIP_Trunking_App_Notes.pdf
Ethernet Routing Switch 5000 Software Release v6.2.0.200
Aug 20th
Avaya has released software 6.2.0.200/201 for the Ethernet Routing Switch 5500/5600 series switches.
The following issues were identified and resolved in this release;
- SMLT – IST/SMLTs may bounce every 2-3 hours (Q02161349)
Issue was present on 56XX devices when used as IST peers. Issue not present on 55XX devices. - ERS5600 vt6.2-trials: ARP table timeout (Q02162399).
ARPs would timeout in certain scenarios only when using 5520/5530 devices in stacks as IST peers and when connected through SLT (not SMLT) to edge devices. - Power is cut off when AES is deactivated (Q02146930)
Please review the release notes for all the specific details.
We recently had a discussion regarding why Avaya released 6.1.4 software after releasing 6.2.0. This is a perfect example of why you don’t rush into major software releases unless you’re prepared to bleed alittle. I wonder how they came up with the phrase bleeding edge? This isn’t just an issue with Avaya either, I’ve see it with every vendor I’ve ever worked with including Cisco, Juniper, Blue Coat, etc. Now it’s definitely true that some vendors are much better than others in both their software development and their QA testing but there are always going to be some issues.
Cheers!
Blue Coat ProxySG Appliance – test http url
Aug 18th
We recently had an issue where a few of our Blue Coat ProxySG appliances were having issues connecting to a specific URL. We would continually get the “TCP Error” banner from the Blue Coat proxy servers trying to connect to this website. We had no issues connecting directly (outside of the ProxySG appliances) so the proxy servers were assumed to be the immediate suspect in the problem.
Thankfully there’s a way to quickly and easily test access a specific URL from the CLI interface of the Blue Coat ProxySG appliances.
SG800#test http get ? <url>
So I performed a quick test from the CLI interface;
SG800#test http get http://someurlsomewhere.com Type escape sequence to abort. Executing HTTP get test * HTTP request header sent: GET http://someurlsomewhere.com HTTP/1.0 Host: someurlsomewhere.com User-Agent: HTTP_TEST_CLIENT * HTTP response header recv'd: HTTP/1.1 503 Service Unavailable Cache-Control: no-cache Pragma: no-cache Content-Type: text/html; charset=utf-8 Proxy-Connection: close Connection: close Content-Length: 1329 Measured throughput rate is 0.03 Kbytes/sec HTTP get test passed
It was easy to immediately see that the web server was returning a 503 error to the proxy server, something that was impossible to see from the client browser and difficult to locate from the log files.
The hosting company for the server in question eventually resolved the issue when they removed the automatic blacklisting that had been automatically placed on the proxy server’s public IP address after too many people failed to authenticate properly (because the website in question had a password on it).
Here’s the test when it worked properly returning a 401 error requiring the user to authenticate;
SG800#test http get http://someurlsomewhere.com Type escape sequence to abort. Executing HTTP get test * HTTP request header sent: GET http://someurlsomewhere.com HTTP/1.0 Host: someurlsomewhere.com User-Agent: HTTP_TEST_CLIENT * HTTP response header recv'd: HTTP/1.1 401 Authorization Required Date: Wed, 11 Aug 2010 15:40:31 GMT Server: Apache/2.2.3 (CentOS) WWW-Authenticate: Basic realm="For Acme Health only..." Content-Type: text/html; charset=iso-8859-1 Cache-Control: proxy-revalidate Content-Length: 479 Connection: close Proxy-support: Session-based-authentication Measured throughput rate is 4.50 Kbytes/sec HTTP get test passed
Cheers!
Avaya Communication Server 1000 6.0 SIP Trunking with Frontier
Aug 18th
Avaya has released another technical configuration guide (application note) from their interoperability testlab regarding how to properly configure the Avaya Communication Server 1000 release 6.0 for SIP (PSTN) trunking with Frontier Communication System. The document is highly technical and very thorough and while it might be “over the top” for some it’s just what the doctor ordered for those users who are eager to take a more hands on approach to their voice solutions rather than just relying on resellers.
Cheers!
References;NN10000-133_1_CS1000_R6_FrontierComSIPTrunkAppNotes.pdf
Loading ...
RECENT COMMENTS