|
Welcome,
|
Technology Briefs - Tips and Tricks
2. Configuring the OME6500 to accept external alarms using the SONET/SDH-J access panel The OME6500 allows input telemetry pins on the SONET/SDH-J access panel to be used in conjunction with Normally Open (NO) relays to raise alarms from external environmental sensors. Determining which telemetry pins to use isn't always straight forward. Here are some things to keep in mind when identifying the appropriate pins to use:
3. Prioritizing WLAN Client Traffic Using Wireless Multimedia Extension (WMM) WMM, or Wireless Multimedia Extension, is a subset of the 802.11e standard that provides Quality of Service (QoS) in Wireless LANs. Because wireless networks are a shared medium, similar to an Ethernet hub in a wired environment, WMM is critical for prioritizing time-sensitive applications such as Voice or Video over IP that may be running on a WLAN client device. WMM introduces traffic prioritization capabilities based on four Access Categories including Voice, Video, Best Effort, and Background. Packets with a higher priority have lower wait times before accessing the WLAN while lower priority packets wait longer but are expected to tolerate longer wait times. In order to take advantage of the benefits of WMM the AP, the Client, and the applications running on the Client must all support WMM. The Nortel Wireless Security Switch 2300 and APs support WMM. When enabled the AP advertises QoS capability in the Beacon frame. WLAN Clients that support WMM recognize that the network supports WMM and will include a 802.1D based QoS User Priority (UP) value between 0 and 7 in the 802.11 header when transmitting. WLAN clients, such as a PC laptop, that support both time and non-time sensitive applications determine the WMM QoS User Priority value based on the DiffServ Code Point (DSCP) of the packet that is set by the application. The first 3 bits of the DSCP are mapped to the User Priority value. The User Priority then maps to a WMM Access Category (AC) to determine how it is dequeued onto the wireless medium. The following mapping table is from the 802.11e specification:  When a Nortel 233x AP receives a packet with a QoS User Priority Value it will mark the DSCP of the IP header that encapsulates the original packet before forwarding it to the WSS. The value of the DSCP is based on the configurable CoS to DSCP mapping table on the WSS. 4. CS1000 R5.5 MobileX An integral component of Nortel's Fixed Mobile Convergence strategy, CS1000 R5.5 introduces Mobile Extensions, or MobileX. MobileX extends enterprise voice services to the mobile user, allowing access to the enterprise dial plan from an authorized remote device, typically a cell phone. CS1000 enterprise services are extended to the mobile user by the introduction of a new TN type, the Universal Extension (UEXT). Several capabilities are introduced, including extending calls to, and remote access from, the mobile device and a "hand-off" feature, facilitating the transfer of calls from/to the enterprise phone to/from the cellular phone. Though not required, the mobile user is typically "partnered" with a fixed device, such as an IP set, 2050 softphone or TDM phone. In a similar fashion to a Personal Call Assistant (PCA), the UEXT provides the mechanism for extending calls to the mobile device. When a call terminates on an enterprise DN associated with a UEXT, the call is extended to the cellular device (key 1 hot p). Furthermore, the CS1000 enterprise dial plan may be accessed by the mobile user by first dialing a Mobile Service Access DN (MSA). Once dialed, and prompted with dial tone, the mobile user has access to the enterprise dial plan (security code prompt optional). Remote access of the system via MSA is controlled by the UXID, provisioned on the Universal Extension TN (UEXT). The Universal Extension ID (UXID) specifies the mobile user's cellular number and is used for verification against the Caller ID of the incoming call. Once a call is established, the MobileX user also has access to transfer and conferencing services, invoked by Flexible Feature Codes (FFC). MobileX is enabled by provisioning a UEXT TN and associating it with an enterprise DN (associated hard/soft phone is optional). An example of a UEXT is as follows: type=uext uxty=mobx uxid=9782885555 scpw=1234 key 0 scr 5321 key 1 hot p 12 919782885555 The UXID provides the means for Calling Line ID (CLID) verification when accessing the system via the MSA. The "key 1hot p" provides the means for extending the call to the mobile device similar to a PCA. Also, if the mobile user has an associated phone, a new key type, the "hand-off" key, may be provisioned on the enterprise phone in order to facilitate call transfers (e.g., key 5 HNDO). Once a call is established using the enterprise phone, the "hand-off" key can initiate a transfer to the mobile device. Likewise, the "hand-off" key may be used to seize back control of the call from the mobile device. In this case, the user is prompted for a password (SCPW provisioned on UEXT). 5. CS1K FAXS (PKG-195) Allows the passing of in-band Dual Tone Multi-Frequency (DTMF) digits to an external device after answer, these digits can represent the originally dialed number (DNIS) of the call or different digits based on the programming. The FAXS feature is designed to be used with a FAX server, but a more common application is out-pulsing DTMF to an IVR system. A traditional fax server can be a simple PC or server with one or more Fax compliant modems or intelligent fax boards installed which is connected to one or more analogue extensions on the PABX. Fax servers may be stand alone servers or servers for other applications running a Fax server application. Call Routing for FAXS The CS1k may use the following methods to allow calls to be routed to the FAXS line.
Phantom TN Phantoms allow for a Default Call Forward DN to the FAXS DN. Additionally a Call Forward DN can be specified for the Phantom. Night Call Forwarded Dummy ACD DN Uses more system resources, but can provide some reporting via ACD. This method is not recommended for a large number of dialed numbers to be redirected. HUNT on Busy, Call Forward no Answer, Call Forward All Calls. Either or both of these allow redirects to FAXS port. Figure 1: Call Routing and System Configuration  Analog Line FAXS Configuration (LD 10 or 20) A string of DNIS, CLI, control digits, and timing values may be constructed using the FAXS. FTR FAXS x....x where x....x may be similar to the following; W6 O1234 C#10* D C## W4 Where; W is a waiting time 0 to 9 seconds Oxxx is the originating or designated fax DN - (letter O not zero) C is control digits including * and # as required D is the called fax DN Refer to figure 1, if an external call to via Phantom DN 1000 to the faxs port, the line will see the following string of DTMF information upon answer [wait 6s]1234#10*1000##[wait 4s] If the call came from internal DN 3641 the output string would be [6s]3641#10*399##[4s] Where Internal CLI is available, CLI can be passed in the DTMF stream. CLI replaces the Oxxx value. Calls from trunks defined as external do not pass CLI information to the fax server even if CLI is provided. Simplest configuration FTR FAXS D Which out-pulses 1000 CLS and FTR Requirements DTN, FND, CWD, FBD, CFTD, AGTD, FAXS, NO CFW, NO ACD. 6. Nortel Application Switch (NAS) - Downgrading "E" models to pre 22.0.8 code is dangerous Recently a customer had asked if it was possible to use 22.0.2 code on their newly acquired 3408E Nortel Application Switches. Due to standardization requirements within their organization it is not acceptable for them to change code versions without prior approval for a new release. CSE tested this capability used a 2424E NAS running 23.2.2, and downgraded it to 22.0.2 code. The result was a boot loop which started with this error: ERROR: Unknown model number EB1412028 ERROR: invalid image loaded. This image cannot run on this type of Hardware Forcing a reset - please press any key? To remedy this condition you will need to be locally connected to the console using HyperTerm (or equivalent). During the boot loop, keep hitting shift m" until you see a prompt like this: =>; then type "xmodem", then set your baud rate to 115.2K as indicated by the prompt, next, browse to select the source application image 23.x or 24.x file on the local PC. DO NOT POWER CYCLE DURING THE DOWNLOAD/ WRITING OF THE FILE TO FLASH. It will take about 10 minutes. If you are unsure that it is done, hit return, when the same (=>) prompt is returned back to you, type "reset", then change the baud rate back to 9.6K and you will see the normal boot process once again. 9. ERS5500 Virtual Link Aggregation Control Protocol (VLACP) The ERS5000 supports Virtual Link Aggregation Control Protocol, VLACP to provide improved link resiliency between switches. The ERS5500 uses a unique global VLACP Multicast MAC address.  The ERS5500 VLACP configuration screen is found in Java Device Manager under the MLT pull down tab. Command line equivalent commands to configure VLACP are: 5530(config)# vlacp enable 5530(config)# vlacp macaddress 0180.c200.000f The default ERS5500 VLACP Multicast MAC address should be changed from 01:80:c2:00:11:00 to a recommended MAC of 01:80:c2:00:00:0f on all switches. 11. ERS8600 link-flap-detect The ERS8600 supports link-flap-detect; however this feature is disabled by default in version 4.1.5.4. The ERS8600 may have this feature dynamically enabled without impacting the operation of the Ethernet Routing Switch. Java Device Manager or ERS8600 CLI commands that can be used to enable this feature to monitor link flapping on all ports.  config sys link-flap-detect interval 60 config sys link-flap-detect frequency 10 config sys link-flap-detect auto-port-down enable config sys link-flap-detect send-trap enable The configuration can be confirmed using JDM or CLI show command on the ERS8600. show sys link-flap-detect general-info Auto Port Down: enable Send Trap : enable Interval : 60 Frequency : 10 The frequency defines how often a port can go down, where the default is 10 (times). The default interval is 60 minutes; therefore the port will be disabled if the port goes down 10 times within 60 minutes. This feature will protect the network against link flapping on a port, which may cause undesired route or spanning tree recalculations. 12. ERS4500 with Bi-directional Transceiver (BX) Small Form-factor Pluggable (SFPs) The ERS4500 running software version 5.1.0 "unofficially" supports BX style SFPs operating at 1490nm and 1320nm. ERS4500 interoperate with a new BX style SFP which uses only one strand of fiber to transmit and receive 1 gigabit of traffic on two different wavelengths. This example has ERS4500_A port 48 equipped with 1490nm wavelength BX SFP connected to another ERS4500_B equipped with a 1310nm wavelength SFP on port 48. The ERS4500_A is equipped with a 1490nm BX SFP which represents Nortel part # AA1419070-E6. ERS4500_A#show interface gbic-info 48 GBIC Type BX10-D The ERS4500_B is equipped with a 1310nm BX SFP which represents Nortel part # AA1419069-E6. ERS4500_B#show interface gbic-info 48 GBIC Type BX10-U The BX SFPs will enable customers to virtually double their bandwidth capabilities using their existing multimode (or single-mode) fiber using two wavelengths (1490nm and 1310nm) to transmit and receive gigabit traffic over a single fiber. The test was conducted using multimode fiber (MMF). ERS4500 future software release will “officially” support BX style SFPs. The BX SFPs come in two versions that define the wavelength for TX and RX. 13. ERS8300 Advanced Filtering The ERS8300 supports advanced filtering introduced in version 4.1.0 software release in conjunction with 8394SF/CPU and newer I/O modules. The ERS8300 now has a boot flag that can be set to enable this advanced deep packet filtering; however this feature is not supported on the 8393SF/CPU cards. ERS8300_B:5(config)# boot config flag t-mode WARNING: The change made will take effect only after the configuration is saved and the chassis is rebooted. This feature is not applicable to 8393SF/CPU cards. All non T modules will be taken off-line if t-mode is enabled. ERS8300_B:5(config)# save bootconfig ERS8300_B:5(config)# boot -y  ERS8300 supports multiple user defined ACL patterns with this new configuration boot flag (t-mode). The above ACL patterns can be used to filter ARP reply packets based on user defined offset and length. 16. Communication Control Toolkit (CCT) integration with Genesys T-Server Setting up CCT6 to interface with a Genesys T-Server that will communicate with the M-1 via the Meridian Link Services Module (MLSM) link and provide call information to CCT that will be passed on to IVR(MPS500) correctly and allow screen pops. In this setup the CCT does not communicate directly to the M-1 but through the T-Server to get the M-1 information. Install CCT as a Knowledge Worker and apply all PEPs and Patch bundle as documented in the NTPs. Configuring the Media Processing Server (MPS) manager: Log in as Administrator At the Telephony Link Identifier window by default you have a (tlsdefault) ID. You can modify this default ID or add a new ID. When interfacing to a Genesys T-Server you will need to use the default (tlsdefault) ID and select modify. You would then add the IP address and port number that Genesys is using.  Configuration window for adding the Genesys IP address and port number.  If you select ADD you get the option to select M-1, Avaya (3), ICM or Genesys. If you select Genesys and configure it with the IP address and port number the system creates a new system or sit ID.  When the CCT receives the call information from the TServer it has the M-1 site information (HLOC) and the calling line information and site ID. When CCT sends this information to IVR (MPS500) the ID sent from CCT, (when added as Genesys) is a different site ID then the one the T-Server sent. The original site ID does not match what the IVR has and the screen pops fail. By using the tlsdefault ID, the information that CCT receives from the T-Server is passed through to the IVR correctly. The information that IVR gets matches what the T-Server has and the call is sent to the work station and screen pops occur. The tls.cfg log of a working system is included below: logmode +all #logmode -applic #logmode -connect #logmode -ftrace #logmode -mcblib #logmode -msgdump #logmode -terse logmode -timer #logmode -verbose logsize 20384 service-gts start serviceid tlsdefault pollinginterval 10 requesttimer 10 pbxtype gts_m1 hostaddress 172.16.0.75 switchport 3000 linkinterface third_party_tcp_ip setlink serviceid tlsdefault uniquecallids off serviceid tlsdefault debug_protocol on serviceid mcb pbxtype mmpserver hostaddress localhost switchport 5151 linkinterface ipc setlink startlinks |
||
