[OpenSIPS-Users] CallID shorting

[Antonios Psaras]

Hello Johan.

 

Thank you for your reply. That was my first thought as well. But in all steps I have cases with 3rd party systems connected so I need to have topology hiding at all steps or I must enable topology hiding per gateway which was my next thought but in that case reconciliation / cooking / billing will get complex.

 

In any case, if there is no other way to go I will consider it.

 

My opinion is that OpenSIPs should keep the information required internally in dialog level and generate a new fixed length callid which can be configurable to have specific length, prefix and suffix. 

 

But again… if there is any other option which can be implemented as is, I will be happy to consider.

 

Regards

 

 

From: Johan De Clercq <Johan at democon.be> 
Sent: Πέμπτη, 8 Μαΐου 2025 16:35
To: apsaras at microbase.gr; OpenSIPS users mailling list <users at lists.opensips.org>
Subject: Re: [OpenSIPS-Users] CallID shorting

 

my 2 cents (at least that's what I do), use topology-hiding on acces and interco. 

doing it also on core and routing just makes your life overly complicated. 

 

Br, Johan. 

 

Op do 8 mei 2025 om 14:50 schreef Antonios Psaras <apsaras at microbase.gr <mailto:apsaras at microbase.gr> >:

Dear Team

 

We have a setup with multiple SBCs in line like

 

Access SBC -> Routing SBC -> Core SBC -> Interconnect SBC

 

On each level we apply topology hiding so the callid keeps increasing in length ending up with 200+ characters which is not manageable by all upstreams carriers. Some of those asking for max 40 char length callid.

 

Is there a way to keep topology hiding to all SBCs and decrease / minimize / control the callid length?

 

Best regards

 

_______________________________________________
Users mailing list
Users at lists.opensips.org <mailto:Users at lists.opensips.org> 
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20250508/867b2df6/attachment.html>