From voransoy at gmail.com Wed Jul 2 10:50:14 2025 From: voransoy at gmail.com (Volkan Oransoy) Date: Wed, 2 Jul 2025 11:50:14 +0100 Subject: [OpenSIPS-Users] Random auth realms Message-ID: Hi all I store user authentication data on a subscriber table with precalculated hashes for obvious reasons. Lately we are having issues with these new AI conversations services. They send requests with random realms, especially with IP addresses. What I understand, if I store the plain text password and calculate ha1 at request time, I can accept these requests even if the realm is different. But I don't want to do that. I tried to tweak auth_db, when I set `use_domain` to 0, Opensips does not add the realm to the query but still use is on ha1 challenge since the RFC requires I think. Is there a best practice to handle this issue? Best regards -- Volkan Oransoy -------------- next part -------------- An HTML attachment was scrubbed... URL: From joao.coucelo at celfocus.com Thu Jul 3 15:13:39 2025 From: joao.coucelo at celfocus.com (=?utf-8?B?Sm/Do28gQ291Y2Vsbw==?=) Date: Thu, 3 Jul 2025 15:13:39 +0000 Subject: [OpenSIPS-Users] b2b_logic bridge with no-late-sdp unable to get bentity1->to_uri Message-ID: Hi all, I successfully run the prepaid b2b_bridge scenario from https://opensips.org/Documentation/Tutorials-B2BUA-3-2 However, I cannot use the SDP less INVITE to initiate the connection with the "callee". Hence I was trying to use the "no-late-sdp", but I get an error when the SDPless 200 OK response from the "caller" is received. On the b2b_logic_request route I simply added two extra args: b2b_bridge("caller", "callee", "", "no-late-sdp"); The SPDless Re-INVITE 200 OK is received on process_bridge_200OK(), but it fails to get the bentity1->to_uri       DBG:b2b_logic:process_bridge_200OK: Send invite to [] Proxy [] When initiating the bridge, I can confirm that the new client entity is added correctly with the to_uri       DBG:b2b_logic:b2bl_entity_new: First new entity [callee] saved in context       opensips_1 | Jul 3 13:25:55 [10] DBG:b2b_logic:b2bl_bridge: New entity, dest = [sip:+351940026774 at 172.16.254.101:5060]       opensips_1 | Jul 3 13:25:55 [10] DBG:b2b_logic:b2bl_bridge: New entity, dest = [sip:+351940026774 at 172.16.254.101:5060]       opensips_1 | Jul 3 13:25:55 [10] DBG:b2b_logic:b2bl_create_new_entity: new entity type [1] [0x7f74039c9308]->[]       opensips_1 | Jul 3 13:25:55 [10] DBG:b2b_logic:bridging_start_old_ent: Send reInvite to old entity       opensips_1 | Jul 3 13:25:55 [10] DBG:b2b_logic:b2bl_create_new_entity: new entity type [1] [0x7f74039cb620]->[] Looking at the code, it appears to me the new_br_ent[1]->dest_uri is properly filled when preparing the bridge, and so the b2bl_create_new_entity() should be filling the to_uri and the returned entity properly stored on the tuple->bridge_entities[1] However, when receiving the 200 OK, there the same tuple->bridge_entities[1] returns no to_uri..       opensips_1 | Jul 3 13:25:55 [12] DBG:core:MD5StringArray: MD5 calculated: 38b99f724da7821223927ccebf7b95d6       opensips_1 | Jul 3 13:25:55 [12] DBG:b2b_entities:generate_tag: from_tag = 38b99f724da7821223927ccebf7b95d6-0668       opensips_1 | Jul 3 13:25:55 [12] DBG:core:parse_headers_aux: flags=ffffffffffffffff       opensips_1 | Jul 3 13:25:55 [12] DBG:tm:t_uac: next_hop=<>       opensips_1 | Jul 3 13:25:55 [12] ERROR:core:parse_uri: uri too short: <> (0)       opensips_1 | Jul 3 13:25:55 [12] ERROR:tm:uri2proxy: bad_uri:       opensips_1 | Jul 3 13:25:55 [12] ERROR:b2b_entities:_client_new: while sending request with t_request       opensips_1 | Jul 3 13:25:55 [12] ERROR:b2b_logic:b2bl_new_client: Failed to create client id       opensips_1 | Jul 3 13:25:55 [12] ERROR:b2b_logic:bridging_new_client: Failed to generate new client       opensips_1 | Jul 3 13:25:55 [12] ERROR:b2b_logic:_b2b_handle_reply: Failed to process bridging 200OK for Invite If there is an issue with the code, I cannot find it. Maybe I'm simply misusing this feature. Any thoughts? -------------- next part -------------- An HTML attachment was scrubbed... URL: From spanda at 3clogic.com Fri Jul 4 05:06:50 2025 From: spanda at 3clogic.com (Sasmita Panda) Date: Fri, 4 Jul 2025 10:36:50 +0530 Subject: [OpenSIPS-Users] Need some inforamtion on opensips change logs . Message-ID: I am using opensips 3.4 right now . I have the DB at aws RDS . If someone logged into the DB and made some changes to the table I am not getting that information stored anywhere . If I will talk about dynamic routing only (this module only can hamper my calls ) , any changes in the table at runtime , when my service get restarted Can I get the latest table information on the logs itself ? So that I can check from the logs what changes made in the DB before restart . If this is not possible , then what is the other way to do so ? Please suggest . I am stuck on soothing here before production live . *Thanks & Regards* *Sasmita Panda* *Senior Network Testing and Software Engineer* *3CLogic , ph:07827611765* -------------- next part -------------- An HTML attachment was scrubbed... URL: