Service Provider UI for Super Admin to configure third party provider connectivity

[ivelin]

This is a huge aggregate issue that should be split into the following individual issue when implementation time comes:

1) Termination/Outbound SIP service provider configuration. For one or more service providers.

2) Configuring plugin for best cost routing or other algorithm for routing to multiple service providers configured in 1.

3) Origination/Inbound SIP service provider configuration. Enabling one or more providers to send inbound traffic to Restcomm.

4) DID provisioning API. For one or more service providers. Some have better DID rates and quality in certain markets than others.

5) TTS service provider configuration

6) Transcription service provider configuration

7) Real time voice recognition service provider configuration

8) Termination/Outbound SMS/MMS service provider(s) configuration

9) Origination/Inbound SMS/MMS service provider(s) configuration

[telecomsxchange]

Was this every done ? Completed ?

[deruelle]

@telecomsxchange Not yet. There is work in progress on the backend server side first https://github.com/RestComm/Restcomm-Connect/issues/1981 to provide support for multi providers.

Would you like to help and contribute to the effort ?

[telecomsxchange]

Hello,

Yes, we can contribute. if we integrate TelecomsXChange it gives access to 300+ Carriers within a single interconnection.

I would be happy to work on this integration with you and run some tests.

I also can help with bringing Arabic language to web interface and probably IVR stuff.

---

Ameed Jamous

CTO

North America: +1(855) 233-4464 Europe: +327-848-1312 E-mail: a.jamous@telecomsxchange.com Web: www.telecomsxchange.com Latest News: Click here https://apple.news/TEIVgIbVRSG2EJG2E37IwBQ FCC License :ITC-214-20150519-00126

Address: 1100 NW 163rd Drive, Suite C-3 Miami, FL 33169 - USA

On Thu, Apr 13, 2017 at 12:40 PM, Jean Deruelle notifications@github.com wrote:

@telecomsxchange https://github.com/telecomsxchange Not yet. There is work in progress on the backend server side first #1981 https://github.com/RestComm/Restcomm-Connect/issues/1981 to provide support for multi providers.

Would you like to help and contribute to the effort ?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/RestComm/Restcomm-Connect/issues/206#issuecomment-293842287, or mute the thread https://github.com/notifications/unsubscribe-auth/AZdwbRhb0WXh8821xXSI-WrzsKAq-V2aks5rve2egaJpZM4D5Ybo .

[deruelle]

@telecomsxchange We have an API to integrate new providers, you can see https://github.com/RestComm/Restcomm-Connect/tree/master/restcomm/restcomm.provisioning.number.api and there is already a number of providers integrated (nexmo, bandwidth, VoIP Innovations, voxbone) that you can check out in https://github.com/RestComm/Restcomm-Connect/tree/master/restcomm

Arabic language support would be great too !

We would need you to sign the Contributor License Agreement at https://telestax.com/open-source/#Contribute

Are you already in touch with someone at Telestax to discuss further ?

[telecomsxchange]

Hi Jean,

Yes. I have a scheduled call on Tuesday with Teles tax team to discuss other subjects as well.

Yes I see those voice provider integrations. But those are very expensive for voice termination compared to the real market rate and don't give the best quality possible.

As a service provider assuming I use Restcomm , i am not going to pay Twilio 5 cents per minute to India while real market rate is $0.0084 with better quality than Twilio and Nexmo however nexmo and twilio are wonderful for SMS and DIDs and more should be added (voxbone , didww .. )

In my opinion Restcomm should give the flexibility to add any SIP provider easily and run an LCR ( extremely needed in the real world to compete in the market ) this is offered by many open source and commercial solutions out of the box. This is critical for many service providers that will use this great software.

The power of TelecomsXchange integration out of the box that it gives you access to 300+ carriers in a single integration and the seller voice rates are not marked up. So basically the carrier rates are never marked up and passed on to the buyer (e.g Restcomm user) without any commission.

https://youtu.be/j0e_TV0JQ0k this is a quick video demonstration to give you an idea of how it works and what it looks like.

I'll check out the contributor agreement and get back to you.

Thank you very much.

-- Ameed

Sent from my iPhone

On Apr 13, 2017, at 11:21 PM, Jean Deruelle notifications@github.com wrote:

@telecomsxchange We have an API to integrate new providers, you can see https://github.com/RestComm/Restcomm-Connect/tree/master/restcomm/restcomm.provisioning.number.api and there is already a number of providers integrated (nexmo, bandwidth, VoIP Innovations, voxbone) that you can check out in https://github.com/RestComm/Restcomm-Connect/tree/master/restcomm

Arabic language support would be great too !

We would need you to sign the Contributor License Agreement at https://telestax.com/open-source/#Contribute

Are you already in touch with someone at Telestax to discuss further ?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.

[deruelle]

If you want to allow developers/users be able to purchase TelecomsXchange DIDs through the API or Restcomm Dashboard, you need to implement https://github.com/RestComm/Restcomm-Connect/tree/master/restcomm/restcomm.provisioning.number.api and provide a TelecomsXchange plugin so that users can purchase and use your DIDs at the rates you are mentioning. As soon as this is available and merged, all Restcomm users will be able to use TelecomsXchange through Restcomm Connect

[telecomsxchange]

Hello Jean,

We don't provide DIDs. We provide voice termination (outbound international dialing) at best rates in the industry.

Restcomm can send those calls to TelecomsXchange via SIP. Let me know if this required any software integration.

Sent from my iPhone

On Apr 25, 2017, at 12:50 PM, Jean Deruelle notifications@github.com wrote:

If you want to allow developers/users be able to purchase TelecomsXchange DIDs through the API or Restcomm Dashboard, you need to implement https://github.com/RestComm/Restcomm-Connect/tree/master/restcomm/restcomm.provisioning.number.api and provide a TelecomsXchange plugin so that users can purchase and use your DIDs at the rates you are mentioning. As soon as this is available and merged, all Restcomm users will be able to use TelecomsXchange through Restcomm Connect

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.

[deruelle]

Only setting up the outbound proxy to TelecomsXchange should work.

[telecomsxchange]

Thank you

---

Ameed Jamous

CTO

North America: +1(855) 233-4464 ext 1 E-mail: a.jamous@telecomsxchange.com Web: www.telecomsxchange.com Skype: telecomsxchange D&B Number: 07-971-4461 FCC License :ITC-214-20150519-00126 Status Page: http://status.telecomsxchange.com Github Repo: https://github.com/telecomsxchange

Address: 1100 NW 163rd Drive, Suite C-3 Miami, FL 33169 - USA

On Tue, May 2, 2017 at 11:08 AM, Jean Deruelle notifications@github.com wrote:

Only setting up the outbound proxy to TelecomsXchange should work.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/RestComm/Restcomm-Connect/issues/206#issuecomment-298544422, or mute the thread https://github.com/notifications/unsubscribe-auth/AZdwbXKCf9SwE-hG4JBNZ6Rc9pOUzHsvks5r1uSbgaJpZM4D5Ybo .