SIP Request Headers Sample Clauses

SIP Request Headers. All SIP requests shall support the following headers :- REQ-URI, TO, FROM, CALL-ID, CSEQ & CONTENT-LENGTH. In addition, the following table describes the salient headers which are supported in the various requests:- Content Type C O O O O M M Contact M O O N/A N/A O N/A Supported M N/A O O O O N/A Rack N/A N/A M N/A N/A N/A N/A Require M N/A N/A N/A N/A N/A N/A Content Disposition C N/A N/A N/A N/A N/A M Record Route M N/A N/A N/A N/A N/A N/A Route O O N/A O O O O Session Expires O N/A N/A N/A N/A N/A O Min-SE O N/A N/A N/A N/A N/A N/A Allow M (note) N/A N/A N/A N/A N/A N/A Resource Priority O O O O O O O Accept Resource Priority O O O O O O O Note – Used to advertise support of UPDATE. Key :- M – Mandatory, O – Optional, C – Conditional (i.e. if message body not empty, then M), N/A – Not applicable. Embedded ISUP messages may be present in the following Methods :- INVITE IAM Always present. ACK None Never present BYE REL Always present CANCEL REL Always present PRACK None PRACK used to acknowledge early bearer info (e.g. in 18X). INFO RES, SUS UPDATE None UPDATE used for mid call bearer change or session timer update. None ▇▇▇ ▇/A since en-bloc working assumed.
SIP Request Headers. All SIP requests shall support the following headers :- REQ-URI, TO, FROM, CALL-ID, CSEQ & CONTENT-LENGTH. In addition, the following table describes the salient headers which are supported in the various requests:-

Related to SIP Request Headers

  • When Must Electronic Communications Be Retained? Email that qualifies under FOIA as a public record will need to be stored pursuant to the Local Records Act (LRA), only if it is evidence of the District's organization, function, policies, procedures, or activities or contains informational data appropriate for preservation. 50 ILCS 205/. An example is any email from a Board officer concerning a decision made in his or her capacity as an officer. If a Board member uses his or her personal email, he or she must copy this type of email to the appropriate District office where it will be stored. If made available, Board members should use their email accounts provided by the District, and the District will automatically store the official record messages. The District will delete these official record messages as provided in an applicable, approved retention schedule. Of course, email pertaining to public business that is sent or received by a Board Member using a District-issued device or email address will be subject to FOIA, even if the email does not need to be retained under the LRA.

  • Posting of Approved Electronic Communications (a) Each of the Agents, the Lenders, the Issuers and Group and the Borrower agree, and Group shall cause each other Loan Party to agree, that the Administrative Agent and the Collateral Agent may, but shall not be obligated to, make the Approved Electronic Communications available to the Lenders and Issuers by posting such Approved Electronic Communications on IntraLinks™ or a substantially similar electronic platform chosen by the Facility Agents to be their electronic transmission system (the “Approved Electronic Platform”). (b) Although the Approved Electronic Platform and its primary web portal are secured with generally-applicable security procedures and policies implemented or modified by the Facility Agents from time to time (including, as of the Closing Date, a dual firewall and a User ID/Password Authorization System) and the Approved Electronic Platform is secured through a single-user-per-deal authorization method whereby each user may access the Approved Electronic Platform only on a deal-by-deal basis, each of the Lenders, the Issuers, Group and the Borrower acknowledges and agrees, and Group shall cause each other Loan Party to acknowledge and agree, that the distribution of material through an electronic medium is not necessarily secure and that there are confidentiality and other risks associated with such distribution. In consideration for the convenience and other benefits afforded by such distribution and for the other consideration provided hereunder, the receipt and sufficiency of which is hereby acknowledged, each of the Facility Agents, the Lenders, the Issuers, Group and the Borrower hereby approves, and Group shall cause each other Loan Party to approve, distribution of the Approved Electronic Communications through the Approved Electronic Platform and understands and assumes, and Group shall cause each other Loan Party to understand and assume, the risks of such distribution. (c) THE APPROVED ELECTRONIC PLATFORM AND THE APPROVED ELECTRONIC COMMUNICATIONS ARE PROVIDED “AS IS” AND “AS AVAILABLE”. NONE OF THE FACILITY AGENTS OR ANY OF THEIR AFFILIATES OR ANY OF THEIR RESPECTIVE OFFICERS, DIRECTORS, EMPLOYEES, AGENTS, ADVISORS OR REPRESENTATIVES (THE “AGENT AFFILIATES”) WARRANT THE ACCURACY, ADEQUACY OR COMPLETENESS OF THE APPROVED ELECTRONIC COMMUNICATIONS OR THE APPROVED ELECTRONIC PLATFORM AND EACH EXPRESSLY DISCLAIMS LIABILITY FOR ERRORS OR OMISSIONS IN THE APPROVED ELECTRONIC PLATFORM AND THE APPROVED ELECTRONIC COMMUNICATIONS. NO WARRANTY OF ANY KIND, EXPRESS, IMPLIED OR STATUTORY, INCLUDING, WITHOUT LIMITATION, ANY WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, NON-INFRINGEMENT OF THIRD PARTY RIGHTS OR FREEDOM FROM VIRUSES OR OTHER CODE DEFECTS, IS MADE BY ANY OF THE AGENT AFFILIATES IN CONNECTION WITH THE APPROVED ELECTRONIC PLATFORM OR THE APPROVED ELECTRONIC COMMUNICATIONS. (d) Each of the Lenders, the Issuers, Group and the Borrower agrees, and Group shall cause each other Loan Party to agree, that each Facility Agent may, but (except as may be required by applicable law) shall not be obligated to, store the Approved Electronic Communications on the Approved Electronic Platform in accordance with such Agent’s generally-applicable document retention procedures and policies.

  • Implementation Report Within 150 days after the Effective Date, Ensign Group shall submit a written report to OIG summarizing the status of its implementation of the requirements of this CIA (Implementation Report). The Implementation Report shall, at a minimum, include: 1. the name, address, phone number, and position description of the Compliance Officer required by Section III.A, and a summary of other noncompliance job responsibilities the Compliance Officer may have; 2. the names and positions of the members of the Compliance Committee required by Section III.A; 3. the names and positions of the members of the Board of Directors who are responsible for satisfying the Board of Directors compliance obligations described in Section III.A.3; 4. a copy of Ensign Group’s Code of Conduct required by Section III.B.1; 5. the number of individuals required to complete the Code of Conduct certification required by Section III.B.1, the percentage of individuals who have completed such certification, and an explanation of any exceptions (the documentation supporting this information shall be available to OIG upon request); 6. a summary of all Policies and Procedures required by Section III.B (copies of the Policies and Procedures shall be made available to OIG upon request); 7. the following information regarding each type of training required by Section III.C: a. a description of such training, including a summary of the topics covered, the length of sessions, and a schedule of training sessions; b. the number of individuals required to be trained, percentage of individuals actually trained, and an explanation of any exceptions. A copy of all training materials and the documentation supporting this information shall be made available to OIG upon request. 8. a description of the Disclosure Program required by Section III.E; 9. the following information regarding the IRO(s): (a) identity, address, and phone number; (b) a copy of the engagement letter; (c) information to demonstrate that the IRO has the qualifications outlined in Appendix A to this CIA; (d) a summary and description of any and all current and prior engagements and agreements between Ensign Group and the IRO; and (e) a certification from the IRO regarding its professional independence and objectivity with respect to Ensign Group; 10. a description of the process by which Ensign Group fulfills the requirements of Section III.F regarding Ineligible Persons; 11. a list of all of Ensign Group’s locations (including locations and mailing addresses); the corresponding name under which each location is doing business; the corresponding phone numbers and fax numbers; each location’s Medicare and state Medicaid program provider number and/or supplier number(s); and the name and address of each Medicare and state Medicaid program contractor to which Ensign Group currently submits claims; 12. a description of Ensign Group’s corporate structure, including identification of any parent and sister companies, subsidiaries, and their respective lines of business; and

  • Checks, Drafts, etc All checks, drafts or other orders for payment of money, notes or other evidences of indebtedness, issued in the name of or payable to the Company, shall be signed or endorsed by such person or persons and in such manner as shall be determined from time to time by resolution of the Board.

  • Board Member Use of Electronic Communications For purposes of this section, electronic communications includes, without limitation, electronic mail, electronic chat, instant messaging, texting, and any form of social networking. Electronic communications among a majority or more of a Board-quorum shall not be used for the purpose of discussing District business. Electronic communications among Board members shall be limited to: