Enki Multimedia
FRContact
Menu

Network and products / SIP Edge, in development

A managed SIP edge for your voice platform.

A managed boundary between your voice platform and its external SIP peers, with routing policies, signalling handling and media relaying agreed for your deployment. Keep your platform and carrier relationships; Enki operates the edge.

Built on Chappe. Operated by Enki Multimedia on AS209823.

Discuss SIP EdgeSee the Chappe architecture

Status: in development. First deployments are scoped with each customer.

The problem it solves

Your voice platform exchanges SIP with carriers, customers' PBXs and other platforms over the public Internet. Each peer has its own addresses, behaviour and security expectations, and the edge that faces them needs constant attention. SIP Edge puts a managed boundary in front of your platform, so your team can work on the platform instead of its border.

ForHosted PBX providers, contact centres, communications platforms and organisations running their own telephony.
Not a PBXSIP Edge sits in front of your platform. It does not replace it, and it does not add PBX features.

Who does what

Enki operates

  • The edge deployment on AS209823
  • Peers, routing policies and signalling rules agreed with you
  • Media relaying, when your deployment includes it
  • Monitoring, updates and fixes for the edge

You keep

  • Your voice platform and its call logic
  • Your carrier relationships and contracts
  • Your customers and their numbers

Not included

Phone numbers, carrier SIP trunks, PSTN minutes and emergency-calling service.

Signalling and media take different paths

SIP signalling always passes through the edge. Media passes through a relay only when your deployment anchors it.

SIP signalling

External SIP peersCarriers, customer PBXs, other platforms
SIP EdgeBuilt on chappe_sip, operated by Enki
Your voice platformUnchanged, run by you

Media, when the deployment anchors it

Peers' media endpointsRTP from carriers and peers
RTPengineExternal media engine, controlled by chappe_rtpengine
Your platform's mediaMedia servers or endpoints
RTP travels through RTPengine, never through the Erlang signalling processes. Without media anchoring, media flows between endpoints as negotiated. SIP peers use standard SIP; they do not need Enkiway or MASQUE. The diagram shows roles, not locations: SIP Edge is not offered at every point of presence, and the diagram does not describe failover.

How Chappe is used

Chappe is the voice software we develop in Erlang/OTP. SIP Edge uses the parts of it that a deployment needs, and only those.

See the Chappe architecture

Signallingchappe_sip handles SIP at the edge, as a proxy or a back-to-back user agent (B2BUA). The mode is chosen for each deployment.
Media controlchappe_rtpengine drives RTPengine over its NG control protocol when the deployment anchors media. It controls the sessions; RTPengine carries the packets.
OperationEnki configures the edge for your peers and routes, monitors it and maintains it, on AS209823.
Not part of SIP EdgePBX features, conferencing, IVR, recording, transcription and transcoding.

Where it stands

SIP Edge is in development on Chappe. Each first deployment is scoped with the customer.

Transports, encryption, media policy and locations are agreed per deployment. We will publish them here once they are established.

  1. Technical discussion

    Your platform, your peers, your call volumes and where they are.

  2. Written proposal

    Scope, media policy, monitoring, responsibilities and price.

  3. First deployment

    On a limited set of peers and routes, tested with you.

  4. Operation

    Enki runs the edge; you extend it to more peers when you are ready.

Discuss SIP Edge.

Tell us about your platform and the peers it connects to. Benoît replies to arrange a technical discussion.

Discuss SIP EdgeSee the Chappe architecture

Need voice software built rather than an edge operated? That is engineering work: Erlang engineering