I need Help Integrating

[odejinmisa]

Hi team,

I need help on this.

If possible kindly provide your email.

[havfo]

I am not able to provide any support for this at the moment other than simple instructions for getting it running.

[odejinmisa]

I will be glad if you can provide instructions. Thanks

…

On Sat, 15 Oct 2022, 9:31 am Håvar Aambø Fosstveit, < ***@***.***> wrote: I am not able to provide any support for this at the moment other than simple instructions for getting it running. — Reply to this email directly, view it on GitHub <#1 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AO6VNOS342LQWZPLHCI36ITWDJTWLANCNFSM6AAAAAAQFUVI4Y> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[havfo]

First of all, I have not tested this in quite a while (2+ years) as I'm not currently working with Teams/SIP, so this might not work.

Get the Drachtio daemon up and running according to the latest documentation at https://www.drachtio.org/docs. Also make sure you have DNS set up properly and a valid certificate for the domain(s) that the daemon server is supposed to represent.

Create a mysql/mariadb database and populate it using the https://github.com/havfo/drachtio-msteams-gw/blob/master/lib/database/schema.sql schema. Have a look at the examples in that file to populate it with an organization and destination.

Create a config file in config/ called production.json. This will be the config the server will use if you start it with NODE_ENV=production. Have a look at the default.json for examples. The msgw section represents the hostname part of the FQDN of the gateway (where the Drachtio daemon is running). The contact port is the port at which the daemon is listening for incoming SIP traffic.

When you add an organization with a domain to the database, the final SIP FQDN will then be the combination of the msgw hostname variable and the organization domain name. Example where the organization domain is example.com and the msgw hostname is sip: sip.example.com. And the certificate for the daemon server would of course need to be valid for that FQDN.

The Node server can run on the same server as the daemon or a different server all together, that doesn't matter as long as there is a connection between them according to the config.

If you are unable to get it up and running based on this info, I am unable to provide more help. This repo requires quite a bit of knowledge on how to run and is in no way a turnkey solution.