the updated docker image is having problems with clang-3.7. It seems that
now the package process is adding *-fdebug-prefix-map* and that is not
supported in clang-3.7 [0] [1]
clang: error: unknown argument: '-fdebug-prefix-map=/code=.'
So I'm moving to clang-3.8 in the stretch version and to
@linuxmaniac pushed 1 commit.
f2115ca sca: sca_call_info_update() fix param calls
--
You are receiving this because you are subscribed to this thread.
View it on GitHub:
Great, that works!
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/commit/e65e84caa0e89d8955b44c1ecb8628486ae83e76#commitcomment-19096560___
This issue got fixed in a later version on git master.
--
View this message in context:
http://sip-router.1086192.n5.nabble.com/Kamailio-4-4-2-P-CSCF-crashing-on-REGISTER-tp151804p151996.html
Sent from the Development mailing list archive at Nabble.com.
Hi,
Here they are:
- All the logs:
https://gist.github.com/cruzccl/c3c0aeede9304caf17708fd84cdcd754
- Just the failing request:
https://gist.github.com/cruzccl/ebcb593079a88c9cb3e9c9e3c5489162
Regards,
--
You are receiving this because you are subscribed to this thread.
Reply to this email
log and pcap:
[20092016-1300-kamailio-pcap_log.zip](https://github.com/kamailio/kamailio/files/482465/20092016-1300-kamailio-pcap_log.zip)
kamailio -v
version: kamailio 5.0.0-dev6 (x86_64/linux) 1ed9c2-dirty
flags: STATS: Off, USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS, USE_RAW_SOCKS,
DISABLE_NAGLE,
I pushed a patch to print the sip message when the error occurs to see if it is
something wrong with it. Test again with the latest master branch and provide
the log messages along with the pcap file having the sip traffic.
--
You are receiving this because you are subscribed to this thread.
Module: kamailio
Branch: master
Commit: 1ed9c2712fcfaf378875bc7e478b9481013841d4
URL:
https://github.com/kamailio/kamailio/commit/1ed9c2712fcfaf378875bc7e478b9481013841d4
Author: Daniel-Constantin Mierla
Committer: Daniel-Constantin Mierla
Date:
looks like kamailio dont unerstand that he need handle 407 request
At my side i see that kamailio dont stops 407 request and resend it without any
handling
I use asterisk->kamailio-provider scheme
At this scheme kamailio must stops proxy of get 407/401 and then make another
invite with www-auth
Build Update for kamailio/kamailio
-
Build: #2989
Status: Still Failing
Duration: 15 minutes and 27 seconds
Commit: e65e84c (master)
Author: jaybeepee
Message: modules/ims_usrloc_scscf: don't call db function if in NO_DB mode -
prevents crash
View the
Module: kamailio
Branch: master
Commit: e65e84caa0e89d8955b44c1ecb8628486ae83e76
URL:
https://github.com/kamailio/kamailio/commit/e65e84caa0e89d8955b44c1ecb8628486ae83e76
Author: jaybeepee
Committer: jaybeepee
Date: 2016-09-20T12:44:35+02:00
Module: kamailio
Branch: master
Commit: be7125849d87c89ba58998bfd8dd69f34502175b
URL:
https://github.com/kamailio/kamailio/commit/be7125849d87c89ba58998bfd8dd69f34502175b
Author: Victor Seva
Committer: Victor Seva
Date:
Agreed, I used poor terminology - Apologies for that.
I've tried with the master branch but unfortunately I have the same results as
before.
Log from new build:
[kamailio-dialog-20092016.txt](https://github.com/kamailio/kamailio/files/482253/kamailio-dialog-20092016.txt)
Version output:
OK -- apparently we use different meaning/terminology for re-INVITE -- it is
commonly used for an INVITE that is sent after the call is established, but you
used here for the retry of sending the initial INVITE with the credentials.
I pushed a patch, try with master branch and if all ok I will
Module: kamailio
Branch: master
Commit: 9483b5491f82dd18bbdaeee72fd43ec6e1fbfb8c
URL:
https://github.com/kamailio/kamailio/commit/9483b5491f82dd18bbdaeee72fd43ec6e1fbfb8c
Author: Daniel-Constantin Mierla
Committer: Daniel-Constantin Mierla
Date:
OK, so the call flow is an INVITE from TCP side is sent to Kamailio, an INVITE
is relayed to a UDP SIP server. The UDP SIP server replies with a 401. There is
a failure route to handle the 401 and perform uac_auth()
The TCP side does not handle authentication, so the configuration is for
Is this the right call scenario? From logs, the 401 seems to be sent out and
also a CANCEL appears in the logs. I haven't spotted the re-INVITE either.
Maybe you can grab both pcap and log messages at the same time and send them to
me.
--
You are receiving this because you are subscribed to
Module: kamailio
Branch: master
Commit: 77cacf19ffa8fd4c33fa073529bfc9b7b8c58c0c
URL:
https://github.com/kamailio/kamailio/commit/77cacf19ffa8fd4c33fa073529bfc9b7b8c58c0c
Author: Daniel-Constantin Mierla
Committer: Daniel-Constantin Mierla
Date:
Module: kamailio
Branch: 4.4
Commit: ae2b64d90d0e4652e50afb7d06342f6f6b7bcedb
URL:
https://github.com/kamailio/kamailio/commit/ae2b64d90d0e4652e50afb7d06342f6f6b7bcedb
Author: Victor Seva
Committer: Victor Seva
Date:
I think there is some code missing to break out of the reconnect loop on
success.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
Hi,
you can achieve this in Kamailio suspending the request's transaction and
resuming it later when a REGISTER comes from the callee's device.
Have a look at my presentation at Kamailio World 2015:
http://www.kamailio.org/events/2015-KamailioWorld/Day2/20-Federico.Cabiddu-
[Uploading kamailio-dialog-log.txt…]()
That's the full log during the call on debug 3.
Many thanks
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
Merged #784.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/784#event-795274639___
sr-dev mailing list
sr-dev@lists.sip-router.org
Module: kamailio
Branch: master
Commit: d23aeb40dd828b01ec9ff84892d8fb2f31d7c379
URL:
https://github.com/kamailio/kamailio/commit/d23aeb40dd828b01ec9ff84892d8fb2f31d7c379
Author: Victor Seva
Committer: GitHub
Date:
Can you grab all the log messages printed by kamailio with debug=3 when
processing the request within dialog that doesn't get the cseq updated? Send
them to me.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
Can you make all log messages available from the moment the re-INVITE is
received to the end, when error messages are printed? I need to see in which
stage these errors appear.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on
Hi,
When setting "track_cseq_updates" in dialog module, the ReINVITE that should be
initiated with uac_auth() is never sent. Without "track_cseq_updates" set to 0,
the reINVITE does take place.
In the log I can see dialog doing the cseq update:
Sep 20 07:54:57 sbc
Module: kamailio
Branch: master
Commit: a361686b2c872cad6493804eb71b8b8e7e151a4f
URL:
https://github.com/kamailio/kamailio/commit/a361686b2c872cad6493804eb71b8b8e7e151a4f
Author: Phil Lavin
Committer: Phil Lavin
Date: 2016-09-19T21:27:25+01:00
purple: Fix
Module: kamailio
Branch: master
Commit: 0c36c1b62efef176ae6e9322f14096e3a63ed348
URL:
https://github.com/kamailio/kamailio/commit/0c36c1b62efef176ae6e9322f14096e3a63ed348
Author: Phil Lavin
Committer: Phil Lavin
Date: 2016-09-19T21:27:54+01:00
presence: Fix
29 matches
Mail list logo