Hi!
I have a phone (Mitel 6930) that does not send an Expire-header but
"expire" in Contact during REGISTER:
Session Initiation Protocol (REGISTER)
> Request-Line: REGISTER sip:pbx.example.com SIP/2.0
> Message Header
> Via: SIP/2.0/TLS 192.168.6.16:5061;branch=xxxxxxxxxxxxxxxx;rport
> Route: <sip:pbx.example.com;lr=lr;transport=tls>
> Max-Forwards: 70
> From: "Example" <sip:121212_6666@pbx.example.com>;tag=b0cec92c3e
> To: "Example" <sip:121212_6666@pbx.example.com>
> Call-ID: aaaaaaaaaaaaaaaaa
> CSeq: 1190442896 REGISTER
> Accept-Language: de
> Allow: INVITE, ACK, CANCEL, BYE, NOTIFY, REFER, OPTIONS, UPDATE,
> PRACK, SUBSCRIBE, INFO, PUBLISH
> Allow-Events: talk, hold, conference, LocalModeStatus
> Contact: "Example" <sip:121212_6666@192.0.2.1:62336
> >;+sip.instance="<urn:uuid:00000000-0000-1000-8000-08000FB888F5>";expires=300
> Supported: path, gruu
> User-Agent: Mitel 6930/5.0.0.2041
> Aastra-Line: 1
> Aastra-Mac: AAAAAAAAAAAA
> Content-Length: 0
This results in successful register, kamailio forwards REGISTER to asterisk
(endpoint registered) and immediatly kamailio sends a new REGISTER with
Expire set to 0 to asterisk:
Session Initiation Protocol (REGISTER)
> Request-Line: REGISTER sip:192.168.99.112:5060 SIP/2.0
> Message Header
> Via: SIP/2.0/UDP 192.168.99.111:5060
> ;branch=z9hG4bK9f9e.599cf243000000000000000000000000.0
> To: <sip:121212_6666@192.168.99.112>
> From: <sip:121212_6666@192.168.99.112
> >;tag=7e4f6993bfbf831f6b016fea6683cdca-b98a
> CSeq: 10 REGISTER
> Call-ID: 2bc5fd1061b31723-1350(a)192.168.99.111
> Max-Forwards: 70
> Content-Length: 0
> User-Agent: kamailio (5.1.6 (x86_64/linux))
> Contact: <sip:121212_6666@192.168.99.111:5060>
> Expires: 0
The phone is then unregistered - the phone also shows "no service". It
looks like Kamailio generates this message on it's own (and I don't know
why).
I am still learning to implement kamailio as proxy. Reading the docs, I
would expect Kamailio to automatically eval the correct parameter:
> If the processed message contains neither Expires HFs nor expires contact
> parameters, this value will be used for newly created usrloc records.
[1]
What did I miss?
Phones which use the Expire-header are working fine.
Kind regards
Kevin
[1] default_expires -
http://www.kamailio.org/docs/modules/5.2.x/modules/registrar.html
Hi!
Can someone share his kamailio.cfg with working busy lamp field in a
kamailio-as-proxy scenario?
My config is based on the example shipped with 5.1.x and asterisk as the
backend.
Calling works fine but PUBLISH / SUBSCRIBE is handled by kamailio itself.
I am not sure but this might be the part where I should relay the request
to asterisk(?):
#!ifdef WITH_PRESENCE
> if (!t_newtran()) {
> sl_reply_error();
> exit;
> }
> if(is_method("PUBLISH")) {
> handle_publish();
> t_release();
> } else if(is_method("SUBSCRIBE")) {
> handle_subscribe();
> t_release();
> }
> exit;
> #!endif
Currently the lights are "broken", some phones show them on, some off.
Kind regards
Kevin
Hello team!
Im using kamailio in sipwise!
I get this errors:
Nov 5 11:51:34 sipwise proxy[1943]: ERROR: <core> [db_query.c:235]:
db_do_insert_cmd(): error while submitting query
Nov 5 11:51:34 sipwise proxy[1943]: ERROR: presence [subscribe.c:2514]:
update_db_subs_timer(): unsuccessful sql insert
Nov 5 11:51:34 sipwise proxy[1943]: ERROR: db_mysql [km_dbase.c:127]:
db_mysql_submit_query(): driver error on query: Duplicate entry
'6c23f96-0001-0003-0030(a)10.7.255.250-f3067022b00c564156251ba2f28f' for key
'active_watchers_idx' (1062)
How can I fix it?
Thank you!
Marcos.
Hi Kamailio expert,
i want to use kamailio to simulate presence server, after receive
subscribe, i need kamailio reply 200 OK, and then send out Notify, but
now, it just forward the subscribe, don't reply, could you help check my
cfg? thanks in advance.
BRs
Hello,
with the creation of branch 5.2 done this morning, the master branch is
from now on open for adding new features, to be part of future release
series v5.3.x.
Any bug fix committed to master that applies to 5.2.x or older stable
branches should be backported as usual with git cherry-pick to
appropriate branches like 5.2 or 5.1.
Expect that v5.2.0 will be released in about 2-3 weeks from now.
Based on the workflow used during the past years, the next future
release v5.3.0 should be out after another 8-10 months of development,
plus 1-2 months of testing, so sometime in the summer or autumn of 2019.
Cheers,
Daniel
--
Daniel-Constantin Mierla -- www.asipto.comwww.twitter.com/miconda -- www.linkedin.com/in/miconda
Kamailio World Conference -- www.kamailioworld.com
Kamailio Advanced Training, Nov 12-14, 2018, in Berlin -- www.asipto.com
Hello,
the branch 5.2 has been created, to be used for releasing v5.2.x series.
To check out this branch, the following commands can be used:
git clone https://github.com/kamailio/kamailio kamailio-5.2
cd kamailio-5.2
git checkout -b 5.2 origin/5.2
Pushing commits in this branch:
git push origin 5.2:5.2
Note that 5.2 is an official stable branch, so only bug fixes, missing
kemi exports (discuss on sr-dev if not sure) or improvements to
documentation or helper tools can be pushed to this branch.
As usual, if there is a bug fixed, commit and push first to master
branch and then cherry pick to 5.2 branch.
In few weeks, the first release from branch 5.2 will be out,
respectively Kamailio v5.2.0.
Cheers,
Daniel
--
Daniel-Constantin Mierla -- www.asipto.comwww.twitter.com/miconda -- www.linkedin.com/in/miconda
Kamailio World Conference -- www.kamailioworld.com
Kamailio Advanced Training, Nov 12-14, 2018, in Berlin -- www.asipto.com
Hi!
I read about the SCTP module for Kamailio and I am not sure if I should
load it (currently I am not).
Does this provide any benefit when Kamailio is used as proxy in front of
Asterisk?
At least from Wikipedia and the kamailio docs, it sounds like I can load it
and it does it's magic.
The multihomed part caught my attention.
Kinds regards
Kevin
Hello, I recently discovered that the Kamailio database stores the user's
password directly. I have found that by changing STORE_PLAINTEXT_PW = 0 in
the configuration file, it stops storing the password in the database, but
if I make this change I can no longer register the users in Kamailio. How
should I register if I do not store the password? Have I missed a step? I
have read that it is related to the HA1 field but it has not been clear how
to do it. I hope your help. Thank you.
--
José Antonio Gutiérrez Delgado
Responsable técnico
Oficina: (+34) 923040031
<http://www.arsoft-company.com/>
*Este mensaje se dirige exclusivamente a su destinatario/s y puede contener
información privilegiada o confidencial. Si no es vd. el destinatario
indicado, queda notificado de que la utilización, divulgación y/o copia sin
autorización está prohibida en virtud de la legislación vigente. Si ha
recibido este mensaje por error, le rogamos que nos lo comunique
inmediatamente por esta misma vía y proceda a su destrucción.*
*Antes de imprimir, piensa si es necesario. Cuidar el medioambiente es
tarea de todos.*
Hi all,
I'm testing with the new dlg_db_load_callid function to replicate
dialogs to another (standby) kamailio instance on failover. This works
fine for calls that are connected. But i'm missing the dialogs in
"ringing" state. Looks like dialogs are written to database by the
dialog module when we receive the 200OK/ACK for the invite transaction.
The result is that the call gets connected on the other kamailio
instance but without a dialog.
Is it possible to store the early_dialogs that are in rining state in
the database?
If that is not the case can i still create a dialog when i only receive
the 200OK/ACK to the INVITE transaction (INVITE was processed by another
instance) since TM is not aware of the INVITE transaction?
I also tried to reject the 200OK to the INVITE in the on reply route,
but running into the same issue that TM does not know the INVITE
transaction.
Thanks,
Jan
