<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>tellatek.com &#187; 2000 IPS</title>
	<atom:link href="http://www.tellatek.com/topics/phone-systems/nec-phone-systems-2/2000-ips/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.tellatek.com</link>
	<description>All-You-Can-Eat Telecom and IT Buffet!</description>
	<lastBuildDate>Sun, 04 Jul 2010 19:32:15 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=abc</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>NEC Product Spotlight, Platform Changes and New Model Releases</title>
		<link>http://www.tellatek.com/2010/04/16/nec-product-spotlight-platform-changes-and-new-model-releases/</link>
		<comments>http://www.tellatek.com/2010/04/16/nec-product-spotlight-platform-changes-and-new-model-releases/#comments</comments>
		<pubDate>Fri, 16 Apr 2010 17:33:10 +0000</pubDate>
		<dc:creator>pingram</dc:creator>
				<category><![CDATA[2000 IPS]]></category>
		<category><![CDATA[Featured]]></category>
		<category><![CDATA[IPK]]></category>
		<category><![CDATA[IPKII]]></category>
		<category><![CDATA[NEC]]></category>
		<category><![CDATA[Phone Systems]]></category>
		<category><![CDATA[SV8100]]></category>
		<category><![CDATA[SV8300]]></category>
		<category><![CDATA[2000ips]]></category>
		<category><![CDATA[2000IVS]]></category>
		<category><![CDATA[2400IMS]]></category>
		<category><![CDATA[2400IMX]]></category>
		<category><![CDATA[Electra Elite]]></category>
		<category><![CDATA[nec]]></category>
		<category><![CDATA[Univerge]]></category>

		<guid isPermaLink="false">http://www.tellatek.com/?p=796</guid>
		<description><![CDATA[As you may have already figured out by reading my articles over the past few years, I have been working with NEC Key and PBX systems...]]></description>
		<wfw:commentRss>http://www.tellatek.com/2010/04/16/nec-product-spotlight-platform-changes-and-new-model-releases/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>714 Area code change effects a few things</title>
		<link>http://www.tellatek.com/2008/09/24/714-area-code-change-effects-a-few-things/</link>
		<comments>http://www.tellatek.com/2008/09/24/714-area-code-change-effects-a-few-things/#comments</comments>
		<pubDate>Thu, 25 Sep 2008 03:48:34 +0000</pubDate>
		<dc:creator>pingram</dc:creator>
				<category><![CDATA[2000 IPS]]></category>
		<category><![CDATA[Call Center and Voicemail]]></category>
		<category><![CDATA[NEC]]></category>
		<category><![CDATA[Phone Systems]]></category>
		<category><![CDATA[Zeacom]]></category>
		<category><![CDATA[2000ips]]></category>
		<category><![CDATA[area code]]></category>
		<category><![CDATA[call forward]]></category>
		<category><![CDATA[nec]]></category>

		<guid isPermaLink="false">http://www.tellatek.com/?p=415</guid>
		<description><![CDATA[Ok folks, I had a trouble ticket open regarding a particular client that could not use the call forward all feature without recieving the recording "You must first dial one plus seven one four...". The client presumed that the access code was being sent twice resulting in 9,91714...]]></description>
		<wfw:commentRss>http://www.tellatek.com/2008/09/24/714-area-code-change-effects-a-few-things/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>NeaxMail/EliteMail update &#8211; Changing the web port address</title>
		<link>http://www.tellatek.com/2008/09/03/neaxmailelitemail-update-changing-the-web-port-address/</link>
		<comments>http://www.tellatek.com/2008/09/03/neaxmailelitemail-update-changing-the-web-port-address/#comments</comments>
		<pubDate>Wed, 03 Sep 2008 18:03:40 +0000</pubDate>
		<dc:creator>pingram</dc:creator>
				<category><![CDATA[2000 IPS]]></category>
		<category><![CDATA[IPKII]]></category>
		<category><![CDATA[NEC]]></category>
		<category><![CDATA[NEC Cheat Sheets]]></category>
		<category><![CDATA[Phone Systems]]></category>
		<category><![CDATA[Tutorials]]></category>
		<category><![CDATA[Apache]]></category>
		<category><![CDATA[EliteMail]]></category>
		<category><![CDATA[IM16-LX]]></category>
		<category><![CDATA[Linux]]></category>
		<category><![CDATA[NeaxMail]]></category>
		<category><![CDATA[Voicemail]]></category>

		<guid isPermaLink="false">http://blog.systems4less.com/?p=121</guid>
		<description><![CDATA[Did you know that NEC&#8217;s latest voice mail platforms like the IM16-LX for the 2000 IPS or the EliteMail LX for the IPKII run on a Red Hat version of Linux?
So it didn&#8217;t come to any surprise that the web administration interface is provided through a version of the Apache web server.  http://www.apache.org/
Interestingly, I was a little surprised that NEC didn&#8217;t document how to change the listening port for the installing and maintaining technicians out there.
By default, the system uses the basic defaults:
http = tcp port 80
https = tcp ...]]></description>
		<wfw:commentRss>http://www.tellatek.com/2008/09/03/neaxmailelitemail-update-changing-the-web-port-address/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Message Waiting confusion?</title>
		<link>http://www.tellatek.com/2007/09/18/message-waiting-confusion/</link>
		<comments>http://www.tellatek.com/2007/09/18/message-waiting-confusion/#comments</comments>
		<pubDate>Tue, 18 Sep 2007 17:38:00 +0000</pubDate>
		<dc:creator>pingram</dc:creator>
				<category><![CDATA[2000 IPS Field Reports]]></category>
		<category><![CDATA[IPKII]]></category>
		<category><![CDATA[NEC]]></category>
		<category><![CDATA[Tips]]></category>
		<category><![CDATA[confusion]]></category>
		<category><![CDATA[end users]]></category>
		<category><![CDATA[firstly]]></category>
		<category><![CDATA[handset]]></category>
		<category><![CDATA[message lamp]]></category>
		<category><![CDATA[priority]]></category>
		<category><![CDATA[reminder]]></category>
		<category><![CDATA[speaker button]]></category>
		<category><![CDATA[voice mail message]]></category>
		<category><![CDATA[voice mail messages]]></category>

		<guid isPermaLink="false">http://blog.systems4less.com/?p=76</guid>
		<description><![CDATA[One common problem I encounter is the ability for end users to activate the message waiting lamp at other extensions and in turn causes confusion within the office.  End users often activate this accidentally.  The result is people thinking they have voice mail messages not knowing that the blinking light is essentially a &#8216;callback&#8217; reminder from another user.  Here&#8217;s a tip on how to minimize or eliminate this problem&#8230;  Firstly, here is how the function works:

Lift the handset or press the speaker button
Dial an internal extension ...]]></description>
		<wfw:commentRss>http://www.tellatek.com/2007/09/18/message-waiting-confusion/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>NEC 1000/2000 Time Change Instructions</title>
		<link>http://www.tellatek.com/2007/09/13/nec-10002000-time-change-instructions/</link>
		<comments>http://www.tellatek.com/2007/09/13/nec-10002000-time-change-instructions/#comments</comments>
		<pubDate>Thu, 13 Sep 2007 16:11:02 +0000</pubDate>
		<dc:creator>pingram</dc:creator>
				<category><![CDATA[2000 IPS]]></category>
		<category><![CDATA[NEC]]></category>
		<category><![CDATA[NEC Cheat Sheets]]></category>
		<category><![CDATA[Phone Systems]]></category>
		<category><![CDATA[Time Change Instructions]]></category>
		<category><![CDATA[nec 1000ivs]]></category>
		<category><![CDATA[nec 2000 ips]]></category>
		<category><![CDATA[nec 2000ivs]]></category>
		<category><![CDATA[nec time change]]></category>

		<guid isPermaLink="false">http://blog.systems4less.com/?p=64</guid>
		<description><![CDATA[NEAX 1000 / 1400 / 2000 IVS / 2000 IVS-2 / 2000 IPS
With Dterm Series III, Series E and Series i Phones
CAT Mode Procedure: This is to be done while the phone is in an idle state.


# 1. Press "TRANSFER"
# 2. Press "CONF"
# 3. Press *
# 4. Press "TRANSFER"
# 5. Press "CONF"...]]></description>
		<wfw:commentRss>http://www.tellatek.com/2007/09/13/nec-10002000-time-change-instructions/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Field Report &#8211; MA4000 Blocks MatWorx</title>
		<link>http://www.tellatek.com/2007/09/12/field-report-ma4000-blocks-matworx/</link>
		<comments>http://www.tellatek.com/2007/09/12/field-report-ma4000-blocks-matworx/#comments</comments>
		<pubDate>Wed, 12 Sep 2007 20:52:08 +0000</pubDate>
		<dc:creator>pingram</dc:creator>
				<category><![CDATA[2000 IPS]]></category>
		<category><![CDATA[2000 IPS Field Reports]]></category>
		<category><![CDATA[NEC]]></category>
		<category><![CDATA[Phone Systems]]></category>
		<category><![CDATA[PBX]]></category>
		<category><![CDATA[revisions]]></category>

		<guid isPermaLink="false">http://blog.systems4less.com/?p=49</guid>
		<description><![CDATA[Trouble Summary:
From R12.2 when we connect MA4000 and OAI application and we try to
do maintenace via MWX on TCP/IP port the port 60000 remian blocked.

Trouble Symptom:
After system upgraded to R12.2, so often PBX rest required to release
blocked TCP/IP 60000 port for maintenance.
One or two times per week, reset required.
Attached:
OFD, and ethereal trace when port is blocked.

Modification Treatment:
None, working as designed:
The design of the MA4000 PBX engine is that stays connected to the
PBX. After a period of inactivity the PBX will disconnect the MA4000
PBX engine connection. The next time MA4000 needs ...]]></description>
		<wfw:commentRss>http://www.tellatek.com/2007/09/12/field-report-ma4000-blocks-matworx/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Field Report &#8211; MA4000 turns off key ringing when assigning Dterm</title>
		<link>http://www.tellatek.com/2007/09/12/field-report-ma4000-turns-off-key-ringing-when-assigning-dterm/</link>
		<comments>http://www.tellatek.com/2007/09/12/field-report-ma4000-turns-off-key-ringing-when-assigning-dterm/#comments</comments>
		<pubDate>Wed, 12 Sep 2007 20:49:21 +0000</pubDate>
		<dc:creator>pingram</dc:creator>
				<category><![CDATA[2000 IPS]]></category>
		<category><![CDATA[2000 IPS Field Reports]]></category>
		<category><![CDATA[NEC]]></category>
		<category><![CDATA[Phone Systems]]></category>
		<category><![CDATA[PBX]]></category>
		<category><![CDATA[revisions]]></category>

		<guid isPermaLink="false">http://blog.systems4less.com/?p=48</guid>
		<description><![CDATA[Trouble Summary:
MA4000 turns off key ringing when assigning Dterm.

Trouble Symptom:
MA4000 turns off key ringing when assigning Dterm (CM9001-xxx,yy=0).
Tested inhouse with N1 3.00 and MA4000 5.0.1 with the same results.
Command 9001 for extension 16399 key 01 is turned to a 0 for non ringing.
Submit MA4000 PBX log of problem for a test request.

Modification Treatment:
Corrected in MA4000 5.0.3.8644
S/Revision:N1 2.03 (R13)	Fix Revision: 5.0.3


[email_link]

[ratings]

]]></description>
		<wfw:commentRss>http://www.tellatek.com/2007/09/12/field-report-ma4000-turns-off-key-ringing-when-assigning-dterm/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Field Report &#8211; MA4000 Button Assignments</title>
		<link>http://www.tellatek.com/2007/09/12/field-report-ma4000-button-assignments/</link>
		<comments>http://www.tellatek.com/2007/09/12/field-report-ma4000-button-assignments/#comments</comments>
		<pubDate>Wed, 12 Sep 2007 20:47:13 +0000</pubDate>
		<dc:creator>pingram</dc:creator>
				<category><![CDATA[2000 IPS]]></category>
		<category><![CDATA[2000 IPS Field Reports]]></category>
		<category><![CDATA[NEC]]></category>
		<category><![CDATA[Phone Systems]]></category>
		<category><![CDATA[PBX]]></category>
		<category><![CDATA[revisions]]></category>

		<guid isPermaLink="false">http://blog.systems4less.com/?p=47</guid>
		<description><![CDATA[Trouble Summary:
Edit of Button Assignments results in losing Speed dial buttons

Trouble Symptom:
Edit of Button Assignments results in losing Speed dial buttons, MA4000
Version 5.0.2 PBX version N1 3.00 Tech states that if he Syncs a PBX and
edits Buttons on a 32button phone (with F11XX assignments) and saves
this will results in removal of button assignments including F11XX from
station. Tested in NTAC with same versions of MA4000 and PBX and found
same results. on NTAC switch Added all zone page (Raw code F1278) to
Extension 100 Button 05 ON A 32Button IP Phone.
Prior to changing ...]]></description>
		<wfw:commentRss>http://www.tellatek.com/2007/09/12/field-report-ma4000-button-assignments/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
