INVITE Sample Clauses

INVITE. Supported: 100rel, timer, precondition Session-Expires: 180; refreshor=uac Min-SE: 120 Allow: INVITE, ACK, CANCEL, BYE, PRACK, REFER, UPDATE Contact: <sip:xxxxxxxxx@xxxx.xxxxxxxxxx.xxx> P-Asserted-Id: Major Xxxxxxx <sip:xxxxxxxx@xxxxxxxxxx.xxx> P-Charging-Vector: icid-value=”123456” Require: precondition, 100rel Content-Type: application/sdp Content-Length: XX
Sample 1
AutoNDA by SimpleDocs
INVITE. Support for INVITE is mandatory for both UACs and UASs. The INVITE request is used in many ways: to start a new call, refresh session-timer, reroute (redirect) calls. An INVITE request should have the appropriate headers and may include a SDP body. In case the corresponding INVITE has an SDP body, the ACK should not have an SDP body. The SDP body is necessary for providing early audio. Headers convey specific information about the call such as calling, called party, and the call’s unique identification. Subsequent re-INVITE requests are used to refresh session time, or to change RTP receiving address port and codec. The INVITE request initiates or renegotiates a session may include a SDP body. If originating SIP server does not know its desired characteristic of session until it receives the 200 OK response, the initial INVITE should have not SDP body. In this case the ACK request for this INVITE will contain a SDP body. The INVITE requesting the session-timer refresh requires SDP body. If the INVITE doesn’t contain any SDP, the following ACK shall contain a SDP. It is mandatory for a UAS to support receiving INVITE requests with no SDP body. IPv4 Example: INVITE SIP:0000000000@172.80.2.100:5060 SIP/2.0 Via: SIP/2.0/UDP 172.17.2.29:5060 From: IP30 Phone 1 <SIP:0000000000@172.17.2.29>;tag=949D.80A7 To: <SIP:0000000000@172.20.2.31> Call-ID: 0000.00XX.A152.3C44.949D.80A7@172.17.2.29 CSeq: 21479 INVITE Content-Length: 148 Content-Type: application/sdp Contact: SIP:0000000000@172.17.2.29 Session-Expires: 120 Supported: timer, 100rel v=0 o=- 7323 3661 IN IP4 172.17.2.29 s=- SIP Call c=IN IP4 12.0.0.102 t=0 0 m=audio 9000 RTP/AVP 0 18 a=ptime:20 a=sendrecv IPv6 Example: INVITE SIP:0000000000@[3ffe:302:feed:ffff::d49d:cdce]:5060 SIP/2.0 Via: SIP/2.0/UDP [3ffe:302:feed:beef:208:74ff:fee1:d3ca]:5060 From: IP30 Phone 1 <SIP:0000000000@[3ffe:302:feed:ffff::d49d:cdce]>;tag=949D.80A7 To: <SIP:0000000000@[3ffe:302:feed:ffff::d49d:cdce]> Call-ID: 0000.00XX.A152.3C44.949D.80A7@[3ffe:302:feed:beef:208:74ff:fee1:d3ca] CSeq: 21479 INVITE Content-Length: 148 Content-Type: application/sdp Contact: SIP:0000000000@[3ffe:302:feed:beef:208:74ff:fee1:d3ca] Session-Expires: 120 Supported: timer, 100rel v=0 o=- 7323 3661 IN IP6 3ffe:302:feed:beef:208:74ff:fee1:d3ca s=- SIP Call c=IN IP6 3ffe:302:feed:beef:208:74ff:fee1:d3ca t=0 0 m=audio 9000 RTP/AVP 0 18 a=ptime:20 a=sendrecv
Sample 1
INVITE. The figure below shows two applications Foo and Bar being invoked for the terminating party via the SB/SCIM. Both of the application servers (acting as either proxies or B2BUA’s) propagate the SIP INVITE back to the SB/SCIM. INVITE INVITE Figure 3 - Invocation of Applications via SB/SCIM
Sample 1
INVITE. Supported: 100rel, timer, precondition Session-Expires: 180; refreshor=uac Min-SE: 120 Allow: INVITE, ACK, CANCEL, BYE, PRACK, REFER, UPDATE Contact: <sip:xxxxxxxxx@xxxx.xxxxxxxxxx.xxx> P-Asserted-Id: Major Xxxxxxx <sip:xxxxxxxx@xxxxxxxxxx.xxx> P-Charging-Vector: icid-value=”123456” Require: precondition, 100rel Content-Type: application/sdp Content-Length: XX INVITE from SCIM to Application Server Bar INVITE sip:xxxxxxxx@xxxxxxxxxx.xxx SIP/2.0 Route: <sip: xxxxxxx0@xxx.xxxxxxxxxx.xxx;role=term;lr> Route: <sip:0000000000@xxxx.xxxxxxxxxx.xxx;lr> Record-Route: <sip:xxxxxxxxxxx@xxxx.xxxxxxxxxx.xxx;lr> Via: SIP/2.0/USP xxxx.xxxxxxxxxx.xxx;branch=z9hG4bK7ef4c23456 Max-Forwards: 64 To: Tiny Clanger <sip:xxxxxxxx@xxxxxxxxxx.xxx> From: Major Xxxxxxx <sip:xxxxxxxx@xxxxxxxxxx.xxx>;tag=0000000000 Call-ID: ef4567ef CSeq: 1 INVITE Supported: 100rel, timer, precondition Session-Expires: 180; refreshor=uac Min-SE: 120 Request-Disposition no-fork Allow: INVITE, ACK, CANCEL, BYE, PRACK, REFER, UPDATE Contact: <sip:xxxxxxxx@xxxx.xxxxxxxxxx.xxx> P-Asserted-Id: Major Xxxxxxx <sip:xxxxxxxx@xxxxxxxxxx.xxx> P-Charging-Vector: icid-value=”123456” Require: precondition, 100rel Content-Type: application/sdp Content-Length: XX Propagated INVITE from Application Server Bar to SCIM INVITE sip:xxxxxxxx@xxxxxxxxxx.xxx SIP/2.0 Route: <sip:0000000000@xxxx.xxxxxxxxxx.xxx;lr> Record-Route: <sip:xxxxxxx0000@xxx.xxxxxxxxxx.xxx;lr> Record-Route: <sip:xxxxxxxxxxx@xxxx.xxxxxxxxxx.xxx;lr> Via: SIP/2.0/USP xxx.xxxxxxxxxx.xxx;branch=z9hG4bK7ef4c23986 Via: SIP/2.0/USP xxxx.xxxxxxxxxx.xxx;branch=z9hG4bK7ef4c23456 Max-Forwards: 63 To: Tiny Clanger <sip:xxxxxxxx@xxxxxxxxxx.xxx> From: Major Xxxxxxx <sip:xxxxxxxx@xxxxxxxxxx.xxx>;tag=0000000000 Call-ID: ef4567ef CSeq: 1 INVITE Supported: 100rel, timer, precondition Session-Expires: 180; refreshor=uac Min-SE: 120 Request-Disposition no-fork Allow: INVITE, ACK, CANCEL, BYE, PRACK, REFER, UPDATE Contact: <sip:xxxxxxxxx@xxxx.xxxxxxxxxx.xxx> P-Asserted-Id: Major Xxxxxxx <sip:xxxxxxxx@xxxxxxxxxx.xxx> P-Charging-Vector: icid-value=”123456” Require: precondition, 100rel Content-Type: application/sdp Content-Length: XX INVITE from SCIM to Application Server Baz INVITE sip:xxxxxxxx@xxxxxxxxxx.xxx SIP/2.0 Route: <sip: xxxxxxx0@xxx.xxxxxxxxxx.xxx;role=term;lr> Route: <sip:0000000000@xxxx.xxxxxxxxxx.xxx;lr> Record-Route: <sip:xxxxxxxxxxx@xxxx.xxxxxxxxxx.xxx;lr> Via: SIP/2.0/USP xxxx.xxxxxxxxxx.xxx;branch=z9hG4bK7ef4c23456 Max-Forwards: 62 To: Tiny Clanger <sip:xxxxxxx...
Sample 1
INVITE. Say something of interest about the next session to encourage the students to attend and to invite friends.
Sample 1

Related to INVITE

  • Attend regularly scheduled Project progress meetings and fully advise the Project Team of the Project status including schedule, costs, quality and changes.

  • Representatives for PFA (a) The HSP’s Representative for purposes of this PFA shall be [insert name, telephone number, fax number and e-mail address.] The HSP agrees that the HSP’s Representative has authority to legally bind the HSP.

  • Interview A new employee will have the opportunity to meet with a representative of the Union in the employ of the Hospital for a period of up to minutes during the employee's orientation period without loss of regular earnings. The purpose of the meeting will be to acquaint the employee with such representative of the Union and the collective agreement. Such meetings may be arranged collectively or individually for employees by the Hospital as part of the orientation program." No Other "No employee shall be required or permitted to make any written or verbal agreement with the Hospital or its which conflicts with the terms of this agreement. No individual employee or group of employees shall undertake to represent the union at meetings with the Hospital without proper authorization from the union."

  • Coordinators The contractor shall assign coordinators as needed to coordinate At-Sea Monitor deployment and provide At-Sea Monitor support services. The coordinator shall be designated as key personnel under this contract (per section H.8). All coordinators are required to maintain current At-Sea Monitor Certification. Ensure that all key personnel attend any refresher trainings for At-Sea Monitors. For a specific job description see Section J, Attachment 2, Labor Category Classifications and Job Descriptions.

  • Provide Information Inform FTA immediately of any information it receives from any source alleging a violation of the prohibitions listed in section 4(f)(4) of this Master Agreement; and

  • Obligation to Provide Information Each party’s obligation to provide information shall be as follows:

  • REPRESENTATIVE; ADDRESSES 6.01. The Recipient’s Representative is the Minister of Finance.

  • Visits During all visits by either party to the facilities of the other party, visitors shall comply with all reasonable rules of the host company, and each party to this Agreement will indemnify and hold the other party harmless from any liability, claim or loss whatsoever (i) for any injury to, or, death of, any of its employees or agents while such persons are present at the facility of the other party; and (ii) for any damages to its own property or to the property of any such employee or agent which may occur during the presence of any such person at the facility of the other party, regardless of how such damage occurs.

  • Consultant’s Representative Consultant hereby designates XXXXXX, or his or her designee, to act as its representative for the performance of this Agreement (“Consultant’s Representative”). Consultant’s Representative shall have full authority to represent and act on behalf of the Consultant for all purposes under this Agreement. The Consultant’s Representative shall supervise and direct the Services, using their best skill and attention, and shall be responsible for all means, methods, techniques, sequences, and procedures and for the satisfactory coordination of all portions of the Services under this Agreement.

  • Management Team Subject to any approval or consulting rights of the --------------- Joint Operations Committee, Manager shall engage or designate one or more individuals experienced in dental group management and direction, including, but not limited to, an administrator, who will be responsible for the overall administration of the Practice including day-to-day operations and strategic development activities.

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