Good that you solved it and thanks for providing feedback, helpful for others in the future.

Cheers,

Henning

From: Giovanni Iamonte <iamonte@quintetto.it>
Sent: Wednesday, October 19, 2022 5:30 PM
To: Henning Westerholt <hw@gilawa.com>; Kamailio (SER) - Users Mailing List <sr-users@lists.kamailio.org>
Subject: Re: [SR-Users] IMC module

Hello,

I managed to figure out the issue and maybe it will help other people.

Basically what i did is to avoid to challenge the kamailio request by adding this line in route[AUTH]

#!ifdef WITH_IMC
#prevent digest authentication for messages sent by IMC via outbound_proxy, where in our case the outbound_proxy is the same server
# modparam("imc", "outbound_proxy", "sip:sip-test.quintetto.it:15006;transport=tcp")
#

if(is_method("MESSAGE") && $si == $Ri)
return;
#!endif

Just to be sure I would like to ask if this is an effective solution or there is a more canonical way to solve the issue.

Many Thanks in advance.

Bye

Ing. Giovanni Iamonte
Developments and technologies area
Quintetto Srl
Via Monte Navale, 1
10015 - Ivrea (TO)
( mobile: +39 393 9196310
( tel: +39 0165 1845290
+ e-mail: giovanni.iamonte@quintetto.it
[ web: www.quintetto.it

On 17/10/22 20:36, Giovanni Iamonte wrote:

Thanks for you reply.

Very basic configuration for the kamailio.cfg file, I have taken it from the repository and I have added what they suggested in the IMC module.

No errors in the log file.

I cannot change the release, anyway I will take in considerations you suggestion and try also with the next versions.

Bye

Ing. Giovanni Iamonte
Developments and technologies area
Quintetto Srl
Via Monte Navale, 1
10015 - Ivrea (TO)
( mobile: +39 393 9196310
( tel: +39 0165 1845290
+ e-mail: giovanni.iamonte@quintetto.it
[ web: www.quintetto.it

On 17/10/22 17:25, Henning Westerholt wrote:

Hello,

my first suggestion would be to use a support release, e.g. 5.5.x or 5.6.x. These releases contains also some improvements/bug fixes related to the IMC module.

Not an expert in the IMC module by myself, but it looks like a wrong configuration or some mistake in the routing script if the SIP message is not routed correctly. Maybe somebody else can comment on that as well.

Do you see any errors in the kamailio log files?

Cheers,

Henning

From: sr-users <sr-users-bounces@lists.kamailio.org> On Behalf Of Giovanni Iamonte
Sent: Monday, October 17, 2022 4:46 PM
To: sr-users@lists.kamailio.org
Subject: [SR-Users] IMC module

HI,

I am facing a problem related to the IMC module.

I have installed kamailio 5.2.x and I tried to list the members of a room-qsipchat.

In my test environment the kamailio.cfg file it is very basic, the kamailio server listen on
tcp=192.168.100.192:15006

the client run on a PC with IP address 192.168.100.156

the imc outbound_proxy is set
modparam("imc", "db_url", DBURL)
modparam("imc", "imc_cmd_start_char", "#")
modparam("imc", "outbound_proxy", "sip:sip-test.quintetto.it:15006;transport=tcp")

The client start by sending a #join message to kamailio and looking the log file I can see that the room-qsipchat has been create, and also I received the message 200 OK.

By using the tcpdump I can see the join message from the Client to kamailio server and the reply from kamailio to the client.

When I send the #list message to the room-qsipchat , I expecting to receive the message relate to room's members and the 200 OK message.

When I tcp dumping I saw the following messages

********************************************************************
Request from client to list the members - from client to server

********************************************************************

TX 538 bytes Request msg MESSAGE/cseq=57652 (tdta0x77b26460a8) to TCP 192.168.100.192:15006:
    MESSAGE sip:room-qsipchat@sip-test.quintetto.it SIP/2.0
    Via: SIP/2.0/TCP 192.168.100.156:48129;rport;branch=z9hG4bKPjRzgOBgY6vfKZ8Fh8GA4CWheCO840Xzud;alias
    Max-Forwards: 70
    From: <sip:quintetto00@sip-test.quintetto.it>;tag=1is.Ng6ZKJmCT1uAJ9WuJhe3hiQysj9f
    To: <sip:room-qsipchat@sip-test.quintetto.it>
    Call-ID: GwOQMLFfIq7o7jvF4OQlJ-jBb2OBaAKY
    CSeq: 57652 MESSAGE
    Accept: text/plain, application/im-iscomposing+xml
    Route: <sip:sip-test.quintetto.it:15006;transport=tcp;lr>
    Content-Type: text/plain
    Content-Length:     5

    #list

********************************************************************
The server ask for the authentication - from server to client

********************************************************************

2022-10-17 15:45:25.837 4700-10610/it.quintetto.qsipchat D/pjlib(pjsua_1): RX 574 bytes Response msg 407/MESSAGE/cseq=57652 (rdata0x77b3337330) from TCP 192.168.100.192:15006:
    SIP/2.0 407 Proxy Authentication Required
    Via: SIP/2.0/TCP 192.168.100.156:48129;rport=48129;branch=z9hG4bKPjRzgOBgY6vfKZ8Fh8GA4CWheCO840Xzud;alias;received=192.168.100.156
    From: <sip:quintetto00@sip-test.quintetto.it>;tag=1is.Ng6ZKJmCT1uAJ9WuJhe3hiQysj9f
    To: <sip:room-qsipchat@sip-test.quintetto.it>;tag=1e5fbdd4b14eff95c400342f4634da91.e417
    Call-ID: GwOQMLFfIq7o7jvF4OQlJ-jBb2OBaAKY
    CSeq: 57652 MESSAGE
    Proxy-Authenticate: Digest realm="sip-test.quintetto.it", nonce="Y01doWNNXHVEyRtiAyN28xJdMjNIG8Ju"
    Server: kamailio (5.2.8 (x86_64/linux))
    Content-Length: 0


*********************************************************************
The client send the authenticated request - from client to server

********************************************************************

TX 755 bytes Request msg MESSAGE/cseq=57653 (tdta0x77b26460a8) to TCP 192.168.100.192:15006:
    MESSAGE sip:room-qsipchat@sip-test.quintetto.it SIP/2.0
    Via: SIP/2.0/TCP 192.168.100.156:48129;rport;branch=z9hG4bKPjj6uuy25r0kKlnICHKQWEaIweOex-sNyq;alias
    Max-Forwards: 70
    From: <sip:quintetto00@sip-test.quintetto.it>;tag=1is.Ng6ZKJmCT1uAJ9WuJhe3hiQysj9f
    To: <sip:room-qsipchat@sip-test.quintetto.it>
    Call-ID: GwOQMLFfIq7o7jvF4OQlJ-jBb2OBaAKY
    CSeq: 57653 MESSAGE
    Accept: text/plain, application/im-iscomposing+xml
    Route: <sip:sip-test.quintetto.it:15006;transport=tcp;lr>
    Proxy-Authorization: Digest username="quintetto00", realm="sip-test.quintetto.it", nonce="Y01doWNNXHVEyRtiAyN28xJdMjNIG8Ju", uri="sip:room-qsipchat@sip-test.quintetto.it", response="d495ec20cb1be8f1b605d4e5b1a4c357"
    Content-Type: text/plain
    Content-Length:     5

    #list


**************************************************************************
The server send the 200 OK message - from server to client

********************************************************************

RX 447 bytes Response msg 200/MESSAGE/cseq=57653 (rdata0x77b3337330) from TCP 192.168.100.192:15006:
    SIP/2.0 200 ok
    Via: SIP/2.0/TCP 192.168.100.156:48129;rport=48129;branch=z9hG4bKPjj6uuy25r0kKlnICHKQWEaIweOex-sNyq;alias;received=192.168.100.156
    From: <sip:quintetto00@sip-test.quintetto.it>;tag=1is.Ng6ZKJmCT1uAJ9WuJhe3hiQysj9f
    To: <sip:room-qsipchat@sip-test.quintetto.it>;tag=1e5fbdd4b14eff95c400342f4634da91.365f
    Call-ID: GwOQMLFfIq7o7jvF4OQlJ-jBb2OBaAKY
    CSeq: 57653 MESSAGE
    Server: kamailio (5.2.8 (x86_64/linux))
    Content-Length: 0



*********************************************************************************
Till here everything is OK.

But regarding the members when a TCP dumping I saw a message with the room's members
that go from the kamailio server to the kamailio server

*********************************************************************************

MESSAGE sip:quintetto00@sip-test.quintetto.it SIP/2.0
   Via: SIP/2.0/TCP 192.168.100.192:15006;branch=z9hG4bKf20a.be253b92000000000000000000000000.0
   To: <sip:quintetto00@sip-test.quintetto.it>
   From: <sip:room-qsipchat@sip-test.quintetto.it>;tag=03e4c67b0f95c0aeb1f633479b4aa5cd-72f2
   CSeq: 10 MESSAGE
   Call-ID: 37db44aa523ea24a-6567@192.168.100.192
   Max-Forwards:.70
   Content-Length: 47
   User-Agent: kamailio (5.2.8 (x86_64/linux))
   Content-Type: text/plain

   Members:
   *sip:quintetto00@sip-test.quintetto.it

**************************************************************************************
a reply from the kamailio server to the kamailio server, with an authenticated request

**************************************************************************************

SIP/2.0.407.Proxy Authentication.Required
Via: SIP/2.0/TCP 192.168.100.192:15006;branch=z9hG4bKf20a.be253b92000000000000000000000000.0
To: <sip:quintetto00@sip-test.quintetto.it>;tag=1e5fbdd4b14eff95c400342f4634da91.cfc3
From: <sip:room-qsipchat@sip-test.quintetto.it>;tag=03e4c67b0f95c0aeb1f633479b4aa5cd-72f2
CSeq: 10 MESSAGE
Call-ID: 37db44aa523ea24a-6567@192.168.100.192
Proxy-Authenticate: Digest realm="sip-test.quintetto.it", nonce="Y01fQmNNXhbsHdM1THmENyJn1MH/VD/8"
Server: kamailio (5.2.8 (x86_64/linux))
Content-Length:.0

**************************************************************************************
bottom of line the outbound_proxy request for an authenticated request, but kamailio do not reply to this request.

Could you please point me in the right direction?

Thanks a lot for any help.

Bye

--

Ing. Giovanni Iamonte
Developments and technologies area
Quintetto Srl
Via Monte Navale, 1
10015 - Ivrea (TO)
( mobile: +39 393 9196310
( tel: +39 0165 1845290
+ e-mail: giovanni.iamonte@quintetto.it
[ web: www.quintetto.it
__________________________________________________________
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