<?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 Field Reports</title>
	<atom:link href="http://www.tellatek.com/topics/phone-systems/nec-phone-systems-2/2000-ips/2000-ips-field-reports/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>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>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>
		<item>
		<title>Field Report &#8211; Non-Display Parking</title>
		<link>http://www.tellatek.com/2007/09/12/field-report-non-display-parking/</link>
		<comments>http://www.tellatek.com/2007/09/12/field-report-non-display-parking/#comments</comments>
		<pubDate>Wed, 12 Sep 2007 20:43:15 +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[revisions]]></category>

		<guid isPermaLink="false">http://blog.systems4less.com/?p=46</guid>
		<description><![CDATA[Trouble Summary:
When a non-display dterm parks a call using the call park feature key
(f5000) it is automatically placed into a bin.

Trouble Symptom:
When a non-display dterm parks a call using the call park feature key
(f5000) it is automatically placed into a bin. The feature works
correctly,
if
the user dials transfer and the access code (*3 then the user then
has to
enter the bin number).
Features and Specs states that this should work.

Modification Treatment:
Corrected by MP software R14 P1 1.04
S/Revision:R12.2 M1 1.03	Fix Revision: R14 P1 1.04


[email_link]

[ratings]

]]></description>
		<wfw:commentRss>http://www.tellatek.com/2007/09/12/field-report-non-display-parking/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Field Report &#8211; Paging over Handset</title>
		<link>http://www.tellatek.com/2007/09/12/field-report-paging-over-handset/</link>
		<comments>http://www.tellatek.com/2007/09/12/field-report-paging-over-handset/#comments</comments>
		<pubDate>Wed, 12 Sep 2007 20:40:18 +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[handset]]></category>
		<category><![CDATA[revisions]]></category>

		<guid isPermaLink="false">http://blog.systems4less.com/?p=45</guid>
		<description><![CDATA[Trouble Summary:
User hears internal zone paging over handset.

Trouble Symptom:
User hears internal paging over handset. When the user picks up the handset at the same time internal zone page is sent the user they hear the page over the handset. TDM Dterm extension 167 performs internal all-zone page. TDM Dterm extension 165 picks up handset to answer an inbound call (RT 00) at approximately the same time the internal page is sent.Extension 165 hears the page through the handset and the page is still coming through the speakers on the other ...]]></description>
		<wfw:commentRss>http://www.tellatek.com/2007/09/12/field-report-paging-over-handset/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Field Report &#8211; Delayed DTMF</title>
		<link>http://www.tellatek.com/2007/09/12/field-report-delayed-dtmf/</link>
		<comments>http://www.tellatek.com/2007/09/12/field-report-delayed-dtmf/#comments</comments>
		<pubDate>Wed, 12 Sep 2007 20:20:53 +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[revisions]]></category>

		<guid isPermaLink="false">http://blog.systems4less.com/?p=44</guid>
		<description><![CDATA[Trouble Summary:
Delayed DTMF on F2 software and above.

Trouble Symptom:
Delayed DTMF on F2 software and above when dialing from a TDM
Dterm.
Example: TDM Dterm 200 dials TDM Dterm 201
201 answers
200 dials 12345 on the dialpad and hangs up immediately
201 does not hear all of the digits dialed
DTMF digits dialed are delayed and when Dterm 200 hangs up the ORT
is
dropped; therefore 201 does not hear all digits dialed. This
scenario does not fail on F1 software and below. The digits dialed
are
sent &#8220;real time&#8221; not delayed.

Modification Treatment:
Normal operation of the IPS from F2 software and ...]]></description>
		<wfw:commentRss>http://www.tellatek.com/2007/09/12/field-report-delayed-dtmf/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Field Report &#8211; ATTCON transfer to UCD</title>
		<link>http://www.tellatek.com/2007/09/12/field-report-attcon-transfer-to-ucd/</link>
		<comments>http://www.tellatek.com/2007/09/12/field-report-attcon-transfer-to-ucd/#comments</comments>
		<pubDate>Wed, 12 Sep 2007 20:17:44 +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[revisions]]></category>

		<guid isPermaLink="false">http://blog.systems4less.com/?p=43</guid>
		<description><![CDATA[Trouble Summary:
Cannot transfer calls from Attendant console to UCD Group if UCD
member is not available.

Trouble Symptom:
Issue resolved with MP revision M1 0.13 or higher

Modification Treatment:
Issue resolved with MP revision M1 0.13 or higher
S/Revision:N/A	Fix Revision:M1 0.13


[email_link]

[ratings]

]]></description>
		<wfw:commentRss>http://www.tellatek.com/2007/09/12/field-report-attcon-transfer-to-ucd/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
