Customer has a MICS with 2.0 software. What is the minimum software version a MICS may have to add a PRI. They currently have a T-1 and want to go PRI. Can't seem to find that info on my compatibility chart. I will keep looking. Does anybody have a good chart that I can check? Thanks !!!
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
MICS 2.0 PRI ?????
- Thread starter colotelco
- Start date
lugerlover
Programmer
4.1 but software was flaky untill last rel of 6.1 now at 7.1
Need key code to enable PRI
Need key code to enable PRI
Norstarguru
Vendor
4.0 is the earliest version and you will need a PRI Keycode, T-1 Card, Service Card or 6 Port combo, there were some routing issues but I never actually ran into the problems
norstarguru
norstarguru
lugerlover
Programmer
4.0 is the most unstable version of software todate
Norstarguru
Vendor
sold and installed over 400 copies of 4.0 never had any unstable problems...Regardless you need any software with the PCMICA Card to do PRI.
And if you have a voicemail or ACD system you will need to get the version software because more than likely you will need a software upgrade on this unit before you do the upgrade.
There is an upgrade tool that will move all of your programming but I find for the cost I can reprogram the whole system for less in labor than the cost of the tool.
norstarguru
And if you have a voicemail or ACD system you will need to get the version software because more than likely you will need a software upgrade on this unit before you do the upgrade.
There is an upgrade tool that will move all of your programming but I find for the cost I can reprogram the whole system for less in labor than the cost of the tool.
norstarguru
jerryreeve
Vendor
hate to say it but 4.0 only was on the market for a few weeks before the 4.1 replaced it. all the docs were still printed with 4.0 on it but 4.0 definately was not offered for sale for very long.
I just put in a PRI on rel 6.1 software and there was a glitch if you are connecting to a DMS100 style CO switch. the software just does not recognise the PRI init string from the DMS. had to upgrade to 7.1 to get them working.
4.1 software had very few PRI problems but the lack of secondary dial tone (Dial tone after dialing the 9) can be disconcerting to the customer. upgrading to 7.1 is probably the best but if you are running a NAM NVM2.0 you will probably need to upgrade the whole voicemail to a call pilot.
----------------------------
JerryReeve
Communications Systems Int'l
com-sys.com
I just put in a PRI on rel 6.1 software and there was a glitch if you are connecting to a DMS100 style CO switch. the software just does not recognise the PRI init string from the DMS. had to upgrade to 7.1 to get them working.
4.1 software had very few PRI problems but the lack of secondary dial tone (Dial tone after dialing the 9) can be disconcerting to the customer. upgrading to 7.1 is probably the best but if you are running a NAM NVM2.0 you will probably need to upgrade the whole voicemail to a call pilot.
----------------------------
JerryReeve
Communications Systems Int'l
com-sys.com
- Thread starter
- #7
lugerlover
Programmer
issues with 4.0
MICS 4.0 WI 5.01
ITAS SRN-012 April 5, 1999
UPDATE 6/16/99 Scenario #3 is corrected in MICS 4.0 WI 5.05 see SRN-016
MICS 4.0 is Norstar's newest addition to the product portfolio and it's major feature enhancement is PRI connectivity. MICS 4.0 was released to the market place January 25, 1999. The purpose of this TIP is to assist you in supporting MICS 4.0 PRI.
MICS 4.0 was released with version 4.5 in the U.S. and version 4.8 in Canada. Since it's introduction, Nortel has been made aware of 3 different call scenarios that can cause the PRI channels to lockout preventing callers from making calls.
Two of the 3 call scenarios have been corrected in version (working issue) 5.01. MICS 4.0 WI 5.01 was put into manufacturing March 19, 1999. The following is a description of the 2 call scenarios that have been corrected.
PRI Scenario 1
As PRI calls are made, the KSU loses count of the number of calls up and ends up blocking calls when it shouldn't. The Norstar user sees "Not in service" on some or all outgoing call attempts. Some or all incoming calls also fail. When this condition occurs, Usage Metrics/Cbc Metrics show high call blocking counts. The PRI channels can be cleared by cycling the power to the KSU.
PRI Scenario 2
As outgoing PRI calls are made, the KSU loses track of the original B-channel in cases where the network (central office) negotiates a new B-channel for the call. The Norstar user sees "Line xxx busy" on some outgoing call attempts, "Not in service" on others. Incoming calls are not affected. The line number in "Line xxx busy" increases over time as B-channels are lost. When this condition occurs Maintenance/Link Status shows most or all of the B-channels in a 'busy' state. The PRI channels can be cleared by cycling the power to the KSU.
If you currently have MICS 4.0 WI 4.5 or 4.8 installed with PRI activated, it is recommended that you upgrade to MICS 4.0 WI 5.01. You can obtain MICS 4.0 WI 5.01 to correct these 2 call scenarios by calling the Nortel Repair Center at the following number:
USA 1-800-251-1758
Canada 1-888-977-9444
It will be necessary to have a valid P.O. number when calling into the Repair Center, however, MICS 4.0 WI 5.01 will be provided free of charge providing the old cartridge is returned within 30 days. The ordering numbers are as follows:
A0734006 - USA MICS XC 4.0
A0734004 - CDA MICS XC 4.0
A0734007 - NA MICS 4.0
PRI Scenario 3
Due to a change in end-user dialing habits, we have encountered a third call scenario that causes PRI channels to be locked out preventing outgoing calls.
This situation occurs when an end-user accesses an intercom key and either dials a number, uses an autodial key, or uses speed dial to dial a number. Before the call goes through, or if a busy signal is encountered, the user immediately accesses another intercom key and dials a number. The key to this call scenario is that the user does not press the Rls key before accessing the second intercom key. Under this call scenario the PRI channel will be locked out. To prevent the PRI channels from becoming locked out, the user should press the Rls key on the first call prior to accessing the second intercom key. In the event that the PRI channels are locked out, they can be cleared by cycling the power to the KSU.
Although this call scenario has not yet been corrected, Nortel is diligently working to provide a fix as well as scoping the implementation of a routine where the software will tear down invalid PRI calls thus preventing any future call scenarios causing channel lock up. It is expected that this software will be available within 4-6 weeks.
MICS 4.0 WI 5.01 also provides the following performance adjustments.
Selective Line Redirection (SLR)
This situation affected configurations that have analog DID and are using SLR to redirect incoming DID calls to another outside number. When SLR was activated, the first call to the DID line would be redirected but all subsequent calls would continue to ring at the Norstar set. With WI 5.01, all subsequent calls are also redirected.
DID Template
When the DID template was chosen on new MICS 4.0 installs, the target lines would not be assigned to the Norstar telephone sets. The work around for this was to manually program the target lines to the sets. With 5.01 the target lines are assigned to the sets.
AND
MICS 4.0 WI 5.05 ITAS SRN-016 June 1999
MICS 4.0 is Norstar's newest addition to the product portfolio and it's major feature enhancement is PRI connectivity. MICS 4.0 was released to the market place January 25, 1999. MICS 4.0 was released with version 4.5 in the U.S. and version 4.8 in Canada. In March 1999, MICS 4.0 WI 5.01 was released to address two PRI call handling scenarios (see SRN 012 April 5, 1999).
The purpose of this SRN is to notify you that MICS 4.0 WI 5.05 will be released July 5, 1999. This SRN will describe the performance enhancements in WI 5.05 over WI 5.01 and the process for replacement for those customer sites exhibiting any of the following conditions.
PRI Scenario 3
Due to a change in end-user dialing habits, we encountered a third call scenario that causes PRI channels to be locked out preventing outgoing calls. MICS 4.0 WI 5.05 addresses this scenario and is described as follows.
This situation occurs when an end-user accesses an intercom key and either dials a number, uses an autodial key, or uses speed dial to dial a number. Before the call goes through, or if a busy signal is encountered, the user immediately accesses another intercom key and dials a number. The key to this call scenario is that the user does not press the Rls key before accessing the second intercom key. Under this call scenario the PRI channel will be locked out. To prevent the PRI channels from becoming locked out, the user should press the Rls key on the first call prior to accessing the second intercom key. In the event that the PRI channels are locked out, they can be cleared by cycling the power to the KSU.
This has been addressed in MICS 4.0 WI 5.05.
DID Template Assignment
When a new system is installed, there is the capability to choose the type of template the Norstar system will use. The purpose of the template is to assign lines based on the configuration the customer requires.
One of the templates that can be chosen is DID. When the DID template is chosen, target lines are assigned sequentially to all Norstar sets. In a low number of occurrences with MICS 4.0 pre WI 5.05, either no lines or the incorrect target lines were assigned when the DID template was chosen.
This has been addressed in MICS 4.0 WI 5.05.
System Reset with Background Music
This was a very low occurrence condition that was caused by an interaction with Background Music (Feature 86).
This condition occurred when the dialing pattern described in PRI Scenario 3 above was used while Background Music was active. When a user accessed an intercom key to dial out and then jumped to another intercom key to make a call, while Background Music was activated, a timer within the KSU would expire would expire causing the KSU to reset. The KSU reset can be prevented by ensuring that a user presses the Release key on the original call prior to accessing the second intercom key.
This has been addressed in MICS 4.0 WI 5.05.
Service Modes Target Line Ringing
Service Modes provides the capability to extend the ringing of incoming lines to additional phones that would not normally ring when Service Modes are not activated. The Service Mode specifically that allows this is called Ringing Service.
When Ringing Service in MICS 4.0 pre WI 5.05 was activated, the target lines would not ring at the programmed ringing sets or, if assigned to be answered by voicemail, the target lines would end up being answered by the General Delivery mailbox.
This has been addressed in MICS 4.0 WI 5.05.
KSU Reset with NRU
This was a low occurrence condition that caused the KSU to reset after an NRU session. After an NRU session where the Line Assignment programming was accessed, the KSU would reset once the NRU session ended.
This has been addressed in MICS 4.0 WI 5.05.
COMPANION Portables and Paging
This was a very rare occurrence condition where the conversation of a C3050 portable user would be heard by Norstar desk set users, after the C3050 user activated paging. For this to occur, there needed to be a very high number of pages and a very high number of incoming calls occurring at the same time.
This has been addressed in MICS 4.0 WI 5.05.
4.1 issues
MICS 4.1 WI 6.04 ITAS SRN-019 February 2000
Norstar MICS 4.1 was released to the market on September 15, 1999 and introduced new call processing features such as External Call Forward, as well as support for the Norstar Data Interface. In September, MICS 4.1 released at working issue (WI) 6.00.
MICS 4.1 WI 6.04 is a maintenance release to resolve issues encountered in MICS 4.1 WI 6.00. It was made available to the general market place February 21, 2000. A replacement process is in place and is described below.
This SRN will describe the performance changes made in MICS 4.1 WI 6.04
Overriding Call Forward feature not working
The Overriding Call Forward feature allows a forwarded set to receive calls ONLY from the set it was forwarded to.
An example of the problemdescription is as follows:
- set A forwards to set B
- set B tries to call set A
- set A gets one ring only
- set B gets a ‘Not in Service’ message
This has been addressed in MICS 4.1 WI 6.04
Intermittent ‘Not in Service’ & Calls Being Dropped
The symptoms encountered are as follows. Users would see a " Not In Service" message when trying to transfer (F70), Voice Call (F66), direct station to station, Voice Mail transfers (F986) and Call Park (F74). The ‘Not in Service’ message was seen on originating sets only. Another manifestation could be users experiencing dropped internal and external calls.
This has been addressed in MICS 4.1 WI 6.04
Loss of soft key use on C3050 when a call is FWD to VM DN
A wireless set (C3050) calls a wired set XXX. Wired set XXX is Call Forward All Calls (F4) to Voice Mail DN. The wireless set hears the mailbox greeting and prompts user to leave a message. The wireless set user records a message and uses the soft keys on the C3050 to end and send the message. The soft key fails to work. Message was successfully sent when the DTMF dial pad was used (# to end the message recording and another # to send it)
This has been addressed in MICS 4.1 WI 6.04
MICS4.0 one way speech path on redirected target lines
A target line call ringing at a set that has been re-directed (F84) or externally call forwarded (F4) will experience a one-way speech path (calling party hears but can’t be heard)
This has been addressed in MICS 4.1 WI 6.04
Replacement Process (Marketing Communiqué 213)
If a customer’s MICS 4.1 order was fulfilled with MICS 4.0 during the Stop Ship, and they require the MICS 4.1 features listed below; please follow the RMA procedure below.
Note: MICS 4.0 software does not have the condition identified in MICS 4.1.
Norstar MICS 4.1 software offers the following feature enhancements over MICS 4.0 software:
Ø Norstar Data Interface Support
• DS-30 to synchronous serial connection support into any Nortel Networks or 3rd Party Data Terminal Equipment
Ø External Call Forward
• Call Forward Busy
• Call Forward No Answer
• Call Forward All Calls
Ø Outgoing Name and Number Blocking
Vertical Service Code and Suppression Bit Central Office Support
RMA Procedure: (If a customer’s MICS 4.1 order was fulfilled with MICS 4.0 during the Stop Ship, and they require the MICS 4.1)
and
MICS 4.1 WI 6.15 ITAS SRN-020 October 2000
Norstar MICS 4.1 was released to the market on September 15, 1999 and introduced new call processing features such as External Call Forward, as well as support for the Norstar Data Interface. In September, 1999 MICS 4.1 released at working issue (WI) 6.00. MICS 4.1 was up-issued to WI 6.04 in February of 2000.
MICS 4.1 WI 6.15 is a maintenance release that provides performance enhancements over MICS 4.1 WI 6.04. It was made available to the general market place December 04, 2000.
A replacement process is in place and is described below
This SRN will describe the performance enhancements made in MICS 4.1 WI 6.13
ANI digits not delivered to Voice Mail
Whenever an incoming PRI call on a Norstar is forwarded (CFAC/CFB) to Voice Mail (NAM only), the VM would not receive the ANI digits as delivered by the C.O. This situation occurs due to the fact the call was answered immediately by the user or the application. When a user retrieved messages from the voice mail, he was not presented with the calling number. If the customer was using either VM or ACD reports the ANI information would be missed.
This has been addressed in MICS 4.1 WI 6.13
Event 135 system reset
Intermittently EVT 135 occurs 100 or more times in the system EVT logs, when followed by EVT 285 the system resets.
This has been addressed in MICS 4.1 WI 6.13
Feature 901/902 transient feature inactive message
Minuet ACD has been upgraded to support the ability for Companion users to work as agents on the system. When Feature 901/902 (Available/Unavailable) feature is invoked from the Companion portable, there is a transient 'Inactive feature' message observed by the user.
This has been addressed in MICS 4.1 WI 6.13
Call alerting failure and intermittent call drop
When using Revision 1 C3050 portables users were reporting a failure of alerting (ringing or vibrating) to the portable as well as intermittently calls would drop.
This has been addressed in MICS 4.1 WI 6.13
After upgrading from MICS 4.0 to MICS 4.1 WI 6.04 PRI fails
After an upgrade from MICS 4.0 to MICS 4.1 WI 6.04 the PRI loop fails to come up. Customer can neither make or receive calls.
The problem is only confined to the Norstar behind M1 over PRI SL-1 link and will not affect Norstar systems connected via PRI loop to central offices directly.
This has been addressed in MICS 4.1 WI 6.13
Transferred calls to Hunt groups ring with incorrect ring cadence
Calls transferred to Hunt groups in the Norstar system ring with external ring cadence rather than internal.
This has been addressed in MICS 4.1 WI 6.13
False busy on DSS key for Companion extensions
After inbound calls to a set in the system are transferred to a Companion set and the call is terminated the DSS key for the Companion extension shows the portable busy.
This has been addressed in MICS 4.1 WI 6.13
Unable to program buttons for unconnected sets
A condition existed whereby users were unable to program the button programming on sets that were not physically connected to Station Modules. This situation occurred whether the user was programming using Norstar Remote Utilities (NRU) or when programming in a **Config session.
This has been addressed in MICS 4.1 WI 6.15
Message Waiting Indication
MICS 4.1 WI 6.15 has added functionality for Message Waiting Indication (MWI) when using the new Business Series Terminals (BST). More information about the BST sets, including ordering information, can be found in ITAS TIP 255 on the ITAS web page.
MICS 4.0 WI 5.01
ITAS SRN-012 April 5, 1999
UPDATE 6/16/99 Scenario #3 is corrected in MICS 4.0 WI 5.05 see SRN-016
MICS 4.0 is Norstar's newest addition to the product portfolio and it's major feature enhancement is PRI connectivity. MICS 4.0 was released to the market place January 25, 1999. The purpose of this TIP is to assist you in supporting MICS 4.0 PRI.
MICS 4.0 was released with version 4.5 in the U.S. and version 4.8 in Canada. Since it's introduction, Nortel has been made aware of 3 different call scenarios that can cause the PRI channels to lockout preventing callers from making calls.
Two of the 3 call scenarios have been corrected in version (working issue) 5.01. MICS 4.0 WI 5.01 was put into manufacturing March 19, 1999. The following is a description of the 2 call scenarios that have been corrected.
PRI Scenario 1
As PRI calls are made, the KSU loses count of the number of calls up and ends up blocking calls when it shouldn't. The Norstar user sees "Not in service" on some or all outgoing call attempts. Some or all incoming calls also fail. When this condition occurs, Usage Metrics/Cbc Metrics show high call blocking counts. The PRI channels can be cleared by cycling the power to the KSU.
PRI Scenario 2
As outgoing PRI calls are made, the KSU loses track of the original B-channel in cases where the network (central office) negotiates a new B-channel for the call. The Norstar user sees "Line xxx busy" on some outgoing call attempts, "Not in service" on others. Incoming calls are not affected. The line number in "Line xxx busy" increases over time as B-channels are lost. When this condition occurs Maintenance/Link Status shows most or all of the B-channels in a 'busy' state. The PRI channels can be cleared by cycling the power to the KSU.
If you currently have MICS 4.0 WI 4.5 or 4.8 installed with PRI activated, it is recommended that you upgrade to MICS 4.0 WI 5.01. You can obtain MICS 4.0 WI 5.01 to correct these 2 call scenarios by calling the Nortel Repair Center at the following number:
USA 1-800-251-1758
Canada 1-888-977-9444
It will be necessary to have a valid P.O. number when calling into the Repair Center, however, MICS 4.0 WI 5.01 will be provided free of charge providing the old cartridge is returned within 30 days. The ordering numbers are as follows:
A0734006 - USA MICS XC 4.0
A0734004 - CDA MICS XC 4.0
A0734007 - NA MICS 4.0
PRI Scenario 3
Due to a change in end-user dialing habits, we have encountered a third call scenario that causes PRI channels to be locked out preventing outgoing calls.
This situation occurs when an end-user accesses an intercom key and either dials a number, uses an autodial key, or uses speed dial to dial a number. Before the call goes through, or if a busy signal is encountered, the user immediately accesses another intercom key and dials a number. The key to this call scenario is that the user does not press the Rls key before accessing the second intercom key. Under this call scenario the PRI channel will be locked out. To prevent the PRI channels from becoming locked out, the user should press the Rls key on the first call prior to accessing the second intercom key. In the event that the PRI channels are locked out, they can be cleared by cycling the power to the KSU.
Although this call scenario has not yet been corrected, Nortel is diligently working to provide a fix as well as scoping the implementation of a routine where the software will tear down invalid PRI calls thus preventing any future call scenarios causing channel lock up. It is expected that this software will be available within 4-6 weeks.
MICS 4.0 WI 5.01 also provides the following performance adjustments.
Selective Line Redirection (SLR)
This situation affected configurations that have analog DID and are using SLR to redirect incoming DID calls to another outside number. When SLR was activated, the first call to the DID line would be redirected but all subsequent calls would continue to ring at the Norstar set. With WI 5.01, all subsequent calls are also redirected.
DID Template
When the DID template was chosen on new MICS 4.0 installs, the target lines would not be assigned to the Norstar telephone sets. The work around for this was to manually program the target lines to the sets. With 5.01 the target lines are assigned to the sets.
AND
MICS 4.0 WI 5.05 ITAS SRN-016 June 1999
MICS 4.0 is Norstar's newest addition to the product portfolio and it's major feature enhancement is PRI connectivity. MICS 4.0 was released to the market place January 25, 1999. MICS 4.0 was released with version 4.5 in the U.S. and version 4.8 in Canada. In March 1999, MICS 4.0 WI 5.01 was released to address two PRI call handling scenarios (see SRN 012 April 5, 1999).
The purpose of this SRN is to notify you that MICS 4.0 WI 5.05 will be released July 5, 1999. This SRN will describe the performance enhancements in WI 5.05 over WI 5.01 and the process for replacement for those customer sites exhibiting any of the following conditions.
PRI Scenario 3
Due to a change in end-user dialing habits, we encountered a third call scenario that causes PRI channels to be locked out preventing outgoing calls. MICS 4.0 WI 5.05 addresses this scenario and is described as follows.
This situation occurs when an end-user accesses an intercom key and either dials a number, uses an autodial key, or uses speed dial to dial a number. Before the call goes through, or if a busy signal is encountered, the user immediately accesses another intercom key and dials a number. The key to this call scenario is that the user does not press the Rls key before accessing the second intercom key. Under this call scenario the PRI channel will be locked out. To prevent the PRI channels from becoming locked out, the user should press the Rls key on the first call prior to accessing the second intercom key. In the event that the PRI channels are locked out, they can be cleared by cycling the power to the KSU.
This has been addressed in MICS 4.0 WI 5.05.
DID Template Assignment
When a new system is installed, there is the capability to choose the type of template the Norstar system will use. The purpose of the template is to assign lines based on the configuration the customer requires.
One of the templates that can be chosen is DID. When the DID template is chosen, target lines are assigned sequentially to all Norstar sets. In a low number of occurrences with MICS 4.0 pre WI 5.05, either no lines or the incorrect target lines were assigned when the DID template was chosen.
This has been addressed in MICS 4.0 WI 5.05.
System Reset with Background Music
This was a very low occurrence condition that was caused by an interaction with Background Music (Feature 86).
This condition occurred when the dialing pattern described in PRI Scenario 3 above was used while Background Music was active. When a user accessed an intercom key to dial out and then jumped to another intercom key to make a call, while Background Music was activated, a timer within the KSU would expire would expire causing the KSU to reset. The KSU reset can be prevented by ensuring that a user presses the Release key on the original call prior to accessing the second intercom key.
This has been addressed in MICS 4.0 WI 5.05.
Service Modes Target Line Ringing
Service Modes provides the capability to extend the ringing of incoming lines to additional phones that would not normally ring when Service Modes are not activated. The Service Mode specifically that allows this is called Ringing Service.
When Ringing Service in MICS 4.0 pre WI 5.05 was activated, the target lines would not ring at the programmed ringing sets or, if assigned to be answered by voicemail, the target lines would end up being answered by the General Delivery mailbox.
This has been addressed in MICS 4.0 WI 5.05.
KSU Reset with NRU
This was a low occurrence condition that caused the KSU to reset after an NRU session. After an NRU session where the Line Assignment programming was accessed, the KSU would reset once the NRU session ended.
This has been addressed in MICS 4.0 WI 5.05.
COMPANION Portables and Paging
This was a very rare occurrence condition where the conversation of a C3050 portable user would be heard by Norstar desk set users, after the C3050 user activated paging. For this to occur, there needed to be a very high number of pages and a very high number of incoming calls occurring at the same time.
This has been addressed in MICS 4.0 WI 5.05.
4.1 issues
MICS 4.1 WI 6.04 ITAS SRN-019 February 2000
Norstar MICS 4.1 was released to the market on September 15, 1999 and introduced new call processing features such as External Call Forward, as well as support for the Norstar Data Interface. In September, MICS 4.1 released at working issue (WI) 6.00.
MICS 4.1 WI 6.04 is a maintenance release to resolve issues encountered in MICS 4.1 WI 6.00. It was made available to the general market place February 21, 2000. A replacement process is in place and is described below.
This SRN will describe the performance changes made in MICS 4.1 WI 6.04
Overriding Call Forward feature not working
The Overriding Call Forward feature allows a forwarded set to receive calls ONLY from the set it was forwarded to.
An example of the problemdescription is as follows:
- set A forwards to set B
- set B tries to call set A
- set A gets one ring only
- set B gets a ‘Not in Service’ message
This has been addressed in MICS 4.1 WI 6.04
Intermittent ‘Not in Service’ & Calls Being Dropped
The symptoms encountered are as follows. Users would see a " Not In Service" message when trying to transfer (F70), Voice Call (F66), direct station to station, Voice Mail transfers (F986) and Call Park (F74). The ‘Not in Service’ message was seen on originating sets only. Another manifestation could be users experiencing dropped internal and external calls.
This has been addressed in MICS 4.1 WI 6.04
Loss of soft key use on C3050 when a call is FWD to VM DN
A wireless set (C3050) calls a wired set XXX. Wired set XXX is Call Forward All Calls (F4) to Voice Mail DN. The wireless set hears the mailbox greeting and prompts user to leave a message. The wireless set user records a message and uses the soft keys on the C3050 to end and send the message. The soft key fails to work. Message was successfully sent when the DTMF dial pad was used (# to end the message recording and another # to send it)
This has been addressed in MICS 4.1 WI 6.04
MICS4.0 one way speech path on redirected target lines
A target line call ringing at a set that has been re-directed (F84) or externally call forwarded (F4) will experience a one-way speech path (calling party hears but can’t be heard)
This has been addressed in MICS 4.1 WI 6.04
Replacement Process (Marketing Communiqué 213)
If a customer’s MICS 4.1 order was fulfilled with MICS 4.0 during the Stop Ship, and they require the MICS 4.1 features listed below; please follow the RMA procedure below.
Note: MICS 4.0 software does not have the condition identified in MICS 4.1.
Norstar MICS 4.1 software offers the following feature enhancements over MICS 4.0 software:
Ø Norstar Data Interface Support
• DS-30 to synchronous serial connection support into any Nortel Networks or 3rd Party Data Terminal Equipment
Ø External Call Forward
• Call Forward Busy
• Call Forward No Answer
• Call Forward All Calls
Ø Outgoing Name and Number Blocking
Vertical Service Code and Suppression Bit Central Office Support
RMA Procedure: (If a customer’s MICS 4.1 order was fulfilled with MICS 4.0 during the Stop Ship, and they require the MICS 4.1)
and
MICS 4.1 WI 6.15 ITAS SRN-020 October 2000
Norstar MICS 4.1 was released to the market on September 15, 1999 and introduced new call processing features such as External Call Forward, as well as support for the Norstar Data Interface. In September, 1999 MICS 4.1 released at working issue (WI) 6.00. MICS 4.1 was up-issued to WI 6.04 in February of 2000.
MICS 4.1 WI 6.15 is a maintenance release that provides performance enhancements over MICS 4.1 WI 6.04. It was made available to the general market place December 04, 2000.
A replacement process is in place and is described below
This SRN will describe the performance enhancements made in MICS 4.1 WI 6.13
ANI digits not delivered to Voice Mail
Whenever an incoming PRI call on a Norstar is forwarded (CFAC/CFB) to Voice Mail (NAM only), the VM would not receive the ANI digits as delivered by the C.O. This situation occurs due to the fact the call was answered immediately by the user or the application. When a user retrieved messages from the voice mail, he was not presented with the calling number. If the customer was using either VM or ACD reports the ANI information would be missed.
This has been addressed in MICS 4.1 WI 6.13
Event 135 system reset
Intermittently EVT 135 occurs 100 or more times in the system EVT logs, when followed by EVT 285 the system resets.
This has been addressed in MICS 4.1 WI 6.13
Feature 901/902 transient feature inactive message
Minuet ACD has been upgraded to support the ability for Companion users to work as agents on the system. When Feature 901/902 (Available/Unavailable) feature is invoked from the Companion portable, there is a transient 'Inactive feature' message observed by the user.
This has been addressed in MICS 4.1 WI 6.13
Call alerting failure and intermittent call drop
When using Revision 1 C3050 portables users were reporting a failure of alerting (ringing or vibrating) to the portable as well as intermittently calls would drop.
This has been addressed in MICS 4.1 WI 6.13
After upgrading from MICS 4.0 to MICS 4.1 WI 6.04 PRI fails
After an upgrade from MICS 4.0 to MICS 4.1 WI 6.04 the PRI loop fails to come up. Customer can neither make or receive calls.
The problem is only confined to the Norstar behind M1 over PRI SL-1 link and will not affect Norstar systems connected via PRI loop to central offices directly.
This has been addressed in MICS 4.1 WI 6.13
Transferred calls to Hunt groups ring with incorrect ring cadence
Calls transferred to Hunt groups in the Norstar system ring with external ring cadence rather than internal.
This has been addressed in MICS 4.1 WI 6.13
False busy on DSS key for Companion extensions
After inbound calls to a set in the system are transferred to a Companion set and the call is terminated the DSS key for the Companion extension shows the portable busy.
This has been addressed in MICS 4.1 WI 6.13
Unable to program buttons for unconnected sets
A condition existed whereby users were unable to program the button programming on sets that were not physically connected to Station Modules. This situation occurred whether the user was programming using Norstar Remote Utilities (NRU) or when programming in a **Config session.
This has been addressed in MICS 4.1 WI 6.15
Message Waiting Indication
MICS 4.1 WI 6.15 has added functionality for Message Waiting Indication (MWI) when using the new Business Series Terminals (BST). More information about the BST sets, including ordering information, can be found in ITAS TIP 255 on the ITAS web page.
ALL USA MICS with PRI should be upgraded to rls 6.1 or higher and the old NVRAM pack should be replaced also!
If any of you have any MICS ksu's in the field with PRI and software older than 6.1, you're doing your customers wrong by not recommending an upgrade and by not letting them know about the known PRI software related issues with the older software. Even if the system is working great, you still need to advise your customers that Nortel says to do an upgrade!
If the customer chooses to ignore your excellent advice, at least no one can ever come back to you and say you didn't know what you were doing or "Why didn't you recommend an upgrade to correct these known issues three years ago instead of making us spend a fortune on service calls?"
Cover your asses ladies and gentlemen before they try to pin all of their problems on YOU!
Phonehed in Dallas
If any of you have any MICS ksu's in the field with PRI and software older than 6.1, you're doing your customers wrong by not recommending an upgrade and by not letting them know about the known PRI software related issues with the older software. Even if the system is working great, you still need to advise your customers that Nortel says to do an upgrade!
If the customer chooses to ignore your excellent advice, at least no one can ever come back to you and say you didn't know what you were doing or "Why didn't you recommend an upgrade to correct these known issues three years ago instead of making us spend a fortune on service calls?"
Cover your asses ladies and gentlemen before they try to pin all of their problems on YOU!
Phonehed in Dallas
lugerlover
Programmer
1.
MICS 5.0 WI 6.02
Norstar MICS 5.0 was released to the US market on June 1, 2001 and introduced new call processing features such as MCDN call handling features and Centralized Voice Mail (CVM).
MICS 5.0 WI 6.02 is a maintenance release that provides performance enhancements over MICS 5.0 WI 6.00. It was made available to the general market place June 29, 2001.
A replacement process is in place and is described below.
This SRN will describe the performance enhancements made in MICS 5.0 WI 6.02
Enhancements made over MICS 5.0 WI 6.00
No Ringback tone on inbound calls
Customers calling into the Norstar system from the public network on PRI trunks will not get ringback tone from the Norstar. Those installs using the private networking or MCDN functionality will not be affected. The lack of ringback tone will be encountered when using any of the following protocols:
· NI2
· DMS 100
· DMS 250
· 4ESS
Customer installations using PRI connections directly to the central office will be the only sites affected by this issue. For those sites utilizing PRI trunking in M1 private networked environments installations will be unaffected. Customers using analog only installations will also be unaffected.
This has been addressed in MICS 5.0 WI 6.02
Enhancements made over MICS 4.1.1 WI 6.15
PRI call failures with ISDN Progress message PI#3
When calls are made from a Norstar system to the C.O. using DMS 250 protocol the C.O. responds with a Progress message PI#3. Norstar did not interpret the location code #3 correctly which caused the call to fail. The DMS 250 protocol tables have been modified to accommodate this location code.
This has been addressed in MICS 5.0 WI 6.02
Companion C3060 active softkey failure
Companion users reported intermittent feature failures when using the active softkeys programmed on the C3060 portable handsets.
This has been addressed in MICS 5.0 WI 6.02
Hunt Group Overflow DN does not ring
In this scenario the Hunt Group DN is a transfer point from the Norstar Voice Mail Custom Call Routing menu. When a transfer is completed to the Hunt group and the hunt delay timer expires (i.e. no hunt group members answer the call) the overflow DN does not ring.
If the HG is dialed directly from intercom, it works correctly.
This has been addressed in MICS 5.0 WI 6.02
2.
MICS5.0 WI 6.06 and CICS 4.2 WI 6.06 ITAS SRN-023
January 18,2002
Norstar MICS 5.0 WI 6.00 was released to the US Market on June 1, 2001 and introduced the new call processing features to Norstar MCDN and CVM (Centralized Voice Mail).
CICS 4.2 WI 6.02 was released to the general market and introduced MWI to T series sets for CICS users
MICS 5.0 WI 6.02 was a maintenance release that provided performance enhancements to MICS 5.0 WI 6.00. It was made available to the general market June 29,2001.
MICS 5.0 WI 6.06 is a maintenance release that provides performance enhancements to MICS 5.0 WI 6.02. It was made available to the general market November 26, 2001.
CICS 4.2 WI 6.06 is a maintenance release that provides performance enhancements to CICS 4.2 WI 6.02 A replacement process is in place and described below.
This SRN will describe the performance enhancements made in MICS 5.0 WI 6.06 and CICS 4.2 WI 6.06
Enhancements made to MICS 5.0 WI 6.02 and CICS 4.2 WI 6.02
System Resets when using speed dials from Companion portable sets.
The system may reset when using speed dials from Companion portables.
This has been addressed in MICS 5.0 WI 6.06.
Analog lines on the core can become unusable
Core analog trunks can be unusable when the configuration setting for trunk mode is changed from unsupervised to supervised. The user will not be able to receive or make calls on the affected trunks.
This has been addressed in MICS 5.0 WI 6.06 and CICS 4.2 WI 6.06
ISDN calls being dropped
ISDN calls originating from or tandeming through a Norstar may be dropped. There are certain situations where network delays can exceed the T310 delay parameter configured on the Norstar. An example of this situation would be a Trans Atlantic call where the call, because of network traffic, is re routed from the under sea cable route to a satellite route. This rerouting causes a delay in call processing and therefore a call to drop.
This has been addressed in MICS 5.0 WI 6.06 and CICS 4.2 WI 6.06
Intermittent “not in service” error when calls are transferred to a hunt group
In a broadcast hunt group if one call is ringing in a hunt group then the second call will be forwarded to the Overflow set. If the overflow set transfers the call back to the hunt group the overflow set will get a “not in service” error message.
This has been addressed in MICS 5.0 WI 6.06 and CICS 4.2 WI 6.06
MICS 5.0 WI 6.02
Norstar MICS 5.0 was released to the US market on June 1, 2001 and introduced new call processing features such as MCDN call handling features and Centralized Voice Mail (CVM).
MICS 5.0 WI 6.02 is a maintenance release that provides performance enhancements over MICS 5.0 WI 6.00. It was made available to the general market place June 29, 2001.
A replacement process is in place and is described below.
This SRN will describe the performance enhancements made in MICS 5.0 WI 6.02
Enhancements made over MICS 5.0 WI 6.00
No Ringback tone on inbound calls
Customers calling into the Norstar system from the public network on PRI trunks will not get ringback tone from the Norstar. Those installs using the private networking or MCDN functionality will not be affected. The lack of ringback tone will be encountered when using any of the following protocols:
· NI2
· DMS 100
· DMS 250
· 4ESS
Customer installations using PRI connections directly to the central office will be the only sites affected by this issue. For those sites utilizing PRI trunking in M1 private networked environments installations will be unaffected. Customers using analog only installations will also be unaffected.
This has been addressed in MICS 5.0 WI 6.02
Enhancements made over MICS 4.1.1 WI 6.15
PRI call failures with ISDN Progress message PI#3
When calls are made from a Norstar system to the C.O. using DMS 250 protocol the C.O. responds with a Progress message PI#3. Norstar did not interpret the location code #3 correctly which caused the call to fail. The DMS 250 protocol tables have been modified to accommodate this location code.
This has been addressed in MICS 5.0 WI 6.02
Companion C3060 active softkey failure
Companion users reported intermittent feature failures when using the active softkeys programmed on the C3060 portable handsets.
This has been addressed in MICS 5.0 WI 6.02
Hunt Group Overflow DN does not ring
In this scenario the Hunt Group DN is a transfer point from the Norstar Voice Mail Custom Call Routing menu. When a transfer is completed to the Hunt group and the hunt delay timer expires (i.e. no hunt group members answer the call) the overflow DN does not ring.
If the HG is dialed directly from intercom, it works correctly.
This has been addressed in MICS 5.0 WI 6.02
2.
MICS5.0 WI 6.06 and CICS 4.2 WI 6.06 ITAS SRN-023
January 18,2002
Norstar MICS 5.0 WI 6.00 was released to the US Market on June 1, 2001 and introduced the new call processing features to Norstar MCDN and CVM (Centralized Voice Mail).
CICS 4.2 WI 6.02 was released to the general market and introduced MWI to T series sets for CICS users
MICS 5.0 WI 6.02 was a maintenance release that provided performance enhancements to MICS 5.0 WI 6.00. It was made available to the general market June 29,2001.
MICS 5.0 WI 6.06 is a maintenance release that provides performance enhancements to MICS 5.0 WI 6.02. It was made available to the general market November 26, 2001.
CICS 4.2 WI 6.06 is a maintenance release that provides performance enhancements to CICS 4.2 WI 6.02 A replacement process is in place and described below.
This SRN will describe the performance enhancements made in MICS 5.0 WI 6.06 and CICS 4.2 WI 6.06
Enhancements made to MICS 5.0 WI 6.02 and CICS 4.2 WI 6.02
System Resets when using speed dials from Companion portable sets.
The system may reset when using speed dials from Companion portables.
This has been addressed in MICS 5.0 WI 6.06.
Analog lines on the core can become unusable
Core analog trunks can be unusable when the configuration setting for trunk mode is changed from unsupervised to supervised. The user will not be able to receive or make calls on the affected trunks.
This has been addressed in MICS 5.0 WI 6.06 and CICS 4.2 WI 6.06
ISDN calls being dropped
ISDN calls originating from or tandeming through a Norstar may be dropped. There are certain situations where network delays can exceed the T310 delay parameter configured on the Norstar. An example of this situation would be a Trans Atlantic call where the call, because of network traffic, is re routed from the under sea cable route to a satellite route. This rerouting causes a delay in call processing and therefore a call to drop.
This has been addressed in MICS 5.0 WI 6.06 and CICS 4.2 WI 6.06
Intermittent “not in service” error when calls are transferred to a hunt group
In a broadcast hunt group if one call is ringing in a hunt group then the second call will be forwarded to the Overflow set. If the overflow set transfers the call back to the hunt group the overflow set will get a “not in service” error message.
This has been addressed in MICS 5.0 WI 6.06 and CICS 4.2 WI 6.06
- Status
Similar threads
- Locked
- Question
- Locked
- Question