Establishing secure connection…Loading editor…Preparing document…

Telecommunication Services New SIP Trunk

This template is fully customizable. Edit the text, fill out the fields, and send it for signature. Give it a try!

Telecommunication Services New SIP Trunk Agreement

Parties

This Agreement is entered into by and between Service Provider: , located at and Customer: , located at .

WHEREAS

WHEREAS, Service Provider is engaged in the business of providing telecommunication services, including SIP trunking, and represents that it has the expertise, personnel and equipment necessary to provide such services; and

WHEREAS, Customer desires to obtain from Service Provider, and Service Provider agrees to provide, SIP trunking services and related provisioning, porting and support on the terms and conditions set forth in this Agreement; and

WHEREAS, the parties intend that this instrument constitute the entire agreement governing the provision, operation, and billing of the new SIP trunk ordered by Customer.

Scope of Work

Service Provider shall provision, configure and deliver SIP trunking services in accordance with the technical specifications and order details set forth below. Service Provider will perform provisioning, testing and cutover coordination with Customer and any third parties identified by Customer.

Porting required: If checked, Porting Contact:

Payment Terms

Customer shall pay Service Provider the fees set forth below. All amounts are stated in the currency specified in the invoice and are exclusive of taxes unless otherwise required by law. Customer is responsible for any taxes, duties or assessments imposed by government authority on payments to Service Provider.

Term and Termination

This Agreement shall commence on the Start Date and shall continue for the Initial Term unless earlier terminated in accordance with this Agreement. Unless otherwise stated, the Agreement will automatically renew as provided below.

Start Date:

End Date (if any):

Auto-renewal: If auto-renewal is enabled, renewal term will be the same as the Initial Term unless otherwise agreed in writing.

Confidentiality

Each party (the "Receiving Party") shall hold in strict confidence all Confidential Information disclosed by the other party (the "Disclosing Party"). "Confidential Information" includes technical specifications, network configurations, pricing, customer lists, porting information, and any non-public business or technical information disclosed in connection with this Agreement. The Receiving Party shall not use Confidential Information except as necessary to perform its obligations hereunder and shall not disclose Confidential Information to third parties except to employees, agents or contractors who have a need to know and who are bound by confidentiality obligations at least as protective as those herein.

The obligations of confidentiality do not apply to information that: (a) is or becomes publicly available through no breach by the Receiving Party; (b) was rightfully in the Receiving Party's possession without restriction prior to receipt from the Disclosing Party; (c) is independently developed by the Receiving Party; or (d) is required to be disclosed by law or ordered by a court or regulatory authority, provided the Receiving Party gives prompt written notice to the Disclosing Party to permit a protective order or other remedy.

Confidentiality obligations shall survive termination of this Agreement for a period of three (3) years except that trade secrets shall remain protected for as long as they qualify as trade secrets.

Limitation of Liability

Except for liability arising from willful misconduct, gross negligence, breach of confidentiality, or infringement claims, neither party shall be liable to the other for indirect, incidental, special, punitive or consequential damages, including lost profits, even if advised of the possibility of such damages. Service Provider's aggregate liability for direct damages under this Agreement shall be limited to the total amount of fees paid by Customer to Service Provider in the preceding twelve (12) months.

Governing Law

This Agreement shall be governed by and construed in accordance with the laws of the State of without regard to its conflicts of law principles. The parties submit to the exclusive jurisdiction of the state and federal courts located in that State for resolution of disputes arising out of this Agreement.

Entire Agreement

This Agreement, including any attached order forms, schedules, and appendices executed by the parties, constitutes the entire agreement between the parties with respect to its subject matter and supersedes all prior and contemporaneous agreements, understandings and communications, whether written or oral. No amendment to this Agreement shall be effective unless in writing and signed by authorized representatives of both parties.

Notices

Acceptance

By signing below, the parties acknowledge that they have read, understand and agree to be bound by the terms and conditions of this Agreement and that the person signing on behalf of each party is authorized to bind that party.

Service Provider

Printed Name:

By:

Date:

Customer

Printed Name:

By:

Date:

Enter text✕

What the Telecommunication Services New SIP Trunk document is

The Telecommunication Services New SIP Trunk is a formal service-order and configuration record used to request, provision, and document a new SIP trunk between a customer and a carrier. It captures technical parameters (SIP domains, transport, codecs), numbering information (DID ranges, porting requests), billing and account identifiers, service-level expectations, and signature blocks for authorized parties. The completed form creates an auditable record of the requested service configuration and any responsibilities for testing, cutover, and ongoing support.

Why a clear SIP trunk order matters

A precise Telecommunication Services New SIP Trunk reduces provisioning errors, avoids billing disputes, and documents emergency services responsibilities. Clear fields for IPs, codec lists, DID ranges, and signer authority streamline carrier implementation and create an auditable contract record for compliance and troubleshooting.

Why a clear SIP trunk order matters

Primary users and stakeholders

Teams who commonly complete or approve SIP trunk orders.

  • IT / Network Operations — Prepares technical details and test plan; validates IP addressing and codecs.
  • Procurement / Vendor Management — Reviews billing, contract terms, and vendor SLAs before ordering.
  • Telecom / Facilities Managers — Coordinates DID inventory, 911 responsibilities, and cutover scheduling.

Each stakeholder should confirm their section before submission to avoid delays.

Core pieces included on a professional SIP trunk order

A well-constructed Telecommunication Services New SIP Trunk form groups technical, administrative, and legal data so carriers can provision and verify services without follow-up.

Customer Identity

Legal company name, billing account number, site address, and an authorized signer to validate contractual acceptance and billing responsibility.

SIP Termination Details

SIP domain or IP addresses, transport protocol (UDP/TCP/TLS), port numbers, and any required TLS certificates for secure signaling.

DID and Porting

Requested DID ranges, quantity, and any number-porting instructions including current carrier, account PIN, and desired porting date.

Codec and Media Settings

Preferred codecs (G.711, G.729, Opus), RTP port ranges, jitter buffer guidance, and preferred NAT traversal methods.

Security and Authentication

SIP authentication method (IP ACL, Digest, mutual TLS), SIP trunk passwords if used, and any SBC or firewall requirements.

Service Terms

Requested service start date, SLAs, testing and cutover windows, billing start, and signature block for authorized acceptance.

Step-by-step: completing and submitting the SIP trunk order

Use this sequential checklist to prepare, verify, and submit a complete SIP trunk request to your carrier.

  • 01
    Gather data: Collect billing, DID inventory, and network addressing details.
  • 02
    Complete form: Populate all technical and administrative fields precisely.
  • 03
    Internal review: Have IT, procurement, and legal confirm their sections.
  • 04
    Submit to carrier: Send completed order with attachments and authorized signature.

Typical online workflow settings for electronic completion

Configure the digital workflow to ensure secure signing, optional authentication, and automatic distribution of completed records.

Field Configuration
Signer Order Sequential or parallel routing based on role
Authentication Email link by default; add SMS or KBA if required
Attachments Include network diagrams and porting authorization PDFs
Notifications Auto-email on completion with PDF and audit trail

Platform and file requirements for e-submission

Confirm the carrier's accepted file formats and integrations before uploading.

  • Accepted Formats: PDF, DOCX commonly accepted
  • Integration Options: Salesforce, NetSuite, Microsoft 365
  • Secure Transport: TLS-encrypted upload or SFTP preferred

How provisioning and cutover are typically coordinated

Provisioning follows a predictable sequence: order intake, configuration, testing, and cutover. Clear scheduling avoids service interruptions.

  • Order Intake: Carrier validates account and receives documentation
  • Configuration: Carrier configures SIP peer and routes per the form
  • Testing: Joint testing of calls, codecs, and emergency routing
  • Cutover: Scheduled switch with roll-back plan and confirmation

Typical timelines and processing expectations

Allow adequate lead time: provisioning times vary by carrier, number porting, and complexity. Confirm SLA windows during order review.

Order Submission Window:

Submit at least 3 business days before desired provision date

Standard Provisioning Time:

Often 3–10 business days depending on resources and porting

Number Porting Interval:

Porting typically requires 7–30 days depending on donor carrier

Testing Period:

Allow 1–3 business days for joint connectivity tests

Billing Start:

Billing commonly begins on activation or agreed service date

eSignature pricing comparison for completing SIP trunk orders

Compare basic starting prices and key features for common eSignature vendors. signNow is listed first per vendor comparison conventions.

signNow DocuSign Adobe Sign PandaDoc HelloSign
Starting Price $8/user/mo $15/user/mo $14/user/mo $19/user/mo $15/user/mo
Free Trial Yes, 7-day trial Yes, trial available Yes, trial available Yes, trial available Yes, trial available
Bulk Send Yes (Business Premium) Yes Yes Yes No
Audit Trail Yes Yes Yes Yes Yes
Envelope Cap No cap 100 envelopes/user/year Varies by plan Varies by plan Varies by plan

Security and compliance considerations for electronic submission

Encryption: TLS 1.2/1.3 transit; AES-256 at rest
Audit Trail: Timestamps, IP logging, and action history
HIPAA: BAA required when handling PHI
21 CFR Part 11: Support for audit and e-sign timestamps
SOC 2: SOC 2 Type II report available
Accessibility: WCAG 2.0 Level AA compliant

Key risks and consequences of incorrect or incomplete orders

Service Disruption: Incorrect IPs or DIDs can cause outages
Billing Disputes: Wrong account data may delay charge allocation
Emergency Routing: Misconfigured 911 routing risks public-safety failures
Porting Failures: Incomplete port info can delay number transfer
Security Exposure: Weak auth allows toll fraud or SIP abuse
Regulatory Risk: Noncompliance with recordkeeping may trigger audits

Common mistakes that slow SIP trunk provisioning

  • Providing incomplete DID details or non-contiguous ranges leads to back-and-forth with the carrier and delays.
  • Using ambiguous signer authority causes carriers to reject orders pending legal verification.
  • Omitting emergency services routing information can prevent successful testing and cutover.
  • Submitting network addresses without confirming NAT, firewall, or SBC settings often breaks call flow during testing.

Typical authorized signers and approvers

IT Manager

An IT Manager or Network Lead typically provides technical approvals, confirms IP addresses and firewall rules, and signs to confirm the technical readiness for cutover. They should include contact details for immediate troubleshooting during testing.

Procurement Director

A Procurement or Vendor Manager authorizes billing terms, contract language, and SLA acceptance. This signer confirms commercial responsibility and coordinates legal or procurement reviews if required.

Example scenarios showing how the form is used

Real-world examples show typical attachments, approvals, and outcomes when the SIP trunk order is well prepared.

Enterprise Deployment

A multinational IT team prepared contiguous DID blocks and mutual TLS credentials

  • Carrier validated the SIP peer and scheduled a cross-network test
  • The cutover completed within the SLA window with a documented audit trail for finance and operations.

Small Business Port

A small office provided porting authorization and account PINs

  • Donor carrier required additional verification, delaying porting two weeks
  • After providing requested docs the port completed and billing began on the agreed activation date.

Frequently asked questions about completing and signing SIP trunk orders

Answers to frequent questions about signature validity, e-submission, and signer authority when filing orders electronically.


Need help? Contact support

be ready to get more
Join over 28 million airSlate SignNow users