Hello Daniel,
We moved to the latest 5.2.4 but hostname with underscore are still not
handle properly.
Is it a real design choice or a mistake somewhere in the code that handle
domain name?
Regards,
Igor.
De : igor.potjevle...@gmail.com
Envoyé : mardi 27 août 2019 11:53
À :
Hello,
reading again I see that the error with the host uri is printed from the
C code. I thought of another issue that was reported related to IPv6
addresses in the URI that kamctl rejected.
The problem is that the underscore is not allowed in hostname: the
relevant standard is RFC 1123,
Hello,
Indeed, the max gateway number is defaulting to 128 in the code :
#define DEF_LCR_GW_COUNT 128
You can modify it with a mod parameter :
modparam("lcr", "lcr_gw_count", 200)
Kind regards,
Mathieu Bodjikian
De : sr-users de la part de Laura
Greetings,
I have two Kamailio's working on a HA scenario. Both Kamailio's have DB
replication and each machine has one HA IP. In order to set this up, i have
every GW on the DB duplicated, one with Socket IPA and another with socket
IPB.
I have both GWs in a active state configurated in the
Hi guys,
on our enviromet we have 130+ gateway configured over the LCR_gw tables.
when we try to reload it.. we get error..
"Aug 28 09:40:36 vm-nextaitz-02 /usr/sbin/kamailio[3800]: ERROR: lcr
[lcr_mod.c:1511]: reload_tables(): too many gateways"
We reached some top values.. how can we
Greetings,
I did some testing and onsend route is not executed on local generated
requests.
I asked if they work the same way because for relayed requests, the on send
is the last route before sending the packet.
I'm asking this because I'm trying to debug an issue with my probings via
Yes... found it..
sorry for the stupid question..
thanks for support.
Il 28/08/19 11:55, Mathieu Bodjikian ha scritto:
Hello,
Indeed, the max gateway number is defaulting to 128 in the code :
#define DEF_LCR_GW_COUNT 128
You can modify it with a mod parameter :
modparam("lcr",
Yes, i only want to disable it on one Kamailio.
A quarta, 28/08/2019, 11:32, Duarte Rocha
escreveu:
> Greetings,
>
> I have two Kamailio's working on a HA scenario. Both Kamailio's have DB
> replication and each machine has one HA IP. In order to set this up, i have
> every GW on the DB
You want to disable it on only one kamailio, correct?
On Wed, 28 Aug 2019 at 12:34, Duarte Rocha wrote:
> Greetings,
>
> I have two Kamailio's working on a HA scenario. Both Kamailio's have DB
> replication and each machine has one HA IP. In order to set this up, i have
> every GW on the DB
Hello,
what's best practice for VoiceMail implementation in Kamailio+Asterisk's
scheme?
should I forward register into asterisk? Or I can keep register on
kamailio?
Could you, please, shed any lights on this
___
Kamailio (SER) - Users Mailing List
Why not just calling dispatcher.set_state directly to the kamailio? That
would only set the state in memory. Unless you do a reload.
On Wed, 28 Aug 2019 at 13:21, Duarte Rocha wrote:
> Yes, i only want to disable it on one Kamailio.
>
> A quarta, 28/08/2019, 11:32, Duarte Rocha
> escreveu:
>
Hello,
Hmm, ok. Saw it.
Is it possible to reconsider a less strict control?
Regards,
Igor.
De : Daniel-Constantin Mierla
Envoyé : mercredi 28 août 2019 10:25
À : igor.potjevle...@gmail.com; 'Kamailio (SER) - Users Mailing List'
Objet : Re: [SR-Users] lookup(aliases) issues with
Hello,
I'm trying to make Kamailio to SIP register on a remote server. However storing
plaintext password looks very unsecure.
Is there a possibility to store password for uac module using ha1 hash instead
of the plaintext password? I see there's a row for it in the database, but in
the source
> Why not just calling dispatcher.set_state directly to the kamailio? That
would only set the state in memory. Unless you do a reload.
Set_state works with gw uri and group as argument. In this scenario both
gws have the same uri and group and i only want to disable the one that has
a socket that
Can I fire REGISTER's w/o authentication but then process 401/407 in a failure
route and somehow tell UAC module which ha1 to use? Keeping all the timers
functionality and uac_reg_lookup feature? Or at least if I process 401/407 in a
failure_route and manually create the Auth header, will UAC
Hello,
indeed, it seems to be no support to use the ha1 form of password for
uac module remote registrations. Probably it was is some plans at some
point because the column is there, but it was not implemented so far --
or it was just a cloning of columns from subscriber table.
Not sure about
On 28.08.19 16:54, Alexandru Covalschi wrote:
> Can I fire REGISTER's w/o authentication but then process 401/407 in a
> failure route and somehow tell UAC module which ha1 to use? Keeping
> all the timers functionality and uac_reg_lookup feature? Or at least
> if I process 401/407 in a
Thank you for your feedback, I will first try playing with event route, i'm in
KEMI anyway, however I also think extending the module is a go-for.
Regards,
Alexandru Covalschi
VoIP Engineer and System Administrator
tel: +37367367850
> 28 авг. 2019 г., в 20:56,
Hi all:
I am trying to use the procedure for setting BLF lights described in
https://blog.voipxswitch.com/2018/02/22/kamailio-controlling-presence-with-new-module-pua_json/#comment-587
WIthout success.
My configuration is 1 Grandstream GXP2130 phone behind a NAT on a public
IP. (IPP in
Hello,
I haven't authored that patch and also never needed an underscore in
host part of the URI, but also it didn't affect me before that change. I
guess Juha wanted o be compliant with the RFC.
If people need to allow an extended set of chars in the host part, I am
fine to add some parameter
Hello Igor,
the problem is that this code belongs to the core parser part, it is not
something usrloc module related.
If you need a workaround, probably the easist and fastest option would be to
just build an own kamailio without this change (e.g. apply the patch in reverse
mode).
Cheers,
Hello Alexandru,
you are right, right now the ha1 value in the database is not used from the uac
registration functionality. This could be added similar to the functionality in
auth_db, I think. If you need some pointers for an extension of the code, let
us know on sr-dev list.
I don't think
Hello Bill,
just giving some generic debug pointers here:
- do you see any errors in the kamailio log file?
- do you see any SIP traffic (e.g. by observing with ngrep, wireshark
etc..) to the phone after your curl command?
Cheers,
Henning
Am 28.08.19 um 19:04 schrieb b...@novatrope.us:
> Hi
On Wednesday, August 28, 2019 6:37:43 AM CDT Zhan Bazarov wrote:
> Hello,
>
> what's best practice for VoiceMail implementation in Kamailio+Asterisk's
> scheme?
>
> should I forward register into asterisk? Or I can keep register on
> kamailio?
> Could you, please, shed any lights on this
I
Gotcha. I have a similar scenario. I use SQLops to set a gw status to 4
where it’s ATTRS is “whatever” and reload ds_reload()
That might work for you as well.
On Wed, 28 Aug 2019 at 16:36, Duarte Rocha wrote:
> > Why not just calling dispatcher.set_state directly to the kamailio? That
> would
25 matches
Mail list logo
