<?xml version="1.0" encoding="UTF-8"?><!-- generator="WordPress/2.9.2" -->
<rss version="0.92">
<channel>
	<title>avaya.dwalin.ru</title>
	<link>http://avaya.dwalin.ru</link>
	<description>All things Avaya</description>
	<lastBuildDate>Fri, 04 Nov 2011 08:28:11 +0000</lastBuildDate>
	<docs>http://backend.userland.com/rss092</docs>
	<language>en</language>
	
	<item>
		<title>Tutorial: Copying files to and from CMS with PSCP</title>
		<description><![CDATA[When I was working for Avaya business partner building call centers, one of the most frequent questions of my customers was: how do you copy files to and from CMS? Every time I had to go to explanations and wished I just had a tutorial I could point people to. Now, here it is.
In fact, [...]]]></description>
		<link>http://avaya.dwalin.ru/call-management-system/tutorial-copying-files-to-and-from-cms-with-pscp/</link>
			</item>
	<item>
		<title>AES Trace (renew)</title>
		<description><![CDATA[Did you remember my old post about tracing on AES side. It was little bit difficult. You need to change file and bla-bla-bla. Now we have more easier way, just type trcedt  servicename  set [on&#124;off&#124;bits] bit[1-8]. ie. for trace TSAPI &#8220;trcedt TSAPI set on 1&#8243;
]]></description>
		<link>http://avaya.dwalin.ru/quick-tips/aes-trace-renew/</link>
			</item>
	<item>
		<title>Tutorial: Using Informix tools to access CMS historical database</title>
		<description><![CDATA[Following my previous article, I decided to expand on this topic; I feel it may prove useful for people who don&#8217;t want to (or can&#8217;t) mess with ODBC in CMS to still have access to historical and administrative data.
Here&#8217;s how to do it.
As you probably know CMS uses Informix IDS (Informix SE before CMS R9) [...]]]></description>
		<link>http://avaya.dwalin.ru/call-management-system/tutorial-using-informix-tools-to-access-cms-historical-database/</link>
			</item>
	<item>
		<title>How to list CMS users</title>
		<description><![CDATA[Following a discussion on Avaya Users forum, here&#8217;s how to use standard Informix utility dbaccess to query CMS database and get the list of users defined in CMS, with their logins, names and locations:
. /opt/informix/bin/setenv
dbaccess cms@cms_ol - &#60;&#60;!
select l_name, f_name, room, telephone from users
!
You need to run this as root since only root account has [...]]]></description>
		<link>http://avaya.dwalin.ru/call-management-system/how-to-list-cms-users/</link>
			</item>
	<item>
		<title>Using CMS External Call History Interface, part 1: Data Extraction</title>
		<description><![CDATA[Avaya Call Management System is very good as a standalone reporting solution, but it has its drawbacks, too. Besides having very outdated architecture and performance limitations, its lack of openness for external applications was always one of the major concerns for anybody who wanted to make the most of their call center. For example, people [...]]]></description>
		<link>http://avaya.dwalin.ru/call-center/using-cms-external-call-history-interface-part-1-data-extraction/</link>
			</item>
	<item>
		<title>Connecting to CMS terminal with TuTTY</title>
		<description><![CDATA[Using CMS terminal UI is easy; in some aspects it is even easier than CMS Supervisor application. There are lots of different terminal emulators out there, simple and complex, free and paid. Some require extensive learning, some do not. I will show how to use TuTTY, a freeware SSH and Telnet client software, with CMS [...]]]></description>
		<link>http://avaya.dwalin.ru/call-management-system/connecting-to-cms-terminal-with-tutty/</link>
			</item>
	<item>
		<title>OSSI implementation as Perl module</title>
		<description><![CDATA[An accidental but fantastic find: Benjamin Roy posted an article describing ready Perl module he wrote for managing his Avaya PBXes. Well, actually the module is the back end and he&#8217;s talking about Web service utilizing that back end to provide application interface. Code looks a bit incomplete but that&#8217;s definitely a start, I think [...]]]></description>
		<link>http://avaya.dwalin.ru/communication-manager/ossi-implementation-as-perl-module/</link>
			</item>
	<item>
		<title>Mastering Device, Media and Call Control</title>
		<description><![CDATA[As follow-up to a recent post regarding DMCC developer&#8217;s guide, I have found another very interesting and useful document on the same topic. It is a DevConnect publication called &#8220;Mastering Device, Media and Call Control Using Avaya DMCC Dashboard&#8221;. It&#8217;s not only a guide, it&#8217;s a whole tutorial that I think is a must have [...]]]></description>
		<link>http://avaya.dwalin.ru/computer-telephony-integration/mastering-device-media-and-call-control/</link>
			</item>
	<item>
		<title>Configuring LLDP on Cisco Catalyst switches for using with Avaya 46XX IP Phones</title>
		<description><![CDATA[Another white paper I found in my archive. I don&#8217;t know why all these useful documents are disappearing from Avaya website but somehow they do. This one I had saved in my email folder as file rather than link so here it is.
Cisco LLDP with 46XX IP Phones
]]></description>
		<link>http://avaya.dwalin.ru/ip-phones/configuring-lldp-on-cisco-catalyst-switches-for-using-with-avaya-46xx-ip-phones/</link>
			</item>
	<item>
		<title>CMS licensing</title>
		<description><![CDATA[Did you know that CMS Supervisor licenses are used exactly as their name suggests, only for CMS Supervisor application instances? Yes, they are–and it means that terminal access is not limited. Teach your supervisors or managers to use that “scary text interface” and you can save your company a chunk of $$ on supervisor licenses.
Agent [...]]]></description>
		<link>http://avaya.dwalin.ru/call-management-system/cms-licensing/</link>
			</item>
</channel>
</rss>

