The FluentStream infrastructure supports custom routing of inbound calls based on a set of match rules. This allows customization of routing outside of the my.fluentcloud.com portal for on-demand changes required for certain setups.
The match rules are based on pre-defined custom headers placed in the SIP Invite sent to our system. When a match is found, the call is sent to the context desired as defined in the match rule. For assistance in setting this up, please contact FluentStream support at firstname.lastname@example.org. The most common use case is to send calls directly to extensions with no additional call processing via the fc-extension context.
Example for Twilio - Create a match rule for your Twilio AccountSID to modify routing on calls coming from Twilio system.
Headername - X-Twilio-AccountSid
Headervalue - youraccountid
context - fc-extension
tenant - Example
INVITE sip:100-Example@mediaserver.fluentcloud.com SIP/2.0
From: "+11234567891" <sip:+email@example.com>
CSeq: 102 INVITE
Date: Fri, 01 Jan 3099 00:00:01 GMT
User-Agent: Twilio Gateway
X-Twilio-AccountSid: youraccountid ----------- This header is added to our match list, and will change routing for any incoming calls with the specific AccountSID defined
o=- 659503768 659503768 IN IP4 22.214.171.124
s=Twilio Media Gateway
c=IN IP4 126.96.36.199
m=audio 10050 RTP/AVP 0 101
a=silenceSupp:off - - - -