CUBE: Variable identification in outgoing calls

[dgonzalez1]

Hello, my customer wants that outgoing calls from CUBE are identified with different numbers from a pool. The incoming call comes into the CUBE with always the same identification (calling number), so I can't map with translations rules to manipulate de calling number. One thing I thought was to have different outgoing dial-peers with different translation profiles to chosen sequentially, but I don't know how to make it work. Besides, the routing is made with destination uri to match outgoing dial-peer. I don't know if I can user the same destination uri tag in several dial-peers and if I can I suppose it's going to choose always the first one.

So I'm looking for some other idea to have variable calling numbers in outgoing calls.

Thank you.

[Roger Kallberg]

Maybe if you outline the end result that you're looking to achieve we might better be able to support you. Please provide detailed examples of what you're looking for as your original post wasn't super clear, at least not for me, what you want out of this.

[dgonzalez1]

Ok, I'm sotty, I though it was clear.

What I want to achieve is that for every call coming out from the CUBE the calling number in 'From' header is different, choosing them from a certain pool. For example, if I want to use numbers 1140045000/5001 and /5002, the outgoing INVITE messages for three consecutive calls should be:

INVITE sip:3016378803@x.x.x.x:5060 SIP/2.0
Via: SIP/2.0/UDP y.y.y.y:5060;branch=z9hG4bK454CA159
From: "ALARMA" <sip:1140045000@y.y.y.y>;tag=4D3D2FB2-C97
To: <sip:3016378803@x.x.x.x>
Date: Fri, 26 Jan 2024 19:31:57 GMT
Call-ID: 676E4101-BBB811EE-936AB997-3CFD2533@y.y.y.y

INVITE sip:3016378803@x.x.x.x:5060 SIP/2.0
Via: SIP/2.0/UDP y.y.y.y:5060;branch=z9hG4bK454CA159
From: "ALARMA" <sip:1140045001@y.y.y.y>;tag=4D3D2FB2-C97
To: <sip:3016378803@x.x.x.x>
Date: Fri, 26 Jan 2024 19:31:57 GMT
Call-ID: 676E4101-BBB811EE-936AB997-3CFD2533@y.y.y.y

INVITE sip:3016378803@x.x.x.x:5060 SIP/2.0
Via: SIP/2.0/UDP y.y.y.y:5060;branch=z9hG4bK454CA159
From: "ALARMA" <sip:1140045002@y.y.y.y>;tag=4D3D2FB2-C97
To: <sip:3016378803@x.x.x.x>
Date: Fri, 26 Jan 2024 19:31:57 GMT
Call-ID: 676E4101-BBB811EE-936AB997-3CFD2533@y.y.y.y

Thank you.

[Roger Kallberg]

There is no native way to do that in IOS. Possibly it might be possible with some TCL script running on the router, but not sure on how to trigger it for the calls.

What is the use case for this? Why do you want to present different calling numbers from a pool?

[dgonzalez1]

Customer ideas. I find it so useless as you do.

[Roger Kallberg · Accepted solution]

One idea came to mind. If you have multiple outbound dial peers, all with exactly the same destination match and same preference, but with different calling number translation profile/rule used it might work as then it should with the default dial peer hunt option use random selection. For more information see this document. Number String Dial-Peer Hunting 

[dgonzalez1]

Ok, sounds good. I had thought of using multiple dial-peers but i didn't know that the hunting was configurable. I though it was always to choose the first one.One thing is that I use destination uri tag for selection, not destination pattern. Not sure if it would be the same, but I could make some test.

Thank you, that gave me a interesting hint.

[dgonzalez1]

Hi Roger, I tried it and it worked as expected. So, thank you!

[Roger Kallberg]

Glad to hear that!