[ASTPPCOM-322] Setup Signaling Details so customer can choose different Rate Group? Created: 24/Jan/18  Updated: 14/Feb/18  Resolved: 14/Feb/18

Status: Done
Project: ASTPP Community
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Task
Reporter: slango-im Assignee: Unassigned
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

I have a use case that I can't figure out it ASTPP.

I have 2 Rate Groups, and I would like our customer to choose which Rate Group he wants to dial into based on a prefix or IP or something. For example:

We have Rate Group X and Rate Group Y.

Is there a way we can setup different signaling details so one customer account can choose between rate groups?



 Comments   
Comment by Eduardo Felipe de Oliveira (Inactive) [ 24/Jan/18 ]

You can create different prefixes within the same rate group.

For example:

55113588 ... - without a prefix
4654 55113588 ... - with prefix

where the origination rate 5511 ... matches only the termination rate of Trunk A
Where 4654 ... matches only the termination rate of Trunk B

And in the Rate Group you should add Trunks A and B

This way 5511 ... will have a price and 4654 ... will have another price per minute

Comment by slango-im [ 25/Jan/18 ]

Thank you, @eduardofoliveira.

Can you please clarify though. I though the prefix on our Trunks were the prefixes required by our termination partners?

Can you please point out where the prefix should be added?

Comment by Eduardo Felipe de Oliveira (Inactive) [ 25/Jan/18 ]

In the Edit Termination Rate you can remove the prefix used for internal control and add the prefix of your termination.

In this example the prefix 10 that is before 55 ... is used when my client sends the call to my gateway. To remove it, simply fill in the "Strip" field with the value of the prefix.

This prefix is removed and if I need to add another one to send to my termination in the "Prepend"

Generated at Sat Feb 10 07:16:06 CET 2024 using Jira 8.13.3#813003-sha1:22ebedbb75c99b147c66f14e031dd8a2d214753a.