davehorton/drachtio-basic-registrar

A SIP registrar built using drachtio and rtpengine

drachtio-basic-registrar

A SIP registrar built using drachtio and rtpengine.

Features:

• supports sip clients connecting using udp, tcp, or websockets
• supports traversing nat firewalls
• supports webrtc clients and handles SRTP/RTP encrypt/decrypt
• connectable to your SIP trunking provider

Installing

• install drachtio, rtpengine and redis somewhere in your network (drachtio and rtpengine must have public IP addresses),
• create a config file (see config/default.json.example for example settings),
• add your sip user credentials to the config file,
• assign DIDs to sip users in the config file, if you want to receive calls from the PSTN and route them to sip users,
• add your SIP trunking provider details (If you have one) to the config file, then

$ npm install
$ npm start

Then point your sip phones and webrtc clients to the drachtio server and enjoy!

Testing

npm test

Status

Currently, this app just handles registrations and invites. Planned next steps would be to handle presence-related messages (SUBSCRIBE, PUBLISH) and IM (Message) as well.

Hey, contributors are welcome! Join in! :)

drachtio-basic-registrar's Issues

Invite logs have multiple Call-ID tags applied.

During my testing I have noticed that my INVITE logs have multiple Call-ID added.

I believe these are applied here:
if (process.env.NODE_ENV !== 'test') logger = logger.child({'Call-ID': req.get('Call-ID')});

Looks like this is intended behaviour for Pino:
http://getpino.io/#/docs/child-loggers?id=cost-of-child-logging

However wont the logs keep growing in size if the Call-ID is always appended?

Thanks