News & Announcements User Community Developer Community

Welcome to the RingCentral Community

Please note the community is currently under maintenance and is read-only.

Search
Make sure to review our Terms of Use and Community Guidelines.
  Please note the community is currently under maintenance and is read-only.
Home » Developers
Call Routing based upon API Call
Tags: rest api
Feb 13, 2020 at 8:11am   •   3 replies  •  0 likes
Tony Spotorno

Our company provides several levels of support for our clients. Some users are email only, others have phone support. We would like to have the system automatically make an api call to a service we would setup that returns the extension to move to. I.e. if the client has phone support, we could forward the call to the support queue, if they only had email support, we could forward to a VM explaining their support options...

I've researched and saw some posts where this feature was coming? Is it available now?

3 Answers
answered on Feb 19, 2020 at 8:53am  

1. Inbound call to Ringcentral at phone number 123-123-1234.

=> Register for a presence event notification for the extension which owns the phone number "123-123-1234" or at the account level to receive incoming call notification.

// subscribe for extension presence notification
'/restapi/v1.0/account/~/extension/[extensionId]/presence?detailedTelephonyState=true'
// subscribe for account level notification
'/restapi/v1.0/account/~/presence?detailedTelephonyState=true'

2. Ringcentral sends a get message to an external url passing the phone number... Example: https://www.mycompany.com/GetExtension.aspx?phonenumber=1234567890

=> RingCentral does not send any GET request to external url. It is up to you to send GET request to any external server to get external information. And where is the phone number "1234567890" coming from? Who's number is that?

3. GetExtension.aspx returns a single extension.

=> What is this extension? Why it comes from "https://www.mycompany.com"

4. Ringcentral directs the call to the extension specified via the url.

=> There is no API to direct a call to an extension based on url. What URL is this? You can only forward an incoming call to a phone number using the telephoneySessionId and the partyId from the telephony session notification payload.


 0
answered on Feb 16, 2020 at 10:34am  

It's really hard for me to understand your questions. So my answers will be generic and based on what I could guess.

1. Yes, you can programmatically make a phone call using the RingOut or CallOut API

2. Yes, you can forward an incoming call to a call queue's phone number

3. Yes, you can forward an incoming call to a voice mailbox. It is the same way you forward a call to another extension but that extension's setting is accepting voicemail only.

To detect incoming call, you can subscribe for the telephony session notification to receive events.

If you can explain your problem better, I can help you better.


 0
answered on Feb 18, 2020 at 8:28am  

This is for inbound calls.


1. Inbound call to Ringcentral at phone number 123-123-1234.

2. Ringcentral sends a get message to an external url passing the phone number... Example: https://www.mycompany.com/GetExtension.aspx?phonenumber=1234567890

3. GetExtension.aspx returns a single extension.

4. Ringcentral directs the call to the extension specified via the url.


 0



A new Community is coming to RingCentral!

Posts are currently read-only as we transition into our new platform.

We thank you for your patience
during this downtime.

Try Workflow Builder

Did you know you can easily automate tasks like responding to SMS, team messages, and more? Plus it's included with RingCentral Video and RingEX plans!

Try RingCentral Workflow Builder

PRODUCTS
RingEX
Message
Video
Phone
OPEN ECOSYSTEM
Developer Platform
APIs
Integrated Apps
App Gallery
Developer support
Games and rewards

RESOURCES
Resource center
Blog
Product Releases
Accessibility
QUICK LINKS
App Download
RingCentral App login
Admin Portal Login
Contact Sales
© 1999-2024 RingCentral, Inc. All rights reserved. Legal Privacy Notice Site Map Contact Us