6 Dec
2021
6 Dec
'21
6:43 p.m.
We have an internal component of our callflow that does not support compact headers
(vendor says it's on the roadmap but no eta, etc) so I'm trying to find a clean
way to detect if a message has compact headers and reject it. I haven't had much luck
in finding a way to identify specifically if any of the headers of the message are compact
however. Can anyone point me in a direction please?
Thanks!
Confidentiality Notice: This e-mail, and any attachment to it, contains privileged and
confidential information intended only for the use of the individual(s) or entity named on
the e-mail. If the reader of this e-mail is not the intended recipient, or the employee or
agent responsible for delivering it to the intended recipient, you are hereby notified
that reading this e-mail is strictly prohibited. If you have received this e-mail in
error, please immediately return it to the sender and delete it from your system.
6 Dec
6 Dec
6:48 p.m.
Are some of the core SIP headers and others not? If they’re pretty consistent, checking
for a single one like “i” for Call-ID is a safe bet.
—
Sent from mobile, with due apologies for brevity and errors.
On Dec 6, 2021, at 12:43 PM, Brooks Bridges
<bbridges(a)call48.com> wrote:
We have an internal component of our callflow that does not support compact headers
(vendor says it's on the roadmap but no eta, etc) so I'm trying to find a clean
way to detect if a message has compact headers and reject it. I haven't had much luck
in finding a way to identify specifically if any of the headers of the message are compact
however. Can anyone point me in a direction please?
Thanks!
Confidentiality Notice: This e-mail, and any attachment to it, contains privileged and
confidential information intended only for the use of the individual(s) or entity named on
the e-mail. If the reader of this e-mail is not the intended recipient, or the employee or
agent responsible for delivering it to the intended recipient, you are hereby notified
that reading this e-mail is strictly prohibited. If you have received this e-mail in
error, please immediately return it to the sender and delete it from your system.
__________________________________________________________
Kamailio - Users Mailing List - Non Commercial Discussions
* sr-users(a)lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the sender!
Edit mailing list options or unsubscribe:
* https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
7:15 p.m.
It appears that it's just the "major" ones, From, To, Call-ID, etc. Where
I'm running into the issue is actually detecting the header being "i:"
instead of "Call-ID:" as pretty much everything I've found for parsing that
data is based on the content not the header name itself.
-----Original Message-----
From: sr-users <sr-users-bounces(a)lists.kamailio.org> On Behalf Of Alex Balashov
Sent: Monday, December 6, 2021 9:49 AM
To: Kamailio (SER) - Users Mailing List <sr-users(a)lists.kamailio.org>
Subject: Re: [SR-Users] detecting compact headers?
Are some of the core SIP headers and others not? If they’re pretty consistent, checking
for a single one like “i” for Call-ID is a safe bet.
—
Sent from mobile, with due apologies for brevity and errors.
On Dec 6, 2021, at 12:43 PM, Brooks Bridges
<bbridges(a)call48.com> wrote:
We have an internal component of our callflow that does not support compact headers
(vendor says it's on the roadmap but no eta, etc) so I'm trying to find a clean
way to detect if a message has compact headers and reject it. I haven't had much luck
in finding a way to identify specifically if any of the headers of the message are compact
however. Can anyone point me in a direction please?
Thanks!
Confidentiality Notice: This e-mail, and any attachment to it, contains privileged and
confidential information intended only for the use of the individual(s) or entity named on
the e-mail. If the reader of this e-mail is not the intended recipient, or the employee or
agent responsible for delivering it to the intended recipient, you are hereby notified
that reading this e-mail is strictly prohibited. If you have received this e-mail in
error, please immediately return it to the sender and delete it from your system.
__________________________________________________________
Kamailio - Users Mailing List - Non Commercial Discussions
* sr-users(a)lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the sender!
Edit mailing list options or unsubscribe:
* https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
__________________________________________________________
Kamailio - Users Mailing List - Non Commercial Discussions
* sr-users(a)lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the sender!
Edit mailing list options or unsubscribe:
* https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Confidentiality Notice: This e-mail, and any attachment to it, contains privileged and
confidential information intended only for the use of the individual(s) or entity named on
the e-mail. If the reader of this e-mail is not the intended recipient, or the employee or
agent responsible for delivering it to the intended recipient, you are hereby notified
that reading this e-mail is strictly prohibited. If you have received this e-mail in
error, please immediately return it to the sender and delete it from your system.
9:02 p.m.
Hello,
there might be a more elegant way, but one idea would be to use one of the regular
expression matches from textops (search(..)) to look for the compact header names.
It would be probably a good idea to add a transformation to output the type of the
header.
Cheers,
Henning
--
Henning Westerholt – https://skalatan.de/blog/
Kamailio services – https://gilawa.com
-----Original Message-----
From: sr-users <sr-users-bounces(a)lists.kamailio.org> On Behalf Of Brooks Bridges
Sent: Monday, December 6, 2021 7:16 PM
To: Kamailio (SER) - Users Mailing List <sr-users(a)lists.kamailio.org>
Subject: Re: [SR-Users] detecting compact headers?
It appears that it's just the "major" ones, From, To, Call-ID, etc. Where
I'm running into the issue is actually detecting the header being "i:"
instead of "Call-ID:" as pretty much everything I've found for parsing that
data is based on the content not the header name itself.
-----Original Message-----
From: sr-users <sr-users-bounces(a)lists.kamailio.org> On Behalf Of Alex Balashov
Sent: Monday, December 6, 2021 9:49 AM
To: Kamailio (SER) - Users Mailing List <sr-users(a)lists.kamailio.org>
Subject: Re: [SR-Users] detecting compact headers?
Are some of the core SIP headers and others not? If they’re pretty consistent, checking
for a single one like “i” for Call-ID is a safe bet.
—
Sent from mobile, with due apologies for brevity and errors.
On Dec 6, 2021, at 12:43 PM, Brooks Bridges
<bbridges(a)call48.com> wrote:
We have an internal component of our callflow that does not support compact headers
(vendor says it's on the roadmap but no eta, etc) so I'm trying to find a clean
way to detect if a message has compact headers and reject it. I haven't had much luck
in finding a way to identify specifically if any of the headers of the message are compact
however. Can anyone point me in a direction please?
Thanks!
Confidentiality Notice: This e-mail, and any attachment to it, contains privileged and
confidential information intended only for the use of the individual(s) or entity named on
the e-mail. If the reader of this e-mail is not the intended recipient, or the employee or
agent responsible for delivering it to the intended recipient, you are hereby notified
that reading this e-mail is strictly prohibited. If you have received this e-mail in
error, please immediately return it to the sender and delete it from your system.
__________________________________________________________
Kamailio - Users Mailing List - Non Commercial Discussions
* sr-users(a)lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the sender!
Edit mailing list options or unsubscribe:
* https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
__________________________________________________________
Kamailio - Users Mailing List - Non Commercial Discussions
* sr-users(a)lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the sender!
Edit mailing list options or unsubscribe:
* https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Confidentiality Notice: This e-mail, and any attachment to it, contains privileged and
confidential information intended only for the use of the individual(s) or entity named on
the e-mail. If the reader of this e-mail is not the intended recipient, or the employee or
agent responsible for delivering it to the intended recipient, you are hereby notified
that reading this e-mail is strictly prohibited. If you have received this e-mail in
error, please immediately return it to the sender and delete it from your system.
__________________________________________________________
Kamailio - Users Mailing List - Non Commercial Discussions
* sr-users(a)lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the sender!
Edit mailing list options or unsubscribe:
* https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
865
days inactive
865
days old
3 comments
3 participants
participants (3)
-
Alex Balashov -
Brooks Bridges -
Henning Westerholt