[SR-Users] Recommendation for compatible IMS soft phones

[Ashay Matekar]

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

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

[Alex Balashov]

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

> On Jan 4, 2022, at 12:53 AM, Richard Edmands  wrote:
> 
> 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

-- 
Alex Balashov | Principal | Evariste Systems LLC

Tel: +1-706-510-6800 / +1-800-250-5920 (toll-free)
Web: http://www.evaristesys.com/, http://www.csrpswitch.com/


__
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] Catching Register 200 OK, then using it to validate other packets.

[Richard Edmands]

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

Re: [SR-Users] Problem with auth_ephemeral and parse_uri(): bad port in uri

[Henning Westerholt]

Hello,

have you already tried to use the default username format "1", the IETF format? 
This might be better for Kamailio.

If this solves the problem, the mode 0 should probably be removed then.

Cheers,

Henning

-- 
Henning Westerholt – https://skalatan.de/blog/
Kamailio services – https://gilawa.com

-Original Message-
From: sr-users  On Behalf Of Vlasis 
Chatzistavrou
Sent: Sunday, January 2, 2022 8:37 PM
To: sr-users@lists.kamailio.org
Subject: [SR-Users] Problem with auth_ephemeral and parse_uri(): bad port in uri

Hello,

I have a problem with Kamailio 5.4.6 and auth_ephemeral. I have the following 
in the Kamailio configuration

loadmodule "auth_ephemeral"
     modparam( "auth_ephemeral", "sha_algorithm", 3 )
     modparam( "auth_ephemeral", "username_format", 0 )
     modparam( "auth_ephemeral", "secret", 1234 )

as per

https://kamailio.org/docs/modules/4.1.x/modules/auth_ephemeral.html#auth_eph.p.username_format

and registrations fail. In the logs we see:

Jan  2 18:21:10 enswitch43 /sbin/kamailio[37501]: DEBUG: {1 545 REGISTER 
rhaqgafd7boteg24jp5db0} sanity [sanity.c:777]: check_parse_uris(): 
looking up From header
Jan  2 18:21:10 enswitch43 /sbin/kamailio[37501]: DEBUG: {1 545 REGISTER 
rhaqgafd7boteg24jp5db0} sanity [sanity.c:817]: check_parse_uris(): 
parsing From URI
Jan  2 18:21:10 enswitch43 /sbin/kamailio[37501]: DEBUG: {1 545 REGISTER 
rhaqgafd7boteg24jp5db0}  [core/parser/parse_uri.c:1296]: 
parse_uri(): bad port in uri (error at char 5 in state 2) parsed: 
(17) / (35) Jan  2 
18:21:10 enswitch43 /sbin/kamailio[37501]: WARNING: {1 545 REGISTER 
rhaqgafd7boteg24jp5db0} sanity [sanity.c:820]: 
check_parse_uris(): failed to parse From uri


Apparently Kamailio is confused by the timestamp following the username 
separated by the : character. The REGISTER message is below:

REGISTER sip:192.168.2.99 SIP/2.0
Via: SIP/2.0/WSS 192.0.2.202;branch=z9hG4bK5452321
Max-Forwards: 70
To: "3518929" 
From: "3518929" ;tag=ht76o8b2b6
Call-ID: phkj9mi2n3s3ju7uu3qq2f
CSeq: 274 REGISTER
Contact: 
;reg-id=1;+sip.instance="";expires=300
Allow: ACK,CANCEL,INVITE,MESSAGE,BYE,OPTIONS,INFO,NOTIFY,REFER
Supported: path, gruu, outbound
User-Agent: Raspberry Phone (SipJS - 0.11.6)
Content-Length: 0

and Kamailio parses it as sip:: instead of 
sip::.

Is this a bug that should be reported or is there any setting that I am missing?


__
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

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

[Denys Pozniak]

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