Thanks Henning, the problem described in the issue 3090 https://github.com/kamailio/kamailio/issues/3090 looks very similar to mine; I will organise myself to test the patch.

Thanks, have a nice day

Giovanni

On Wed, Apr 27, 2022 at 7:47 PM Henning Westerholt hw@gilawa.com wrote:

Hello,

did you also looked into this: https://github.com/kamailio/kamailio/issues/3090

There is a commit references in the issue, in case you want to test it.

Cheers,

Henning

--

Henning Westerholt – https://skalatan.de/blog/

Kamailio services – https://gilawa.com

*From:* sr-users sr-users-bounces@lists.kamailio.org *On Behalf Of *Giovanni Tommasini *Sent:* Tuesday, April 26, 2022 7:51 PM *To:* Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org *Subject:* [SR-Users] TOPOS, 183 (before a 200OK) and SIP INFO

Hi kamailiers,

I ask your help for a strange situation with topos, 183 (before a 200OK) and SIP INFO

My topology is kamailio in front of asterisks; so kamailio has 2 interfaces (1Public to talk with customers and carriers and 1 Private to talk with asterisk).

In the image:

• the first column is the customer

• the second is the public interface of kamailio

• the third is the private interface of kamaiio

• the fourth is asterisk

As you can see in the image, the customer send an INVITE and the carrier give back the IVR messages in a 183 (before a 200OK) asking for an IVR selection.

The customer (configured to use SIP INFO) types a key and sends in INFO, but as you can see kamailio sends the INFO to himself to private interface instead of sending it to asterisk as if the contact that handled topos contained incorrect information.

• If the customer is configured with a RFC2833

• or if the IVR messages is not in a 183 but is sent after a 200OK

• or if I disabe TOPOS

*all works fine*

I used kamailio 5.5.3, I also try to upgrade to 5.5.4 but nothing change

Maybe could be connected with

https://github.com/kamailio/kamailio/issues/2344

https://github.com/kamailio/kamailio/issues/1077

Could be a kamailio bug for this particular situation or am I getting lost in a glass of water?

thanks a lot

cheers

Giovanni Tommasini

*evoseed s.r.l.*

phone: +39 340 11 28 800 mail: giovanni.tommasini@evoseed.io site: evoseed.io address: Via Lucrezio 13, Trieste Italy

Hi Daniel,

I test my situation with the latest master branch (the last commit sha is 89495b8595d37f4d24e10e5ed1177614b2979d82) and I can confirm that all works fine now! Perfect bugfix. [image: Schermata 2022-04-28 alle 19.55.11.png]

Giovanni

On Thu, Apr 28, 2022 at 9:38 AM Daniel-Constantin Mierla miconda@gmail.com wrote:

Hello,

you should try with latest master branch, I just pushed a commit that should catch this case. Report back the results and if it fixes it, then it will be backported.

Cheers, Daniel On 28.04.22 09:28, Giovanni Tommasini wrote:

Thanks Henning, the problem described in the issue 3090 https://github.com/kamailio/kamailio/issues/3090 looks very similar to mine; I will organise myself to test the patch.

Thanks, have a nice day

Giovanni

On Wed, Apr 27, 2022 at 7:47 PM Henning Westerholt hw@gilawa.com wrote:

...

Hello,

did you also looked into this: https://github.com/kamailio/kamailio/issues/3090

There is a commit references in the issue, in case you want to test it.

Cheers,

Henning

--

Henning Westerholt – https://skalatan.de/blog/

Kamailio services – https://gilawa.com

*From:* sr-users sr-users-bounces@lists.kamailio.org *On Behalf Of *Giovanni Tommasini *Sent:* Tuesday, April 26, 2022 7:51 PM *To:* Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org *Subject:* [SR-Users] TOPOS, 183 (before a 200OK) and SIP INFO

Hi kamailiers,

I ask your help for a strange situation with topos, 183 (before a 200OK) and SIP INFO

My topology is kamailio in front of asterisks; so kamailio has 2 interfaces (1Public to talk with customers and carriers and 1 Private to talk with asterisk).

In the image:

• the first column is the customer

• the second is the public interface of kamailio

• the third is the private interface of kamaiio

• the fourth is asterisk

As you can see in the image, the customer send an INVITE and the carrier give back the IVR messages in a 183 (before a 200OK) asking for an IVR selection.

The customer (configured to use SIP INFO) types a key and sends in INFO, but as you can see kamailio sends the INFO to himself to private interface instead of sending it to asterisk as if the contact that handled topos contained incorrect information.

• If the customer is configured with a RFC2833

• or if the IVR messages is not in a 183 but is sent after a 200OK

• or if I disabe TOPOS

*all works fine*

I used kamailio 5.5.3, I also try to upgrade to 5.5.4 but nothing change

Maybe could be connected with

https://github.com/kamailio/kamailio/issues/2344

https://github.com/kamailio/kamailio/issues/1077

Could be a kamailio bug for this particular situation or am I getting lost in a glass of water?

thanks a lot

cheers

Giovanni Tommasini

*evoseed s.r.l.*

phone: +39 340 11 28 800 mail: giovanni.tommasini@evoseed.io site: evoseed.io address: Via Lucrezio 13, Trieste Italy

---

Kamailio - Users Mailing List - Non Commercial Discussions

• sr-users@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

-- Daniel-Constantin Mierla -- www.asipto.comwww.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio Advanced Training - Online

• https://www.asipto.com/sw/kamailio-advanced-training-online/