Silence Indication Via Explicit Notification Sample Clauses

Silence Indication Via Explicit Notification. Silence may also be indicated by sending one or more packets containing noise parameters during silence periods. This approach uses the RTP payload type transition from a speech coder to an alternate 'noise' coder to indicate the speech to silence transition, and allows multiple packets of the alternate 'noise' coder type to be sent during a given silent period. This VoIP IA has defined only one of a number of possible noise information transmission schemes. This scheme, based on G.764 absolute noise level indexing, has been allocated the dynamic RTP payload type 120. This method transmits absolute level noise information in a single byte payload, which should be transmitted immediately after the last speech packet of a speech burst. Additional noise packets with updates to the noise level may be sent during long silence periods if desired. Other noise information transmission schemes may be included in later versions of the VoIP IA and assigned to other dynamically allocated RTP payload types. Redundancy of noise information packets is not considered important in the G.764 method, as the loss of noise information packets will, in the worst case, cause nothing more than a default to the 'Silence Indication Via Receive Underrun Conditions' case. For baseline compatibility, receivers must at minimum throw away silence packets of payload type 120 without causing a functional disruption in other aspects of operation.
Sample 1
AutoNDA by SimpleDocs

Related to Silence Indication Via Explicit Notification

  • Development Plan document specifying the work program, schedule, and relevant investments required for the Development and the Production of a Discovery or set of Discoveries of Oil and Gas in the Concession Area, including its abandonment.

  • Development Schedule The Project shall substantially comply with the specific timetables and triggers for action set forth in Article 5 of this Agreement. The parties acknowledge that, as provided in G.S. 160A-400.25(b), the failure to meet a commencement or completion date shall not, in and of itself, constitute a material breach of this Agreement pursuant to G.S. 160A-400.27 but must be judged based upon the totality of the circumstances.

  • MSAA Indicator Technical Specification Document This Agreement shall be interpreted with reference to the MSAA Indicator Technical Specifications document.

  • Unauthorized Access Notification XXX shall notify Provider promptly of any known unauthorized access. XXX will assist Provider in any efforts by Provider to investigate and respond to any unauthorized access.

  • Network Access Control The VISION Web Site and the Distribution Support Services Web Site (the “DST Web Sites”) are protected through multiple levels of network controls. The first defense is a border router which exists at the boundary between the DST Web Sites and the Internet Service Provider. The border router provides basic protections including anti-spoofing controls. Next is a highly available pair of stateful firewalls that allow only HTTPS traffic destined to the DST Web Sites. The third network control is a highly available pair of load balancers that terminate the HTTPS connections and then forward the traffic on to one of several available web servers. In addition, a second highly available pair of stateful firewalls enforce network controls between the web servers and any back-end application servers. No Internet traffic is allowed directly to the back-end application servers. The DST Web Sites equipment is located and administered at DST’s Winchester data center. Changes to the systems residing on this computer are submitted through the DST change control process. All services and functions within the DST Web Sites are deactivated with the exception of services and functions which support the transfer of files. All ports on the DST Web Sites are disabled, except those ports required to transfer files. All “listeners,” other than listeners required for inbound connections from the load balancers, are deactivated. Directory structures are “hidden” from the user. Services which provide directory information are also deactivated.

  • Originating Switched Access Detail Usage Data A category 1101XX record as defined in the EMI Telcordia Practice BR-010-200- 010.

  • Commercialization Plan (a) Not later than three [***] after submission of Regulatory Filings for each Product in each country of the Territory, Licensee will provide to the JCC for review its initial Commercialization Plan for each Product for each country in the Territory. Such initial Commercialization Plan will describe Licensee’s plans for activities to be conducted for such Product for such country. Each Commercialization Plan shall include the details of obligations to be performed by Licensee to achieve the specific activities that are applicable to the stage of [***] Certain information in this document has been omitted and filed separately with the Securities and Exchange Commission. Confidential treatment has been requested with respect to the omitted portions. Commercialization (e.g., pre-launch, launch planning, launch, or post-launch) of the applicable Product during the time period covered by such Commercialization Plan and subsequent time periods. (b) Prior to the First Commercial Sale for such Product in such country, Licensee will provide to the JCC for review an updated Commercialization Plan for such Product for such country. Such updated Commercialization Plan will include, but not be limited to, Licensee’s updated plans for activities to be conducted for such Product for such country prior to launch as well as activities to be conducted in connection with such launch. (c) Promptly after each anniversary of the First Commercial Sale of such Product during the Term, Licensee will provide to the JCC for review updated Commercialization Plans for such Product for such country. Such further updated Commercialization Plan will include, but not be limited to, Licensee’s plans for Commercialization activities for such Product and such country for the twelve (12) month period following the date of delivery of such Commercialization Plan. No Commercialization Plan may be implemented by Licensee if [***]. Each Commercialization Plan shall be consistent with and shall not contradict the terms of this Agreement [***], and in the event of any inconsistency between the Commercialization Plan and this Agreement, the terms of this Agreement shall prevail. Notwithstanding the foregoing, if a [***], Licensee shall [***] and shall promptly [***].

  • Review Protocol A narrative description of how the Claims Review was conducted and what was evaluated.

  • Protocol The attached Protocol shall be an integral part of this Agreement.

  • Statement of Work The Statement of Work to which Grantee is bound is incorporated into and made a part of this Grant Agreement for all purposes and included as Attachment A.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!