Request-URI Sample Clauses

Request-URI. The Request-URI of the INVITE sent to the Media Resource Broker indicates the media resources being requested. The MRB MUST support the annc, conf and dialog resources defined in RFC4240. For conf allocations then all concurrently active sessions with the same conference id value will be allocated to the same physical media server. It is the responsibility of the sending client to ensure all requests sharing the same conference-id are directed to the same Media Resource Broker instance. The following additional parameters MAY be included in the Request-URI to further influence the action of the Media Resource Broker. br-conf-size = <n> This parameter is used in conjunction with the conf= Request-URI (from RFC4240) in order to instruct the Media Resource Broker the ultimate size of the conference being requested so an appropriate number of ports can be reserved. This parameter is not propagated to the Media Server itself. br-affinity = <unique id> This parameter can be used to indicate to the Media Resource Broker that multiple requests should be allocated to the same physical Media Server. All concurrently active sessions that share the same unique id should be resolved to the same physical Media Server. This parameter is redundant for conf allocations and is not propagated to the Media Server itself. It is the responsibility of the client issuing the request to ensure both the uniqueness of the <unique id> and to ensure that all requests using the same <unique id> are directed to the same Media Resource Broker instance. br-mrid= <media server id> This parameter can be used to indicate a request for a specific media server (identified by the <media server id>). How Media Servers are identified through the Media Server Id is left to individual implementations. The parameter is not propagated to the Media Server itself. br-capabilities=<comma separated list of capabilities> This parameter allows the definition of custom media capabilities. When custom capabilities are used then the Media Resource Broker must be configured with the capabilities supported by each Media Server under its allocation control. The request will be resolved to a Media Server supporting all the requested custom capabilities, if not all the capabilities can be supported then the request is rejected. The parameter is not propagated to the Media Server itself.
Sample 1
AutoNDA by SimpleDocs
Request-URI. The Request-URI of the REGISTER MUST contain the SIP URI of the AS or SB / SCIM (the S-CSC obtains this from the iFC of the subscribers service profile).
Sample 1
Request-URI. The Request-URI is set to the resource that the Application Server is subscribing to, i.e. the public user identity of the user that was received in the To header of the secondary REGISTER.
Sample 1
Request-URI. The Request-URI in the SIP INVITE returned/ propagated back from the Application Server will contain the destination party address. The Application Server may, as part of the service it is providing, have modified this destination party address. If the propagated INVITE contains a different destination address than the INVITE sent to the Application Server, and the Application Server was invoked for terminating services then. ⮚ If the propagated INVITE is received by the SB/SCIM it will not engage any further applications for the original terminating user and will immediately propagate the INVITE with the new destination party address back to the S-CSC. ⮚ If the propagated INVITE is received by the S-CSC then it will not engage any further applications for the original terminating user. o If the new destination address is registered on the S-CSC then it will check the service profile to determine if any terminating services need to be invoked for the subscriber identified by new destination address. o If the new destination address is not registered on the S-CSC then it performs originating side session routing and forwards the INVITE on to the S-CSC handling the registration of the subscriber identified in the new destination address, or in the case of the subscriber not being registered an appropriate S-CSC.
Sample 1

Related to Request-URI

  • Request for Proposal Once the project development stage and joint scope meeting have produced a County approved Detailed Scope of Work, the County will issue a Request for Proposal (RFP) to the Contractor. The RFP will include the Scope of Work approved by the County and other pertinent information with regards to scheduling, submittals, shop drawings and sketch requirements. The Contractor agrees to prepare and submit a JOC Task Order Proposal of Work.

  • Request for Proposals A State request inviting proposals for Goods or Services. This Contract shall be governed by the statutes, regulations and procedures of the State of Connecticut, Department of Administrative Services.

  • Bona Fide Request (BFR) The process described in the UNE Attachment that prescribes the terms and conditions relating to a Party's request that the other Party provides a UNE that it is not otherwise required to provide under the terms of this Agreement.

  • Request A request to submit a grievance to arbitration must be in writing, signed by the aggrieved party, and such request must be filed in the office of the Superintendent within ten (10) days following the decision in Level III of the grievance procedure.

  • Request for clarification of the report 1. Within 10 days of the release of the report, either of the disputing Parties may submit a written request to the Panel, a copy of which shall be sent to the other Party, for clarification of any items the Party considers requires further explanation or definition. 2. The Panel shall respond to the request within 10 days following the submission of such request. The clarification of the Panel shall only be a more precise explanation or definition of the original contents of the report, and not an amendment of such report. 3. The filing of this request for clarification will not postpone the effect of the Panel report nor the deadline for compliance of the adopted decision, unless the Panel decides otherwise.

  • Bona Fide Request/New Business Request Process for Further Unbundling 6.1 BellSouth shall, upon request of <<customer_name>>, provide to <<customer_name>> access to its network elements at any technically feasible point for the provision of <<customer_name>>'s telecommunications service where such access is necessary and failure to provide access would impair the ability of <<customer_name>> to provide services that it seeks to offer. Any request by <<customer_name>> for access to a network element, interconnection option, or for the provisioning of any service or product that is not already available shall be treated as a Bona Fide Request/New Business Request (BFR/NBR), and shall be submitted to BellSouth pursuant to the BFR/NBR process.

  • BONA FIDE REQUEST PROCESS 42.1. Embarq shall promptly consider and analyze CLEC requests for unbundled Network Elements that are not currently developed by Embarq, network information that is reasonably required to determine what unbundled Network Elements it needs to serve a particular customer or development of and changes to Embarq work processes related to ordering, provisioning or installation of unbundled Network Elements with the submission of a Bona Fide Request (“BFR”) hereunder.

  • HOW TO REQUEST SERVICE Do not return the Covered Product to the Selling Retailer where You purchased the Covered Product. Contact the Administrator and You will be advised on how to obtain a replacement product. • Call the toll-free number at 877.634.0964 or go online to xxx.xxxxxxxxx.xxx. • You may be required to provide the original sales receipt in order for a claim to be processed. Products found to be non-defective will be returned to You. You are responsible for all costs of postage, insurance, packaging and shipping. Please make sure the Covered Product is properly protected with bubble wrap or other protective materials. A replacement product will not be provided if the Covered Product is damaged during shipping and it is determined that no valid claim existed prior to shipping.

  • Request for Hearing The employee must file a written request for hearing within fifteen calendar days of receipt of the Notice of Dismissal or Suspension. Filing means receipt in the office designated no later than regular close of business on the last day of the filing period. Failure to file such request in a timely manner shall be deemed a waiver of the right to a hearing and the proposed action shall be effective upon action by the Governing Board without notice or hearing except as may be required in a board meeting agenda.

  • Information Request (a) The Owner Trustee shall provide any information regarding the Issuer in its possession reasonably requested in writing by the Servicer, the Administrator, the Seller or any of their Affiliates, in order to comply with or obtain more favorable treatment under any current or future law, rule, regulation, accounting rule or principle.

Time is Money Join Law Insider Premium to draft better contracts faster.