![]() |
Wireless News Aggregation |
|
|
Welcome Back To How we can prevent 911 calls going unansweredBY JEFF MCLEOD AND RONALD HEWITT, OPINION CONTRIBUTORS 06/13/17 11:00 AM EDT
It has been a tough couple of months for 911 call centers. In at least seven states, callers in need of help in March were placed on hold or simply couldn’t reach a dispatch center. More alarming was a denial of service attack, launched by a teenager that nearly took out 911 call centers in at least a dozen states. Regardless of the cause, the result was the same — those in an emergency were unable to reach first responders. Those incidents are indicative of challenges across the state emergency communications ecosystem, which — in addition to 911 call centers — includes land mobile radio (LMR) communications and broadband networks. In many ways, the emergency communications ecosystem is only as strong as its weakest link. Demands on broadband networks will increase as states increasingly adopt next generation 911 or NG911, which will allow citizens to send messages via text, picture or video. Without sufficient broadband capacity for public safety, dispatch centers would be unable to transmit that critical data over a secure and reliable network to first responders. Even with NG911 and a broadband network, the LMR systems that allow first responders to communicate are in need of upgrading, thereby affecting their ability to coordinate across jurisdictions and, ultimately, to assist callers in need. Certainly, funding remains a challenge in many jurisdictions when it comes to building a highly functioning emergency communications ecosystem. However, often overlooked is the importance of strong governance for emergency communications. Strong governance, through established bodies, facilitates greater capability and interoperability among these technologies by coordinating planning and response, which are often fragmented across agencies and levels of government. Last year, the National Governors Association’s Center for Best Practices and the U.S. Department of Homeland Security’s Office of Emergency Communications launched a project to assist a class of participants from five states with identifying challenges and solutions to improving governance of their state’s emergency communications ecosystem. Governor-appointed teams from Alaska, Hawaii, Illinois, Utah and West Virginia participated in the Policy Academy on Enhancing Emergency Communications Interoperability. The NGA Center and OEC recently published three key findings that can help other jurisdictions strengthen their ecosystem and the ability of first responders to save lives. First, state officials responsible for overseeing a state’s LMR interoperability—statewide interoperability coordinators or SWICs—must be empowered to facilitate coordination among their broadband and 911 counterparts. A strong and empowered partnership among these individuals will further ensure that priorities are aligned to maximize expenditures. LMR, broadband and 911 are the backbone to responding to everyday emergencies and for communicating across public safety entities. Without these tools, the millions of first responders across the nation would be unable to do their jobs. It is our responsibility, and duty, to make the best tools available to the men and women who put their lives at risk every day to save others. Second, states should prioritize sustaining an active governance body to coordinate and support all emergency communications. Since these tools are used by several agencies and localities, it is necessary to bring these stakeholders together to unify support around common goals and objectives. Third, officials should revitalize the statewide communication interoperability plan, or SCIP, and inform executive decision makers. This plan is the strategy that guides states’ efforts to improving their emergency communications, but tends not to get the attention it deserves. State officials should emphasize the plan’s importance and garner support for its operation. Lastly, and in line with the third lesson learned, lawmakers and legislatures must be engaged to promote support for the SCIP and identify long-term sustainability solutions. Implementing these recommendations will require leadership. No one is better positioned to lead such efforts than the governor. With authority over state agencies and the ability to convene key stakeholders, they can set priorities, build consensus. and ensure state agencies are coordinated — when emergencies happen. The time to act is now. Lives depend on it. Jeff McLeod is the director of the Homeland Security and Public Safety Division at the National Governors Association’s Center for Best Practices. Ronald Hewitt (Rear Admiral,USCG ret.) is the director of the Office of Emergency Communications in the U.S. Department of Homeland Security. The views of contributors are their own and not the views of The Hill. Source: The Hill. Now on to more news and views. |
Wayne County, Illinois
A new issue of the Wireless Messaging Newsletter is posted on the web each week. A notification goes out by e-mail to subscribers on most Fridays around noon central US time. The notification message has a link to the actual newsletter on the web. That way it doesn’t fill up your incoming e-mail account. There is no charge for subscription and there are no membership restrictions. Readers are a very select group of wireless industry professionals, and include the senior managers of many of the world’s major Paging and Wireless Messaging companies. There is an even mix of operations managers, marketing people, and engineers — so I try to include items of interest to all three groups. It’s all about staying up-to-date with business trends and technology. I regularly get readers’ comments, so this newsletter has become a community forum for the Paging, and Wireless Messaging communities. You are welcome to contribute your ideas and opinions. Unless otherwise requested, all correspondence addressed to me is subject to publication in the newsletter and on my web site. I am very careful to protect the anonymity of those who request it. I spend the whole week searching the Internet for news that I think may be of interest to you — so you won’t have to. This newsletter is an aggregator — a service that aggregates news from other news sources. You can help our community by sharing any interesting news that you find.
Editorial Opinion pieces present only the opinions of the author. They do not necessarily reflect the views of any of advertisers or supporters. This newsletter is independent of any trade association. I don't intend to hurt anyone's feelings, but I do freely express my opinions. Subscribe IT'S FREE * required field If you would like to subscribe to the newsletter just fill in the blanks in the form above, and then click on the “Subscribe” button. There is no charge for subscription and there are no membership restrictions. It’s all about staying up-to-date with business trends and technology.
The Wireless Messaging News
The Board of Advisor members are people with whom I have developed a special rapport, and have met personally. They are not obligated to support the newsletter in any way, except with advice, and maybe an occasional letter to the editor.
Can You Help The Newsletter?
You can help support The Wireless Messaging News by clicking on the PayPal Donate button above. It is not necessary to be a member of PayPal to use this service.
Newspapers generally cost
A donation of $50.00 would certainly help cover a one-year period. If you are wiling and able, please click on the PayPal Donate button above. Back To Paging
Still The Most Reliable Protocol For Wireless Messaging!
|
![]() |
Advertiser Index
|
STI Engineering |
![]() |
Web Site: | http://www.stiengineering.com.au | E-mail: | sales@stiengineering.com.au |
sales@wirelessmessaging.com
Contact Us for OEM Requests BluTrac (Bluetooth Tracking and Control)
MARS (Mobile Alert Response System)
STG (SIP to TAP Gateway)
|
|
SkyTel Luminaries
|
Source: | Facebook (June 9, 2017) |
Voluntary Newsletter Supporters By Donation |
Kansas City
Premium Newsletter Supporter
Premium Newsletter SupporterCanyon Ridge CommunicationsPremium Newsletter SupporterProPage Inc.Newsletter SupporterMetropolitan Communications
Newsletter Supportere*Message Wireless Information Services Europe
Newsletter SupporterLekkerkerk, NetherlandsNewsletter Supporter |
Incyte Capital Holdings LLC
|
Prism Paging |
![]() |
Product Support Services, Inc. |
Repair and Refurbishment Services
Product Support Services, Inc.
511 South Royal Lane
PSSI is the industry leader in reverse logistics, our services include depot repair, product returns management, RMA and RTV management, product audit, test, refurbishment, re-kitting and value recovery. |
CEO Notruf NÖ Austria Compares TETRA & POCSAG AlertingNotruf NÖ operates one of Austria’s biggest integrated rescue services, serving Lower Austria, the large region surrounding Austria’s capital Vienna. NÖ’s rescue forces, with more than 96,000 voluntary firemen and 16,000 voluntary paramedics, respond to more than 1.1 million emergency events per year. For these volunteers it is crucial to be alerted, quickly, accurately and reliably.
“Volunteers need to be alerted wherever they are in their daily routines; they need to be alerted in their basements, in their houses — sometimes in their old houses with big walls. Our alerting solution therefore has to provide full indoor coverage and work anywhere, anytime,” says Christof Constantin Chwojka, CEO Notruf NÖ. Throughout the last decade, Notruf NÖ has gathered extended experience with different public safety communication and alerting systems. The organisation benefits from a TETRA network with 400 base stations in Lower Austria and is operating a POCSAG network with 130 paging base stations covering the entire region. At this week’s Critical Communications World 2017 Hong Kong, Christof Chwojka, gave a presentation on “A Comparison of Public Safety Alerting & Communications Technologies,” comparing TETRA’s and POCSAG’s suitability from an alerting perspective. Here are some of his key findings he shared with the audience:
Christof Chwojka concludes that alerting via POCSAG paging is the most suitable solution for alerting a large number of intervention forces, not only from a reliability and cost perspective, but also from the perspective of the enduser’s comfort: “Volunteers don't want to sleep every night close to the charging station,” says Christof Chwojka. The fact that this requires a POCSAG network next to the TETRA network does not create additional costs compared to an alerting solution with TETRA. In fact, the contrary is true, due to the difference in price of the end-user devices. Given a total of 112,000 volunteers, this amounts to more than 22 Million Euros. With the POCSAG network amounting to less than 2 Million Euros, this results in potential savings of more than 20 Million Euros. “On top of that, our TETRA network is not ready for this large number of alerts, and it covers only the exterior rooms of a house in instead of the full building. To achieve the same TETRA coverage we have today with our POCSAG network by adding TETRA base stations to our TETRA network would create huge additional costs we prefer to avoid,” adds Christof Chwojka. Another advantage Christof Chwojka sees in two separate networks is the overall system redundancy: “If our TETRA network is not working, we can transmit additional information through our POCSAG network, and if the POCSAG network may not be working, we can alert via TETRA, so both systems are serving as backup to each other.” After revisiting their alerting concept for the coming years, Notruf NÖ has therefore decided to maintain and further invest in its POCSAG infrastructure. “Today our POCSAG system is not yet fully self-reliant. We want to take the next step with our partner Swissphone making our network completely independent of any third-party infrastructure. We therefore plan to implement Swissphone’s newest network technology with additional fallback modes such as allowing base stations to communicate over the air if necessary,” says Christof Chwojka. “We want to be ready for any potential future events such as terrorist attacks on infrastructure. Whatever happens to a base station, whatever happens to a transmission in the network, whatever happens in the command center, to the network controller, to whatever, must not be a problem in the future, that is our goal and that is what we want to reach,” concludes Christof Chwojka. |
Source: | Swissphone Holding AG | (Current exchange rate: €1.00 Euro = $1.12 US Dollars.) |
POCSAG: The basic signaling pattern used in many pagers is a sequence of coded binary data using the Post Office Code Standardisation Advisory Group (POCSAG) code. The POCSAG code is a synchronous paging format that allows pages to be transmitted in a single-batch structure. The POCSAG code provides improved battery-saving capability and an increased code capacity. The POCSAG code format consists of a preamble and one or more batches of codewords. Each batch comprises a 32-bit frame synchronization code and eight 64-bit address frames of two 32-bit addresses or idle codewords each. The frame synchronization code marks the start of the batch of codewords. |
RF Demand Solutions |
|
Leavitt Communications |
|
Draft 1.8- 06.11.2017 Mission Critical Communications Article By Rex M. Lee
“Do Smartphones Violate Federal & Industry Cyber Security Standards, NDAs, & Confidentiality Laws?”
The answer is yes according to T-Mobile’s admission (see enclosed quote) that third-parties collect and use surveillance data and sensitive user data collected from telecommunication subscribers via app driven connected devices such as smartphones. The T-Mobile admission was a result of an FCC privacy complaint I filed with the FCC against T-Mobile in July of 2015. I conducted a Samsung Galaxy Note terms of use and installed (“pre-installed/install-by-update”) application analysis to back my privacy complaint with hard data. Due to T-Mobile’s admission coupled with my research, I can tell you that app driven connected technology such as smartphones do not meet federal and industry cyber security standards or critical infrastructure service level agreement criteria. I can state that anyone who uses app driven connected technology for official business is inadvertently violating any nondisclosure and confidentiality agreement that that they may have with their employer. Furthermore, any legal professional, healthcare provider, and government employee who uses app driven connected technology for official business is inadvertently violating confidentiality laws that govern official business pertaining to legal matters, medical purposes, and/or the handling of classified information. Do not take my word for it, T-Mobile confirms it:
If you read the quote carefully, T-Mobile implies that due to the invention of the smartphone, privacy and cyber security should not be expected by the user. My research shows that important legalese that supports the lawful acquisition of connected product user data is hidden from the product owner and/or authorized device user (employees, spouse, children, etc.). The legalese includes installed application permission statements and app product warnings that are not transparent to the app driven connected product user. Below is an example of a real android application permission statement: Figure 1 — Hidden android Application Permission Statement and Product Warning (Galaxy Note screen shot). The permission below is attached to apps such as the Google Services Frameworks app:
Due to hidden app permissions, after spending months doing the analysis, I can only conclude that companies such as Apple, Google, and Microsoft are not being transparent with the T-Mobile telecommunication subscriber when it comes to the connected product business model. For example, what was very troubling was the fact that my T-Mobile agreement implied that my identification would remain anonymous to third-parties since they use the term “de-identified” when referencing the telecommunication product user within the T-Mobile privacy policy. This may be true for T-Mobile, but android app permissions tell another story. Android (Google) app permissions contradict the T-Mobile statement that the user remains anonymous. The personal profile app permission statement is clear when it comes to the identity of the product user. The app permission clearly states that the user can be identified by the apps that contain the personal profile app permission. See the example below: Figure 2 — Personal Profile android App Permission Statement
My research shows that these companies are actually using surveillance and sensitive user data for predictive technology and artificial intelligence (“AI”) so the user can have a better product experience or at least that is what companies such as Google state. Since I do consulting work for a defense contractor and work within critical infrastructure (utility, public safety, oil & gas), it would have been nice for T-Mobile to have explained to me that smartphones are not private prior to me making a product purchase. It would be nice if TV ads promoting app driven telecom products also explained that smartphones are not private then I would not have bought the intrusive and exploitive product in the first place. I believe people who use smartphones for confidential communications and computing really do not understand how smartphones work nor do they understand the connected product business model. After all I did not understand how smartphones really worked nor did I understand the app driven connected product business model until I conducted the Samsung Galaxy Note terms of use and installed app analysis. Samsung Galaxy Note Smartphone Terms of Use and Installed App Analysis While doing consulting work for Space Data Corporation (U.S. defense contractor), I had concerns that third-parties were using the installed apps that supported the Galaxy Note to conduct surveillance on me while collecting surveillance data and sensitive user data. In November of 2014, I conducted a Samsung Galaxy Note terms of use and installed (“pre-installed/install-by-update”) app analysis to back my privacy concerns with hard data. The terms of use included product terms and conditions (“T&Cs”), privacy policies, end user licensing agreements (“EULAs”), application permission statements, and application product warnings. Note that the app permissions and app product warnings were not published in the product terms of use but were hidden in the OS of the device. I identified over 15 multinational entities that were responsible for the development of the Installed apps & content. Many of the apps developed by the multinational entities were governed by app permissions enabling the entities to lawfully conduct surveillance on the product user while the entities data mined connected product user data from the user’s smartphone. Over 275 installed apps supported the Galaxy Note. Each app is supported by an end user licensing agreement (“EULA”) that consisted of 1 to 12 or more pages of legalese. It took me nearly 4 months to research the apps, EULAs, and the terms of use from each company that supported the device. In other words, it took me nearly 4 months to read my cellular phone contract. The Terms of Use do not fully explain how all third-parties use, share, sell, purchase, and aggregate surveillance data and sensitive user data. The apps were even more difficult than the terms of use to analyze since there were over 275 installed apps that supported the Galaxy Note. I classified the android OS as “predatory” since it is designed to give full control to Google while not allowing the product owner the ability to uninstall any of the installed apps or content. I found that most of the intrusive apps could not be controlled nor disabled. I broke the installed apps out into subsets plus identified intrusive apps as predatory and surveillance apps. Predatory apps are designed to enable third-parties to collect sensitive user data (detailed content). Surveillance apps are programmed to enable third-parties the ability to monitor and track the connected product user while collecting the surveillance data produced by the product user. Apps that included predatory and surveillance capabilities included every day usage apps such as the contact app, Samsung keyboard app, email app, gallery (photo) app, messaging (text) app, music app, phone (make calls) app, video app, plus other apps that support basic functionality. After I conducted the Galaxy Note analysis I had identified numerous privacy concerns, cyber security threats, and potential deceptive trade violations I had escalated to T-Mobile, Samsung, and the FCC. To date there are many unanswered questions which T-Mobile, Google, Samsung, the FCC and FTC should address such as:
Paying telecommunication subscribers have a right to know the answers to these all important questions due to privacy concerns and cyber security threats posed by app driven connected technology. The amount of surveillance data and sensitive user data being collected from app driven smartphones is staggering. For example:
Figure 3 — Predatory app permissions (screen shots of actual android app permissions- Galaxy Note):
Figure 4 — Syncing android App Permissions
Figure 5 — Surveillance Hardware android App Permissions
Figure 6 — Surveillance App Permissions
Figure 7 — Control android App Permissions
Figure 8 — BAIDU Interactive Application Permission Command String (National Security Risk) In all there were over 100 predatory and surveillance app permissions that supported each of the over 275 installed apps that were pre-loaded into the Galaxy Note smartphone. Many of the app permissions contained app product warnings. Per my research coupled with the T-Mobile admission, it is obvious that app-driven-connected products should not be used in an environment that requires confidentiality governed by cyber security standards, NDAs, SLAs, and confidentiality laws. In closing, an electronic bill of rights is needed to protect the privacy and data of businesses and consumers who use app driven connected technology. Figure 9 — Electronic Bill of Rights
|
Source: | RML Business Consulting, LLC | “Proprietary” All rights reserved 2017 |
Swissphone |
Disaster-Proven Paging for Public SafetyPaging system designs in the United States typically use a voice radio-style infrastructure. These systems are primarily designed for outdoor mobile coverage with modest indoor coverage. Before Narrowbanding, coverage wasn’t good, but what they have now is not acceptable! The high power, high tower approach also makes the system vulnerable. If one base station fails, a large area loses their paging service immediately! Almost every technology went from analog to digital except fire paging. So it’s time to think about digital paging! The Disaster-Proven Paging Solution (DiCal) from Swissphone offers improved coverage, higher reliability and flexibility beyond anything that traditional analog or digital paging systems can provide. Swissphone is the No. 1 supplier for digital paging solutions worldwide. The Swiss company has built paging networks for public safety organizations all over the world. Swissphone has more than 1 million pagers in the field running for years and years due to their renowned high quality. DiCal is the digital paging system developed and manufactured by Swissphone. It is designed to meet the specific needs of public safety organizations. Fire and EMS rely on these types of networks to improve incident response time. DiCal systems are designed and engineered to provide maximum indoor paging coverage across an entire county. In a disaster situation, when one or several connections in a simulcast solution are disrupted or interrupted, the radio network automatically switches to fall back operating mode. Full functionality is preserved at all times. This new system is the next level of what we know as “Simulcast Paging” here in the U.S.
Swissphone offers high-quality pagers, very robust and waterproof. Swissphone offers the best sensitivity in the industry, and battery autonomy of up to three months. First responder may choose between a smart s.QUAD pager, which is able to connect with a smartphone and the Hurricane DUO pager, the only digital pager who offers text-to-voice functionality. Bluetooth technology makes it possible to connect the s.QUAD with a compatible smartphone, and ultimately with various s.ONE software solutions from Swissphone. Thanks to Bluetooth pairing, the s.QUAD combines the reliability of an independent paging system with the benefits of commercial cellular network. Dispatched team members can respond back to the call, directly from the pager. The alert message is sent to the pager via paging and cellular at the same time. This hybrid solution makes the alert faster and more secure. Paging ensures alerting even if the commercial network fails or is overloaded. Swissphone sets new standards in paging: Paging Network
Pager
Dispatching:
Swissphone provides a proven solution at an affordable cost. Do you want to learn more?
|
GOOGLE DRIVE Google Drive Will Soon Be Able to Back Up Your Whole Computer Madeline Farber Starting soon, you'll be able to rely on Google Drive to back up your computer. On Wednesday, Google (GOOGL, -1.90%) revealed in a blog post that it's releasing a new feature on June 28 called "Backup and Sync." The update, which is intended for consumer users, will allow users to access "huge corporate data sets without taking up the equivalent space on their hard drives," reads the blog. In other words, as USA Today notes, this means that users can have Google Drive back up an entire Desktop folder instead of putting individual files into the Google Drive folder. What's more, Google will continue to backup the folder so everything stays up-to-date. According to the Verge, in some cases Backup and Sync will replace the standard Google Drive app and the Google Photos Backup app. The Verge also notes that it's likely the files will count toward the Google Drive storage limit. |
Source: | FORTUNE.com |
Leavitt Communications |
|
Preferred Wireless |
Surplus Paging Equipment Inventory |
QTY. | MFG. | MODEL NUMBER | DESCRIPTION |
MISC. | |||
1 | Powerware | UPS Model 5119 (new batteries) | |
3 | Glenayre | Universal Exciter, VHF | |
2 | Glenayre | Hot Standby Panel - Old Style | w/antenna relay |
4 | Glenayre | Hot Standby Panel - New Style | |
2 | Spectrum Comm. | Prizm SS10000 Ultra High Simulcast Generator | Currently on 462.8500 |
1 | Motorola | Motorola UDS RM16M Modem Shelf | Includes (10) V.3225 & (1) 202T Modem Cards |
3 | Motorola | UDS Modems, Model 103 LP | |
2 | Spectrum Comm. | Prizm SS10000 Ultra High Simulcast Generator | Currently on 462.8500 |
CABINETS & RACKS | |||
6 | Glenayre | 24" Cabinet - New - Wall Mount Enclosure | Wall Mount, lift-off Front door |
14 | Electrorack | 46" Cabinet - New | Front & Rear hinged doors, Exhaust Fan |
1 | Electrorack | 72" Cabinet - New | Front & Rear hinged doors, Exhaust Fan |
4 | Unknown | Steel Open Rack | 42" x 19" |
ANTENNAS | |||
2 | Decibel | Antenna, DB806DT6-Y, 890-960 MHz | Used |
1 | Decibel | Antenna, DB205F, 144-175 MHz | in cardboard tubes |
1 | Motorola | Antenna, TAD6074A, 162-174 MHz, Folded Coaxial, Unity Gain | Omnidirectional, Unity gain |
1 | Cellular Specialties | Antenna, CSI-AY, 806-960 MHz, 11dB | 11dB gain, 8 Element Yagi |
1 | Antenex | Antenna, YS8966, 896-870, 9dB | 9dB gain, 6 Element Yagi |
36 | Andrews | Antenna, PG1N0F-0093-810, Omni, 928-944 MHz, 10dB, 8 degrees down tilt | 4 new, 34 used |
POWER SUPPLIES | |||
9 | Glenayre | Auxiliary Power Supplies, 16-29VDC | used w/ancillary equip. such as TCC or RL900 Rx. |
2 | Motorola | 12 VDC Power Supply, Desktop Motorola & Astron | |
2 | Glenayre | GL-AC2825 28VDC Power Supply | 100-120/200-240 VAC, 50/60Hz input, 28VDC @ 25A output |
1 | Glenayre | Power supply Model 2100.00113 | Used in 83/8411 |
1 | Newmar | DC-DC Converter Model 48-12-12I | input 20-56 VDC, output 13.6 VDC |
SATELLITE & CONTROL EQUIPMENT | |||
6 | Motorola | ASC-1500 Chassis | Includes (2) 48VDC PS, (2) Memory Cards, (10) ATC Cards |
32 | Motorola | ASC-1500, ATC Card | NRN9232 |
8 | Motorola | ASC-1500, Memory Card | N |
6 | Motorola | CNet Platinum Controller Chassis, P/N: PT1046A | Includes: no cards |
6 | Motorola | Connect Platinum Controller - NCU Cards | Network Control Unit Cards, fully tested |
4 | Motorola | Connect Platinum Controller - NCX Cards | Network Control Switch Cards, fully tested |
8 | Motorola | Connect Platinum Controller - CIU Cards | Channel Interface Unit Cards, fully tested |
3 | Glenayre | DCU II Controllers | |
1 | Skydata | Modem Protection Switch, 8550 | Model 8550 |
40 | Skydata | 8466B Satellite Receivers | 8 New |
1 | Skydata | MSK Modulator, 8360 | |
2 | Skydata | Station Supervisory Unit | P/N: MDL5070S0101 |
3 | Skydata | Station Supervisory Unit, 5070 | Model 5070 |
1 | Skydata | Digital Transmitter | P/N: MDL83728002 |
1 | Gilat | Skyway ODU Controller, 2001 | P/N: MDL2001K0101 |
2 | Skydata | RFT Protection Switch | P/N: MDL8562S0003 |
4 | Gilat | Satellite Transmitter | P/N: 44-300 |
4 | Gilat | Skymux Controller, 8870 | P/N: MDL8870S0101 |
2 | Gilat | Skymux Protection Switch, 8553 | P/N: MDL8553S0002 |
3 | TrueTime | GPS Time & Frequency Receiver | Model XL-AK |
3 | Chase | IOLan+Rack Communications Server | 1 New, 1 Used |
2 | Skydata | Model 5090 Uplink Power Control (NEW) | |
9 | Zetron | Model 66 Link Controllers | P/N: 901-9435 |
12 | Zetron | Model 66 Transmitter Controllers | P/N: 901-9094 |
16 | Zetron | Multi-Site Option Board - for model 66 | P/N: 702-9156 |
2 | Zetron | Delay Board - for model 66 | P/N: 702-9157 |
MOTOROLA PURC 5000 PARTS | |||
8 | Motorola | HSO - UHF, High Stab Osc. - TLF1650A | HSO out of PURC 5000 UHF transmitter |
15 | Motorola | RF Tray, PURC 5000, UHF | |
30 | Motorola | 5 MHz Oscillator - KXN1173AA | |
6 | Motorola | UHF VCO - TTE1472B | UHF VCO Module - used inside RF Tray |
MOTOROLA NUCLEUS PARTS | |||
5 | Motorola | Nucleus Link Receiver, VHF, 150-174 MHz | 150-174 MHz |
6 | Motorola | Nucleus Link Receiver, Midband | 72-76 MHz |
11 | Motorola | Nucleus GPS Reference Receivers | PTRN1013 |
24 | Motorola | Nucleus GPS Dome Receiver Antenna (16 Dome & 8 Puck type) | unknown |
1 | Motorola | Nucleus GPS Reference Receiver | PTRN1002B |
14 | Motorola | Nucleus Receiver Interface boards CRIB | Part No.: TTN4088 |
5 | Motorola | Nucleus Reference Module - PTRN1002B | Reference Module |
30 | Motorola | Nucleus Keypad - CNet - TRN7816A | TRN7816A |
10 | Motorola | Nucleus Keypad - NAC - TTN4014A | TTN4014A |
6 | Motorola | Nucleus 900 MHz PA | 900 MHz Final PA |
6 | Motorola | Nucleus VHF PA - TLD3403A | VHF 350W Final PA |
LINK TRANSMITTERS & RECEIVERS | |||
1 | DX Radio | Midband Exciter - Synthesized | Model T70AM Midband Exciter |
16 | Motorola | PURC 5000 Link Receiver, Midband | |
1 | Motorola | Link Transmitter, C35JZB6101, 900 MHz | 10W 900 MHz Link TX |
1 | Motorola | Link Transmitter, C35JZB6101, 900 MHz | 10W, 900 MHz Link TX, w/HSP |
1 | Motorola | Link Transmitter, C35JZB6106, 900 MHz | 10W 900 MHz Link TX |
7 | Glenayre | QT-4201, 25W, Midband, Link Transmitter | 25W Midband Link |
9 | Glenayre | QT-4201, 25W, Midband, Link Transmitter | 25W Midband Link |
PAGING TRANSMITTERS | |||
1 | Glenayre | GLT-8200, 25W, 900 MHz, (New) | 46" cabinet, w/C2000 |
1 | Glenayre | GLT-8200, 25W, 900 MHz, (New) | 46" cabinet, w/C2000 |
1 | Glenayre | QT-7505, 250W, TCC | 250W, TCC, RL72, currently on 158.10 |
1 | Glenayre | QT-8505, 500W, C2000 | 500W, C2000, RL72, currently on 152.48 |
3 | Quintron | QT100C, 100W, VHF | 100W VHF Transmitter, with Universal Exciter |
8 | Glenayre | GLT-5340, 125W, UHF | Exciter, PA, PS, Complete TX |
3 | Motorola | Nucleus, VHF, 350W, CNET | |
10 | Motorola | Nucleus, VHF, 125W, CNET | |
7 | Motorola | Nucleus, VHF, 350W, NAC Control | |
14 | Motorola | Nucleus, VHF, 125W, NAC Control | Model: T5481B |
1 | Motorola | Nucleus, UHF, 100W, NAC Control | |
GL 3000 CARDS & PARTS | |||
1 | Glenayre | GL3000L Terminal, 2 Cabinets, Complete | |
1 | Glenayre | GL3100 RF Director | |
1 | Glenayre | GL3100 RF Director | |
2 | Glenayre | GL3000 ES Terminal 2 Chassis (Not Complete) | |
16 | Glenayre | UOE Card | |
5 | Glenayre | UOE Daughter Board | |
2 | Glenayre | CPU-030+ | |
2 | Glenayre | CPU-302 8MB | |
4 | Glenayre | CPU 302 | |
1 | Glenayre | CPU 604 NPCS 333/128MB | |
2 | Glenayre | CPU-030 | |
3 | Glenayre | CPU-060 50/32MB | |
2 | Glenayre | CPU 360 33/16MB | |
1 | Glenayre | Net 060 50/16MB | |
1 | Glenayre | Net-060 50/32MB | |
2 | Glenayre | Net 360 33/32MB | |
1 | Glenayre | PC/NVR 16MB | |
1 | Glenayre | 2M Ram + | |
2 | Glenayre | 4M Ram + | |
1 | Glenayre | 8M Ram+ | |
1 | Glenayre | 16MB Ram+ | |
3 | Glenayre | 32M Ram+ | |
4 | Glenayre | -48V Power Supply w/Floppy Drive | |
2 | Glenayre | -48v Power Supply | |
7 | Glenayre | 5V Converter | |
6 | Glenayre | 12V Converter | |
1 | Glenayre | Power Control Card | |
1 | Glenayre | Optical Drive | |
2 | Glenayre | 1.1 G Hard Drive | |
5 | Glenayre | Switch Clock | |
1 | Glenayre | Switch Clock | |
9 | Glenayre | CPT (New) | |
3 | Glenayre | CIF | |
2 | Glenayre | ECIF | |
1 | Glenayre | CPV (New) Call Progress Voice Generator Card | |
17 | Glenayre | DID | |
1 | Glenayre | ETE - End to End Card | |
3 | Glenayre | APT (audio pass through), DMC | |
2 | Glenayre | T1 | |
1 | Glenayre | T1 | |
2 | Glenayre | SCSI | |
5 | Glenayre | SCSI 2 | |
4 | Glenayre | SIO Card | |
3 | Glenayre | ISIO | |
3 | Glenayre | SCSI-2 | |
1 | Glenayre | SIO Card | |
4 | Glenayre | VCB - Voice Compression Board | |
1 | Glenayre | DVSB, Dual Voice Storage Buffer | |
2 | Glenayre | QVSB, Quad Voice Storage Buffer | |
1 | Glenayre | Alarm Card | |
2 | Glenayre | Link Module | |
1 | Glenayre | Redundancy Switch | |
1 | Glenayre | Switch | |
1 | Glenayre | Transfer | |
1 | Glenayre | Arbtrator | |
1 | Glenayre | IDC | |
1 | Glenayre | DCC - Bread Board | |
2 | Glenayre | Bread Board | |
1 | Glenayre | Extender Card | |
ZETRON CARDS & PARTS | |||
1 | Zetron | Zetron DAPT 1000 Paging Terminal | Includes 2 dual trunk cards |
1 | Zetron | Zetron 2200 terminal, Z # 068-0211 | HD Card, Micro PC-10 card, Hayes Modem card, RS232 card, Voice card 702-9051, 2000 Master card, 702-9176. (4) Dual Trunk cards 702-9037 |
2 | Zetron | HD Cards | |
2 | Zetron | I/O cards | |
1 | Zetron | 2000 CPU 702-9176 | |
2 | Zetron | ADPCM Voice 702-9153 | |
4 | Zetron | Multiport 702-9191 | |
1 | Zetron | Internal SCSI z#49595 | |
1 | Zetron | Extender Card | |
1 | Zetron | 2000 Master 702-9560 | |
1 | Zetron | 2000 SCSI Host adapt. 702-9923A | |
1 | Zetron | Voice Card, P/N:702-9051 | |
2 | Zetron | Modem cards | |
3 | Zetron | Power supplies – Condor SDM200B | |
3 | Zetron | Power supplies – Condor HB48-0.5-A | |
9 | Zetron | Model 66 Link Controllers | P/N: 901-9435 |
12 | Zetron | Model 66 Transmitter Controllers | P/N: 901-9094 |
16 | Zetron | Multi-Site Option Board - for model 66 | P/N: 702-9156 |
2 | Zetron | Delay Board - for model 66 | P/N: 702-9157 |
|
Preferred Wireless |
|
Source: | Inside Towers |
Wireless Communication Solutions USB Paging Encoder
Paging Data Receiver (PDR)
Other products Please see our web site for other products including Internet Messaging Gateways, Unified Messaging Servers, test equipment, and Paging Terminals.
|
A ProblemThe Motorola Nucleus II Paging Base Station is a great paging transmitter. The Nucleus I, however, had some problems. One of the best features of this product was its modular construction. Most of the Nucleus' component parts were in plug-in modules that were field replaceable making maintenance much easier. One issue was (and still is) that two of the modules had to always be kept together. They are called the “matched pair.” Motorola used some tricks to keep people in the field from trying to match unmatched pairs, and force them to send SCM and Exciter modules back to the factory for calibrating them with precision laboratory equipment. The serial numbers have to match in the Nucleus programing software or you can't transmit . Specifically the 4-level alignment ID parameter contained in the SCM has to match the Exciter ID parameter.Even if someone could modify the programing software to “fudge” these parameters, that would not let them use unmatched modules effectively without recalibrating them to exact factory specifications. So now that there is no longer a Motorola factory laboratory to send them to, what do we do? I hope someone can help us resolve this serious problem for users of the Nucleus paging transmitter. Please let me know if you can help. [click here] [Thanks to Tom Harger Chief Engineer at Contact Wireless for the correction above in ]
|
BloostonLaw Newsletter |
Selected portions [sometimes more — sometimes less] of the BloostonLaw Telecom Update and/or the BloostonLaw Private Users Update — newsletters from the Law Offices of Blooston, Mordkofsky, Dickens, Duffy & Prendergast, LLP — are reproduced in this section of The Wireless Messaging News with the firm’s permission. Contact information is included at the end of the newsletter.
REMINDER: FCC Form 481 Due July 3, New Location Reporting RequirementsEligible Telecommunications Carriers are reminded that this year’s annual Form 481 filing is due July 3. For 2017, ETCs do not have to file Section 100 Five-Year Plan Progress Reports. Additionally, CAF Phase II participants will report location data and make the associated certifications in the HUBB portal rather than on Form 481. This is also the first time Rate of Return carriers will be filing location data. Specifically, CAF BLS recipients must report location data through the HUBB portal, but only those locations added since May 25, 2016. ACAM recipients will report for the first time next year. BloostonLaw is experienced in preparing and filing Form 481, as well as meeting the FCC’s requirements to obtain confidentiality for the filings. Carriers interested in obtaining assistance should contact the firm. BloostonLaw Contacts: Gerry Duffy and Sal Taillefer. HeadlinesFCC Filing Window for Grandfathered 3.65-3.7 GHz Protection Zones Closes August 7The FCC has established a filing window for incumbent licensees in the 3.65-3.7 GHz band to file supplemental information to define their Grandfathered Wireless Protection Zone within the framework for deployment of the Citizens Broadband Radio Service (CBRS). This filing is necessary for incumbent 3.65-3.7 GHz licensees to enjoy interference protection from new CBRS operations. The deadline for filing any application in the FCC’s Universal Licensing System (ULS) to be afforded protection is August 7, 2017. Clients with 3.65 GHz licenses should contact us promptly if they would like help protecting their existing operations.
As we previously reported, in 2015, the FCC established a new CBRS service in the 3.55-3.70 GHz service, which encompassed spectrum in the 3.65-3.7 GHz band. At that time, the FCC adopted rules in order to protect existing licensees’ registered base stations in the 3.65-3.7 GHz band from harmful interference from CBRS users for a fixed transition period of five years, until April 17, 2020 or for the remainder of the license term – whichever is longer (with the exception that Part 90 incumbents licensed after January 8, 2013 will be limited to a protection period of five years). In order to be able to seek protection, the station must (a) have been registered in the FCC’s Universal Licensing System (ULS) on or before April 17, 2015 and (b) constructed and placed in service as of 1 year later or by April 17, 2016.
The FCC has established a two pronged approach which defines the Grandfathered Wireless Protection Zone around each registered base station, as follows: (a) for sectors encompassing unregistered customer premise equipment (CPE), a 5.3 km radius sector from each registered base station based on the azimuth and beam width registered for that base station and (b) for sectors encompassing registered CPE, a sector centered on each base station with the registered azimuth and beam width covering all registered subscriber stations within that sector.
The following information must be included in any filing in order to establish the Grandfathered Wireless Protection Zone:
If the 3.65-3.70 GHz equipment is being used for point-to-point operations, the licensee will be required to register each end of the point-to-point links separately as a base station and identify the receive location for that end of the point-to-point link as the furthest registered CPE.
It is important to note that the filing of supplemental information does not guaranty that the FCC will grant you protected status. Rather, those applications that pass all validation criteria in ULS will automatically be accepted. If any responses require explanation, or the application does not pass the automatic validation, ULS will change the application status from “saved” to “submitted” at which time the application will be reviewed by the FCC’s staff. A base station will only be entitled to grandfathered protection if the protection zone application has been accepted by the FCC. If further information is needed by the FCC, such information must be submitted in the form of an amendment no later than the August 7, 2017 filing deadline. BloostonLaw Contacts: John Prendergast and Richard Rubino FCC Wireless Buildout “Reminder” May Signal Tougher Enforcement AheadThe FCC’s Wireless Bureau this week issued a Public Notice (DA 17-573) reminding licensees of their construction and coverage obligations, and of the high hurdle they face when seeking to extend their construction deadlines. The PN goes to great lengths in explaining the policies that underlie the Commission’s buildout rules, and may signal more of a “get tough” attitude by the Bureau towards its review of buildout showings and related enforcement matters going forward, especially those involving rural and underserved areas. As a matter of policy, the FCC’s construction obligations ensure that scarce spectrum resources are put to use and developed in a manner that serves all communities. Service-specific rules and a licensee’s FCC authorization describe when and how wireless licensees must construct, commence service, and, as applicable, meet coverage and substantial service benchmarks. With that said, this week’s “reminder” highlights the wording of Rule Section 1.946, which specifies that a licensee’s authorization terminates automatically (in whole or in part as set forth in the service rules) without specific Commission Action if a licensee fails to commence service or operations by the expiration of its construction period. With respect to extensions, the FCC has always expected that licensees conduct due diligence to assure they can timely construct their systems and adequately meet their service requirements. The Commission does not look favorably upon extension requests that cite miscalculations or erroneous predictions about factors such as costs, demand, developments in the market, or timing and success in obtaining permissions that may be needed for construction. Section 1.946 (e) of the Commission’s Rules specifies just two situations that permit an extension — either “involuntary loss of site” or “other causes beyond [a licensee’s] control.” This rule also cautions that extension requests will not be granted for failure to meet a deadline due to delays caused by a failure to obtain financing, to obtain an antenna site, or to order equipment in a timely manner. Our clients should expect the Commission to carefully examine their claims that failures to meet construction requirements were due to causes beyond their control. This stricter scrutiny means that a failed marketplace for a particular technology or spectrum — circumstances that led the FCC to grant extensions for 218-219 MHz (IVDS), 220 MHz, LMDS and MMDS licensees – will no longer be seen as an excuse. Neither will the market’s failure to accommodate a licensee’s specific business plan, such as in the event of a general economic downturn or delays given the type of technology a licensee has chosen. Moreover, a licensee’s own choice regarding which technology to support or whether any equipment is even worth deploying will generally not suffice to warrant an extension. Even where compelling circumstances may exist, the FCC has denied extension requests that are filed at the last minute, or those that reflect a lack of substantial progress by the licensee. Our firm’s wireless clients
therefore will not want to rely on the possibility of a waiver or extension of their construction/service
requirements, to begin their system planning and construction well before the applicable deadlines, and to maintain detailed records of their efforts. These records will be important to establishing that a buildout failure BloostonLaw Contacts: John Prendergast, Cary Mitchell FCC Releases Updated List of Census Blocks Eligible for CAF Phase II Support, Other Updates• On June 8, the FCC’s Wireline Competition Bureau announced the release of an updated list of census blocks eligible for Connect America Phase II support in states where price cap carriers accepted the statewide offers of model-based Connect America Phase II support. The FCC also asked ROR carriers to identify, by July 7, 2017, those census blocks where they do not anticipate being able to extend broadband under the reasonable request standard, so these blocks can be included in the Phase II auction. Specifically, the FCC:
The FCC is also seeking input in the following three categories of census blocks, by July 7, 2017:
A copy of the updated list is available at https://apps.fcc.gov/edocs_public/attachmatch/DOC-345242A1.xlsx. The high-cost blocks eligible for Phase II model support are identified on the list as HC; the extremely high-cost blocks are identified as EHC; and the unclaimed blocks are identified in column H with the number one. BloostonLaw Contacts: Ben Dickens, Gerry Duffy, Mary Sisak, and Sal Taillefer. President Trump to Nominate Jessica Rosenworcel as FCC CommissionerLate in the day on June 13, President Trump nominated Jessica Rosenworcel to again serve as a Commissioner at the FCC. According to Reuters, industry and congressional officials also expect Trump to nominate Brendan Carr, a Republican who is currently general counsel at the FCC and an adviser to Pai, to the last open seat on the Commission. As we have reported in previous editions of the BloostonLaw Telecom Update, the once-and-future Commissioner’s road has been a long one. President Obama nominated Commissioner Rosenworcel for her second term back in May of 2015, but objections by several Republican Senators kept her confirmation in limbo until her first term expired in December of 2016 — more than a year later. Republicans had previously stated that Commissioner Rosenworcel would not be confirmed unless then-Chairman Tom Wheeler agreed to resign. When Wheeler finally made that commitment to Senate Minority Leader Harry Reid, it was apparently late, and the Senate adjourned the last session of that Congress without confirming Rosenworcel’s seat. In a statement, current Chairman Ajit Pai said, ““I congratulate Jessica Rosenworcel on the announcement that President Trump will nominate her to serve another term on the Federal Communications Commission. She has a distinguished record of public service, including the four-and-a-half years we worked together at this agency, and I look forward to working with her once again to advance the public interest.” BloostonLaw Contacts: Ben Dickens and Gerry Duffy. Law & RegulationFCC Reminds MVPDs of July 10 Deadline to Pass Through Emergency InformationOn June 8, the FCC’s Consumer & Governmental Affairs Bureau issued a Public Notice reminding multichannel video programming distributors (MVPDs) of their upcoming obligation to pass through a secondary audio stream containing audible emergency information, when they permit consumers to access linear programming on second screen devices over the MVPD’s network as part of their MVPD services. The compliance deadline for this requirement is July 10. Specifically, each MVPD must ensure that any application or plug-in that it provides to consumers to access linear programming (i.e., programming that is pre-scheduled by the MVPD) on tablets, smartphones, laptops, and similar devices over the MVPD’s network as part of its MVPD services is capable of passing through an aural representation of the emergency information on a secondary audio stream. For purposes of these rules, linear programming is accessed over the MVPD’s network if it can only be received via a connection provided by the MVPD using an MVPD-provided application or plug-in. This is distinguishable from video programming provided over the Internet, which can be accessed by an MVPD subscriber using either an MVPD-provided connection, or a third-party Internet service provider or broadband connection. Companies with questions about the accessible emergency information rules should feel free to contact the firm for more information. BloostonLaw Contacts: Gerry Duffy and Sal Taillefer. Comment Deadline Established for Local Service Rate Floor Comments Due July 10On June 8, the FCC published its Notice of Proposed Rulemaking on eliminating the local service rate floor in the Federal Register. Accordingly, comments are due July 10 and reply comments are due July 24. In the NPRM, the FCC seeks comment on whether it should change the current rate floor methodology or eliminate the rate floor and its accompanying reporting obligation entirely. The FCC asks whether it should allow carriers to charge a rate that is one standard deviation below the average urban rate; or replace the single, national rate floor with state or regional rate floors; or even eliminate the rate floor altogether? BloostonLaw Contacts: Ben Dickens, Gerry Duffy, and Mary Sisak. Industry$280 Million Civil Penalty Awarded Against Dish Network for Do Not Call ViolationsOn June 6, the Federal Trade Commission (FTC) announced that the U.S. District Court for the Central District of Illinois found Dish Network liable for millions of calls that violated the FTC’s Telemarketing Sales Rule (TSR) — including Do Not Call (DNC), entity-specific, and abandoned-call violations -- the Telephone Consumer Protection Act (TCPA), and state law. The civil penalty award includes $168 million for the federal government, which is a record in a DNC case. The remainder of the civil penalty was awarded to the states. The complaint counts relating to the TSR alleged that Dish initiated, or caused a telemarketer to initiate, outbound telephone calls to phone numbers on the DNC Registry, in violation of the TSR, violated the TSR’s prohibition on abandoned calls, and assisted and facilitated telemarketers when it knew, or consciously avoided knowing, that the telemarketer was engaged in violations of the law. Dish markets its programming directly, through telemarketing vendors it contracts with to engage in telemarketing, and through authorized dealers or retailers. The court opinion ruled in favor of the federal government on all of the TSR counts in the complaint, and found more than 66 million TSR violations. In awarding the civil penalty amount, the court found that Dish’s culpability for the violations was significant. In particular, the court stated that, “Dish has some level of culpability for its direct marketing and a significantly higher level of culpability for the illegal calls made through its Order Entry program.” The court also stated that, “Dish initially hired Order Entry Retailers based on one factor, the ability to generate activations. Dish cared about very little else. As a result, Dish created a situation in which unscrupulous sales persons used illegal practices to sell Dish Network programming any way they could.” According to court filings, Dish authorized Order Entry Retailers to market Dish Network programming nationally Dish would then complete the sale provide for the delivery and installation of the satellite dish and related equipment, and provide the programming.” DeadlinesJULY 3: FCC FORM 481 (CARRIER ANNUAL REPORTING DATA COLLECTION FORM). All eligible telecommunications carriers (ETCs) must report the information required by Section 54.313, which includes outage, unfulfilled service request, and complaint data, broken out separately for voice and broadband services, information on the ETC’s holding company, operating companies, ETC affiliates and any branding in response to section 54.313(a)(8); its CAF-ICC certification, if applicable; its financial information, if a privately held rate-of-return carrier; and its satellite backhaul certification, if applicable. Form 481 must not only be filed with USAC, but also with the FCC and the relevant state commission and tribal authority, as appropriate. Although USAC treats the filing as confidential, filers must seek confidential treatment separately with the FCC and the relevant state commission and tribal authority if confidential treatment is desired. BloostonLaw Contacts: Ben Dickens, Gerry Duffy, and Sal Taillefer. JULY 3: MOBILITY FUND PHASE I ANNUAL REPORT. Winning bidders in Auction 901 that are authorized to receive Mobility Fund Phase I support are required to submit to the FCC an annual report each year on July 1 for the five years following authorization. This year, July 1 falls on a Saturday; therefore, the report is due July 3. Each annual report must be submitted to the Office of the Secretary of the FCC, clearly referencing WT Docket No. 10-208; the Universal Service Administrator; and the relevant state commissions, relevant authority in a U.S. Territory, or Tribal governments, as appropriate. The information and certifications required to be included in the annual report are described in Section 54.1009 of the FCC’s rules. BloostonLaw Contacts: John Prendergast and Sal Taillefer. JULY 31: FCC FORM 507, UNIVERSAL SERVICE QUARTERLY LINE COUNT UPDATE. Line count updates are required to recalculate a carrier's per line universal service support, and is filed with the Universal Service Administrative Company (USAC). This information must be submitted on July 31 each year by all rate-of-return incumbent carriers, and on a quarterly basis if a competitive eligible telecommunications carrier (CETC) has initiated service in the rate-of-return incumbent carrier’s service area and reported line count data to USAC in the rate-of-return incumbent carrier’s service area, in order for the incumbent carrier to be eligible to receive Interstate Common Line Support (ICLS). This quarterly filing is due July 31 and covers lines served as of December 31, 2013. Incumbent carriers filing on a quarterly basis must also file on September 30 (for lines served as of March 31, 2014); December 30 (for lines served as of June 30, 2014), and March 31, 2015 (for lines served as of September 30, 2014). BloostonLaw Contacts: Ben Dickens, Gerry Duffy, and Mary Sisak. JULY 31: CARRIER IDENTIFICATION CODE (CIC) REPORTS. Carrier Identification Code (CIC) Reports must be filed by the last business day of July (this year, July 31). These reports are required of all carriers who have been assigned a CIC code by NANPA. Failure to file could result in an effort by NANPA to reclaim it, although according to the Guidelines this process is initiated with a letter from NANPA regarding the apparent non-use of the CIC code. The assignee can then respond with an explanation. (Guidelines Section 6.2). The CIC Reporting Requirement is included in the CIC Assignment Guidelines, produced by ATIS. According to section 1.4 of that document: At the direction of the NANPA, the access providers and the entities who are assigned CICs will be requested to provide access and usage information to the NANPA, on a semi-annual basis to ensure effective management of the CIC resource. (Holders of codes may respond to the request at their own election). Access provider and entity reports shall be submitted to NANPA no later than January 31 for the period ending December 31, and no later than July 31 for the period ending June 30. It is also referenced in the NANPA Technical Requirements Document, which states at 7.18.6: CIC holders shall provide a usage report to the NANPA per the industry CIC guidelines … The NAS shall be capable of accepting CIC usage reports per guideline requirements on January 31 for the period ending December 31 and no later than July 31 for the period ending June 30. These reports may also be mailed and accepted by the NANPA in paper form. Finally, according to the NANPA website, if no local exchange carrier reports access or usage for a given CIC, NANPA is obliged to reclaim it. The semi-annual utilization and access reporting mechanism is described at length in the guidelines. BloostonLaw contacts: Ben Dickens and Gerry Duffy. Calendar At-A-GlanceJune July August
|
Extreme : Grows with Avaya Networking Acquisition06/13/2017 | 08:22am EST In an outcome that was unsurprising for most, Extreme Networks emerged as the winning bidder for the Avaya enterprise networking business. It will be moving ahead with the $100 million acquisition of the unit following the firms filing for Chapter 11 bankruptcy in January (2017). Avaya originally purchased its networking business from the former giant in the sector, Nortel, in 2009. The acquisition came in similar circumstances to the ones that Avaya are facing now. After all, the purchase was made when Nortel fell into bankruptcy and was forced to shed a great deal of its business throughout a serious of auctions. The Avaya Restructuring Opportunity Avaya declared bankruptcy in an attempt to give itself more time to restructure and support its balance sheet. According to Kevin Kennedy, the CEO of the brand, Avaya believes that selling their networking business is the best way to move forward. They feel that this step gives them a positive path for all networking partners, and enables them to focus on their UC and contact centre solutions.
According to Extreme Networks president & CEO, Ed Meyercord, the recent acquisition will help the growing company to establish itself as a major competitor in the world of enterprise networking. Extreme believes that the Avaya business has the potential to generate astonishing revenues of around $200 million every year. This will add to several recent acquisitions that have helped the firm to continue its expansion. Not the First Acquisition for Extreme In 2016, Extreme Networks purchased the Zebra wireless local area network business for $55 million. Recently in this year, it also purchased the Brocade data centre networking assets after the company's new owner, Broadcom revealed that they were only interested in the storage elements of the business. While the assets obtained from Zebra are expected to deliver about $115 in revenues to Extreme Networks, Brocades are projected to deliver over $200 million during Extremes financial year in 2018, which will begin on the first of July this year. According to Meyercord, the purchase of Avayas networking business will complement the company's existing portfolio and help to broaden their range of enterprise solutions and capabilities across their target markets. The brand is currently moving forward with integration planning for both the Brocade data centre business and Avaya networking business. (c) All KUNA right are reserved 2017. Provided by SyndiGate Media Inc. (Syndigate.info)., source Middle East & North African Newspapers |
Source: | 4-traders |
Friends & Colleagues |
|
|||||||||||||
|
Wireless Network Planners
|
LETTERS TO THE EDITOR |
Dear Brad, I hope all is well on your end. It’s always a pleasure to read your newsletter. Pls. find attached a nice story on a European major network operator that compares POCSAG with TETRA Alerting. Could this eventually be of interest to your readership? We’re also finalizing a substantial whitepaper and video on this topic. Would you be open that I share them with you for your consideration once they’re ready? I wish you a nice weekend and look forward to hearing from you. Best regards,
|
|
THOUGHT FOR THE WEEK |
VIDEO OF THE WEEK |
|
Source: | YouTube |
![]() |
Home Page | Directory | Consulting | Newsletters | Free Subscription | Products | Reference | Glossary | Send e-mail |