How to convert CGPN or A-numbers from subsystem to full E.164 for outgoing calls(?)

[joul]

Hi, are there anyone who managed to add or delete digits on a SIP From: / CGPN / A-number? with flexibility, like short code variables?
Voicemail Pro Transfer action only works for IPO extensions but has no effect on external calls. (works mobile twin though)

Let's say the customer has some other brands PBX:es connected to the IPO via SIP trunk? OR perhaps a non-avaya CTI/voicemail.
Example: CLI is 4567 from the sub system but you need +46101234567 for outgoing call to external SIP trunk.
The only way I've done it is to "hard code" every conversion by these steps below:

Conditions:[ul]
[li]Cannot simulate mobile extensions using the CLI, the sub system sends sip Cancel in this case. (otherwise a good method!)[/li]
[li]There are no technicians available (or unwilling or incompetent) to access the sub system and change the behavior if that's even doable.[/li]
[li]There is no SBC between the sub system and the IP Office.[/li]
[li]The features and in the sub system cannot be replaced by the IPO.[/li]
[li]The incoming CLI may be only 3 - 5 extension digits but you need to add a prefix to those numbers to make full E.164 numbers for outgoing calls.[/li]
[/ul]

The following methods is OK if there is a limited number of short CLI's to convert. Example: convert 4567 to +46101234567
(might be quite a few lines in ICR and Short Codes...)
[ol 1]
[li]Using exact CLI matching for every CLI in Incoming Call Route: CLI: 4567 Number: . Dest: 4567# [/li]
[li]Unique SC to identify the caller and replace CLI number: Short Code: 4567N Tel.num: 888NS+46101234567 / Dial / Line Group:888 (ARS "CLIconverter")[/li]
[li]ARS 888: No need for unique shortcodes per CLI now. Code: 8880N Tel.num: +46N / Dial / Line Group: 8 (add more SC as needed per dialed numbers) [/li]
[li] External SIP trunk line group ID 8, Local URI: "Use internal data" works as well as "Auto" since it's not a real extension calling[/li]
[/ol]

 

[janni78]

Normally I would require any sub-system connected with SIP to send numbers in E.164 or at least in national format.

Otherwise an SBC can always be implemented or sub-systems can be replaced.
It might seem it can't but if there's a will there's a way

I wouldn't wanna do a bunch of shortcodes on the IPO side just because the other part can't send the correct number, but guess that might be the only way.

"Trying is the first step to failure..." - Homer

 

[joul]

Yep..
Or Avaya just could add a shortcode character as a variable for a CLI/CGPN..
The "G" is just waiting to be featured as a container for the CGPN received.
That way, only one Short Code could represent a whole number range. Example: Code: 4567N / N+4610123G / Dial / LG nr - Done!

 

[janni78]

You could just as well argue that the other system should send CLI in the correct format as all SIP numbers should be in E.164 format, for some reason many don't follow this tho.
Avaya should do a lot of things but it's not really their place to fix other manufacturers issues.

The other should should at least be able to send numbers in national format which could solve it.
If the maintainers of the other system can't change CLI at all it sounds like it might be better to just replace it with something that can be maintained.

"Trying is the first step to failure..." - Homer