Re: [SR-Users] Features of Kamailio as SBC

2022-01-04 Thread Mojtaba
Configuring Sems to work with Kamailio depends entirely on your network and
the scenario you want.
If you mean how Sems are configured, you can find it in the doc folder in
the source code.
cheers

On Mon, Jan 3, 2022 at 8:24 PM mohsen khashei  wrote:

> Hi can you share hkw to config sems and kamailio to work together as sbc
> (semes for signalling and kamailio+rtpengine for media)
> Thanks.
>
> On Mon, Jan 3, 2022, 8:03 PM Denys Pozniak 
> wrote:
>
>> Hello!
>>
>> We also have a similar experience with the sems, in the end, we came to
>> the conclusion that under heavy load and passing the RTP, it behaves
>> unstable.
>> Now we use sems only for SIP signaling processing and in conjunction with
>> Kamailio and Rtpengine, and in this mode it is excellent!
>>
>> If someone needs packages for Centos 7, then you can use the repository
>> (the building is triggered for each commit into sems-server master):
>> https://copr.fedorainfracloud.org/coprs/denysp/sems/
>>
>>
>> вс, 26 дек. 2021 г. в 11:28, Mojtaba :
>>
>>> I also have written some applications which use some of its SBC
>>> capabilities.
>>> I feel so happy that the SEMS works powerfully in signaling mode. For
>>> some reason, I don't anchor RTP sessions to SEMS and use a media server in
>>> Kamailio (LRKProxy).
>>> Because of the elasticity of each item, you might find some unusual
>>> manner in Sems, they are quite a topic that has no effect on Sems's overall
>>> behavior. For these cases, you can have contributions in solving them or
>>> using Kamailio.
>>>
>>> On Sun, Dec 26, 2021 at 11:17 AM Juha Heinanen  wrote:
>>>
 Alex Balashov writes:

 > I use SEMS myself and like it very much. It’s sad to see it fall away
 > and I regret that I personally lack the resources to prop it
 > up. Nevertheless, I think it’s a fact that it’s not a dependable input
 > in a future-proof way for lack of active public development and (much)
 > maintenance. I think in the most optimistic view it is merely “very
 > unpolished”.

 I too feel sad that SEMS development has stalled to minimal maintenance
 level.  I have written numerous applications from scratch using SEMS's
 DSM scripts (call center, conference, voicemail, ivr apps, charging,
 ...)  plus I'm using some of its SBC capabilities.  As long as there is
 no alternative, for me it is the only way to go.

 -- Juha

 __
 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

>>>
>>>
>>> --
>>> --Mojtaba Esfandiari.S
>>> __
>>> 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
>>>
>>
>>
>> --
>>
>> BR,
>> Denys Pozniak
>>
>>
>> __
>> 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
>>
> __
> 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
>


-- 
--Mojtaba Esfandiari.S
__
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


Re: [SR-Users] Recommendation for compatible IMS soft phones

2022-01-04 Thread Mojtaba
Have you checked Boghe IMS client?
https://boghe-ims-client.software.informer.com/1.0/

Best Regards

*-- Mojtaba Esfandiari.S*

*-- PhD student and Research Affiliate, *

*-- Technical Manager at IP-PBX Laboratory, Ferdowsi University of Mashhad,
Iran.*

-- Address: IP-PBX Lab., Engineering Faculty, Ferdowsi University-Main
Campus, Mashhad, Iran.

-- Mobile: +98-915-117-6713

On Tue, Jan 4, 2022 at 10:41 AM Ashay Matekar 
wrote:

> Hi Team,
>
> We were trying to test a call flow with Kamailio IMS that requires
> preconditio.
>
> Do you know any free or paid IMS softphones that support preconditio and
> are compatible with Kamailio IMS.
>
>
>
> --
>
> *Thanks and Regards,*
>
>
> *Ashay Matekar*
>
> Associate Manager Engineering | +91 932446823
>
> Great Software Laboratory | www.gslab.com
> LinkedIn  | Twitter
>  | Email Disclaimer
> 
>
> Confidentiality Notice and Disclaimer: This email (including any
> attachments) contains information that may be confidential, privileged
> and/or copyrighted. If you are not the intended recipient, please notify
> the sender immediately and destroy this email. Any unauthorized use of the
> contents of this email in any manner whatsoever, is strictly prohibited. If
> improper activity is suspected, all available information may be used by
> the sender for possible disciplinary action, prosecution, civil claim or
> any remedy or lawful purpose. Email transmission cannot be guaranteed to be
> secure or error-free, as information could be intercepted, lost, arrive
> late, or contain viruses. The sender is not liable whatsoever for damage
> resulting from the opening of this message and/or the use of the
> information contained in this message and/or attachments. Expressions in
> this email cannot be treated as opined by the sender company management –
> they are solely expressed by the sender unless authorized.
> __
> 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
>


-- 
--Mojtaba Esfandiari.S
__
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


[SR-Users] Fwd: Catching Register 200 OK, then using it to validate other packets.

2022-01-04 Thread Richard Edmands
Hey Thanks for that one Alex,

If only I hadn't stopped reading at "will send 200 OK"...

I've been doing some more poking at this one, I was having issues with
it so I simplified it down to the basics with both of these code
blocks next to each other.

I can see the contact appear in kamcmd ul.dump as well as the [MAIN]
REGISTERRESPONSE in the log file. The log file also creates the lines
for all three case statements and the phone gets the 404 not
registered.

Not sure why it's not matching in this simplified configuration as the
steps are right after eachother the contact fields should be lining up
without issue.

I've also been playing with these modparams in case they were related,
but I haven't found the right combo if they are the issue.
modparam("registrar", "method_filtering", 0)
modparam("registrar", "gruu_enabled", 0)
#modparam("usrloc", "nat_bflag", 0)
modparam("usrloc", "matching_mode", 0)



# LetsCaptureAnyRegister...
if (src_ip!=PBXIP) {
if (is_method("REGISTER")) {
xlog("L_INFO", "[MAIN] REGISTERRESPONSE\n");
save("location", "0x02");
}   
}



# Then lets verify it...
if ($src_ip!="PBXIP") {
if (!is_method("REGISTER")) {
if(!lookup("location")) {#Try looking up location

switch($rc) {
case -1:
xlog("L_INFO", "[MAIN] case -1\n");
case -2:
xlog("L_INFO", "[MAIN] case -2\n");
case -3:
xlog("L_INFO", "[MAIN] case -3\n");

}



sl_reply("404", "User not Registered");
#If looking up location fails reply with 404
exit;
  #And exit
} else {
xlog("L_INFO", "[MAIN] 
PASSEDREGISTERVALIDATION\n");
}
}
}


I had email digest emailed... I'm guessing this response isn't going
to align correctly on the maillist.




*Alex Balashov*
abalashov at evaristesys.com

   *Tue Jan  4 06:55:52 CET 2022*

Hi Richard,

If I’ve understood your query correctly, flag 0x02 to save() should
accomplish what you want:
https://kamailio.org/docs/modules/5.5.x/modules/registrar.html#registrar.f.save

— Alex



-- Forwarded message -
From: Richard Edmands 
Date: Tue, 4 Jan 2022 at 15:53
Subject: Catching Register 200 OK, then using it to validate other packets.
To: 


Hey Kamailio Users,

I've written a TLS-UDP gateway. It works well, but I want to reduce the
internet noise it pushes through.

I have an idea on what I'd like to try. Wondering if it would be possible
to catch the Register 200 OK, store it and then when receiving packets it
future to then validate them against the data?
I've managed to capture a 200 OK, but the save("location") function says it
will return it's own 200 OK which isn't the plan since we just want to
capture the location.

Anyone done something similar and got some working example code? Is this a
bad idea for some reason?
__
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