Hi All,
Has anyone done any extension based translation rules on inbound calls to a byoc cloud trunk? The use case I'm shooting for would allow us to receive an inbound string that's a derivative of a full e.164 number, and then map it to a route in Genesys via a regular expression.
For example, if the full number is +14045551212, we would receive +
551212@ourdomain.mypurecloud.com, then map that string to an alternate did number in purecloud - something like 13335551212 that would allow us to route it to a flow.
By doing this we'd still be able to allow an end user to have that original full number as their personal extension so that when they make outbound calls their correct did will show.
It's complicated, but we're really struggling with managing outbound caller id presentation.
Any thoughts/ideas are much appreciated!
Dean.
#SIP/VolP#Telephony------------------------------
Dean Thames
Koch Business Solutions
------------------------------