Ability to apply prefix to incoming DDI call

[Kamil]

Hello,

There is an Outgoing DDI rule pattern where you can specify a prefix ex. 2* to present yourself with a specific DDI while calling out. That works nicely. 

Not sure if that's currently possible but I am looking for something similar that would be (optionally) applied to an incoming call. 

For example having multiple DDI numbers redirecting to the same hunt group. This would allow the person who answered to call back using the original DDI number that was initially called.

Something like the screen below unless there is already another way of doing it.

Thanks,

Kamil

[Kaian]

Hi Kamil,

Not sure if I understand exactly the requeriment here. What format is your DDI Provider using to place the call to the platform? How are your users dialing that DDI? 

Usually, manipulating origin DDI is done using numeric transformations, that are linked with main endpoints (Carriers, DDIProviders, Users, ...). For incoming calls, numeric transformation can be used to change presentation so the displayed value can be used by the user to place the call back to that origin. If your users require 2*DDI to be dialed to reach that origin number, you can create a custom Numeric Transformation in brand administration portal to add that2* and assign that transformation to the client or user.

Best regards 

[Kamil]

Hello Kaian,

I will do my best to better explain the requirements. This is probably not a very common deployment. 

For some customers we support we provide a dedicated DDI with a dedicated IVR. Going through the IVR tree at the very end they will eventually reach the same person or group of people that they will be speaking to. Something like the screen below.

We have also set up the Outgoing DDI rules to be able to call each Customer using a Dedicated to them DDI number.

1* for DDI#1
2* for DDI#2
3* for DDI#3

And this works fine if you want to initiate the call and you manually type the number with a dedicated prefix.

But if you want to redial the customer using the phone's history entries you will call the customer back presenting yourself as the default presentation that you have set up for your account. 

To bypass that I thought that we could have a new optional field to the DDIs configuration which would be the prefix (which will match the prefix from the Outgoing DDI rules) as mentioned in my previous post.

I would assume this prepends the origin number with the specified prefix while diverting it to the IVR. Something like to pic below

This would show up on the phone's screen as 2*<calling_number> and when hitting `call back` from the history this would actually dial 2*<number> with the prefix.

And this prefix would be optional to set up so you can decide whether you want to use it or keep the default behaviour as it is now.

Hope this all makes sense.

Let me know your thoughts.

K.

[Kaian]

Hi Kamil,

Thanks a lot for the detailed explanation of your scenario, highly appreciated!

Sadly, I don't think this is possible with current implementation of numeric transformations, because they are designed to convert numbers from E.164 to what the user expects, no matter what PBX flow it has used.

There are some DDI and IVR fields to update what Caller Name is presented, but this won't help you here.

From asterisk point of view, DDI numbers are not usually what user receives in its terminal (p.e. 555666777), but the full E.164 representation (p.e. +351555666777 for a country with +351 as country code), and Kamailio proxies (that are not aware which pbx flow has been used), transform that to what user requires using its assigned numeric transformation (p.e. remove the +351 country code and leave just 555666777 for national calls). If you wanted to add a prefix to that number so the user receives *2555666777, asterisk should work with E.164 numbers like +351*2555666777 (which actually is not E.164 at all).

For outgoing calls placed by users, the *2 code is stripped by Kamailio proxy before applying transformations (converting from user dialed to E.164) and placed in a SIP Header (called X-Info-DDI-Prefix) so asterisk can use that value in Outgoing DDI Rules. If I understand correctly your proposed change will be to add a similar field in DDIs, to do the reverse, adding a SIP Header to Kamailio to request adding that prefix after transforming from E.164 (asterisk numbers format) to user prefered format.

It could be a nice feature, and I will share it with the rest of the team, but with the current schedule I don't know when it could be implemented. Of course, If you're willing to pay to prioritize features, feel free to contact our commercial team at come...@irontec.com

Best regards!

--
You received this message because you are subscribed to a topic in the Google Groups "ivozprovider-users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/ivozprovider-users/xrO4QU3fcQA/unsubscribe.
To unsubscribe from this group and all its topics, send an email to ivozprovider-us...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/ivozprovider-users/ec163f9a-381f-4de7-a7d8-781946b81713n%40googlegroups.com.