Creating a Project

Projects are the top-level organizational unit in CallMeter. Every test, registrar, probe, media file, and worker assignment lives inside a project. Before you can run your first SIP test, you need at least one project.

What Is a Project?

A project is a dedicated workspace that groups all the resources related to a specific testing objective. Think of it as a container for everything needed to test a particular SIP infrastructure, environment, or customer deployment.

Each project contains:

Step-by-Step: Creating a Project

1. Log in to your CallMeter account at callmeter.io
2. From the main dashboard, click Projects in the left sidebar
3. Click the New Project button in the top-right corner
4. Fill in the project details:

5. Click Create

Your new project appears in the sidebar immediately and is ready for use.

The Project Slug

When you create a project, CallMeter automatically generates a URL-friendly slug from the project name. For example:

The slug is used in all URLs related to the project (e.g., callmeter.io/app/production-pbx-testing/tests). Once created, the slug cannot be changed because it would break existing bookmarks, shared links, and API integrations.

Project Limits by Plan

The number of projects you can create depends on your subscription plan. The Free plan restricts you to a single project, while paid plans allow multiple projects. Enterprise plans can negotiate custom limits.

Projects share organization-level resource quotas. The key limits that affect how you use projects are:

This means creating more projects does not give you more capacity -- it gives you more separation. A single project with 50 endpoints uses the same quota as five projects with 10 endpoints each.

Check your current usage and limits in the Billing section under Organization Settings, or visit Plans and Pricing for a full comparison.

Project Organization Strategies

How you structure projects depends on your team and testing needs. Here are proven approaches:

One Project per Environment

Create separate projects for production, staging, and development SIP infrastructure. This keeps test results isolated and prevents accidental testing against the wrong environment.

• Production PBX -- live system monitoring with probes
• Staging PBX -- pre-release validation with load tests
• Dev Environment -- experimental test configurations

One Project per SIP Platform

If you manage multiple SIP platforms or PBX vendors, dedicate a project to each:

• Asterisk Cluster -- all Asterisk-related tests and registrars
• FreeSWITCH Lab -- FreeSWITCH testing and tuning
• Cloud SIP Provider -- third-party trunk testing

One Project per Customer

Managed service providers (MSPs) testing client infrastructure often create one project per customer for clean separation of data, credentials, and access control:

• Acme Corp -- Acme's SIP trunk and PBX
• Globex Inc -- Globex's hosted PBX
• Initech -- Initech's SIP infrastructure

This approach also simplifies member management since you can grant customer-facing engineers access only to their relevant projects.

When to Use One Project vs. Many

A common question is whether to consolidate everything into a single project or split resources across multiple projects. The decision comes down to isolation requirements.

Use a single project when:

• You are testing one SIP platform or environment
• All team members need access to all tests and results
• Your registrars and SIP accounts are shared across test scenarios
• You want the simplest possible setup with everything in one place

Split into multiple projects when:

• You manage separate SIP environments (production, staging, development) and must never accidentally run a load test against the wrong one
• Different teams or customers should see only their own test data, registrars, and results
• You use different SIP servers for different purposes (e.g., Asterisk cluster vs. FreeSWITCH lab) and want clean credential separation
• Regulatory or contractual requirements demand data isolation between customers or business units
• You want separate probe configurations and status pages per environment

Avoid creating projects for:

• Organizing tests by date or campaign -- use descriptive test names instead
• Separating audio tests from video tests -- use groups within a single test
• One project per team member -- use project member roles for access control

A good rule of thumb: if two test scenarios share the same SIP server and credentials, they probably belong in the same project. If they use different SIP infrastructure or require different access control, separate projects make sense.

What to Do After Creating a Project

A newly created project is empty. Follow this onboarding sequence to run your first test. Each step builds on the previous one.

Step 1: Add a Registrar

Connect your SIP server by creating a registrar. You need to know your SIP server's hostname or IP address, the transport protocol it accepts (UDP, TCP, TLS, or WebSocket), and the SIP port it listens on.

See Adding a Registrar for details on transport selection and TLS configuration.

Step 2: Provision SIP Accounts

Create SIP credentials that test endpoints will use to register. You need at least two accounts for a basic caller-callee test. For load testing, provision as many accounts as your maximum endpoint count.

If your PBX supports bulk provisioning, use the bulk import feature to add hundreds of accounts at once. See SIP Accounts.

Step 3: Verify Connectivity (Optional but Recommended)

Before building a large test, create a minimal test with 1 concurrent call and a short duration (30 seconds) to confirm that your registrar settings and SIP accounts work correctly. This saves time debugging configuration issues in a complex test.

Step 4: Upload Media Files (Optional)

If you want to test with real audio or video content instead of synthetic signals, upload your media files now. CallMeter transcodes them into all supported codec formats automatically. See Uploading Files.

Step 5: Create Your Test

Configure a test with groups, endpoint counts, codecs, call duration, and call patterns. This is where the registrar, SIP accounts, and media files come together. See Creating a Test.

Step 6: Invite Team Members

Share the project with colleagues by adding them as project members with appropriate roles. See Managing Members.

Step 7: Set Up Monitoring (Optional)

Once you have validated your SIP infrastructure with on-demand tests, consider setting up probes for continuous monitoring. Probes run periodic lightweight tests and alert you when quality metrics cross your defined thresholds. See Creating a Probe.

Next Steps

• Project Settings -- Configure project options, rename, or delete
• Managing Members -- Control who can access this project
• Adding a Registrar -- Connect a SIP server to start testing