MOBILE VOICE / BUSINESS / RESELLERS
From a mobile dialer to a reseller network, shape your next connection with a focused telecom partner.
EGY iTelSwitch brings the conversation around dialers, SIP connectivity, routing and reseller operations into one place. Start with your use case, agree the technical scope, then validate the connection before rollout.
THE ANDROID APP
Download the app directly to your Android phone.
Download Android AppOpen the downloaded APK on your Android phone to install the app.SOLUTIONS
Explore the scope, see what to prepare, and send a focused request.
Give mobile users a clear path to voice access.
Discuss dialer compatibility, account activation, supported codecs and a test call before onboarding users.
Device & OS • Dialer • Number format • Test destination
Plan the connection between your PBX or dialer and a voice provider.
Agree the SIP host, authentication method, transport, media settings and concurrent-call requirement. SIP handles session signaling; RTP carries the media.
PBX • SIP host • Authentication • Transport • Concurrency
Turn destinations and traffic rules into a clear routing plan.
Define destination prefixes, route priority, capacity and fallback behavior. Validate routing with controlled test calls and call-detail records.
Destination prefixes • Priority • Fallback • CDR review
Build an account structure that grows with your customer base.
Scope customer provisioning, balance controls, rate presentation and usage reports. Commercial terms and available account functions are confirmed during review.
Account hierarchy • Credit policy • Rate sheet • Reporting
Prepare a useful brief for international voice traffic.
List destination countries, expected minutes, peak concurrency and quality criteria. Test destinations and agree rates before committing traffic.
Destinations • Minutes • Peak capacity • Acceptance tests
Connect branch, office and remote-team requirements.
Start with users, extensions, existing PBX, call flows and support responsibilities. Build a rollout plan around the agreed technical scope.
Users • Extensions • Branches • Call flows
NETWORK / YOUR BUSINESS
Your location, destinations and operating model shape the connection brief.
Connection planning illustration
Choose your location and outline the destinations you need.
Explore by region
Service availability is confirmed during review.Scope is confirmed per connection.
PARTNER OPERATIONS
Agree how accounts, balances and customer support should work before onboarding your first users.
Your reseller operationIllustrative account structure
Define the account hierarchy and who can create or manage customers.
Agree how top-ups, limits and rate changes are reviewed.
Use call-detail records to reconcile durations, destinations and charges.
OPERATIONS / VISUAL WALKTHROUGH
Explore accounts, routes and usage review in an interactive illustration of the operating workflow.
| Route | Purpose | Review |
|---|---|---|
| Route A | Primary voice path | Priority |
| Route B | Alternate path | Fallback |
| Destination group | Prefix-based policy | Scope |
Define permissions and commercial scope.
Agree account and credit responsibilities.
Review activation and usage needs.
Destination → Duration → Charge
Include the endpoint, test-call time and observed result. Attach your requirements through the inquiry form.
Send a technical inquiryCONNECTION PLANNER
Choose your operating model. Download the checklist or add it to your inquiry.
TECHNICAL FIELD NOTES
Short notes to help you ask the right questions and isolate common issues.
SIP establishes, changes and ends sessions. RTP carries real-time media such as voice. A successful registration alone does not prove that audio will work in both directions.
SIP · RFC 3261 ↗Check the agreed media ports, firewall rules and NAT configuration. Compare an approved Wi-Fi connection with mobile data, and provide a test-call timestamp and destination to the technical team. ICE is a standard mechanism for finding workable media paths through NAT.
ICE · RFC 8445 ↗Ask which transports and media security mechanisms the connection supports. TLS protects the signaling transport; SRTP provides protection for real-time media. These must be confirmed for the actual endpoints and route.
SRTP · RFC 3711 ↗FAQ
Clear expectations for access, setup and inquiries.
This website helps businesses and telecom partners scope mobile voice, SIP, switching and reseller requirements, and submit a technical inquiry. The team confirms the exact service and commercial scope before activation.
Sign in with your iTel account to open the keypad, call and view your synced history and recordings. Allow microphone access to make a call.
Define your account hierarchy, balance policy, customer onboarding and reporting needs. Availability, rates and access duration are agreed with the team; submitting a request does not activate an account.
Provide your PBX or dialer model, destination countries, expected concurrent calls and preferred authentication method. Do not include passwords in an inquiry.
Caller ID presentation depends on the provider, destination network and account configuration. Confirm the required presentation and test the destination before using a route.
A successful submission is saved in the site’s private inquiry inbox and returns a reference number. It is not an automatic account activation or payment. Keep the reference for follow-up.
LET’S CONNECT
Share your use case and the team can review the right technical scope. Successful inquiries are saved with a reference number.
Include destinations, expected users and concurrent calls. Service availability and commercial terms are confirmed during review.
GET STARTED
Apply as an individual, business or reseller. We will review your request before arranging account setup.
Your request is saved securely with a reference number. Account activation is arranged after review. No password or payment is needed here.
