Module: kamailio
Branch: master
Commit: 982cc452c3ac80a38b562bc8d06159c8423ec18b
URL: https://github.com/kamailio/kamailio/commit/982cc452c3ac80a38b562bc8d06159c…
Author: Victor Seva <linuxmaniac(a)torreviejawireless.org>
Committer: Victor Seva <linuxmaniac(a)torreviejawireless.org>
Date: 2017-01-12T17:16:50+01:00
app_python: fix compiler warning
> Add "-fno-strict-aliasing" to compilation flags
>
> Fixes a slew of:
> "dereferencing type-punned pointer will break strict-aliasing rules"
> warnings from GCC for lines of the form:
> Py_INCREF(Py_True);
> and
> Py_INCREF(Py_False);
>
> due to the cast from PyIntObject* to PyObject*
>
> GCC is technically correct here; see:
> http://www.python.org/dev/peps/pep-3123/
> though this is unlikely to lead to non-working machine code.
---
Modified: src/modules/app_python/Makefile
---
Diff: https://github.com/kamailio/kamailio/commit/982cc452c3ac80a38b562bc8d06159c…
Patch: https://github.com/kamailio/kamailio/commit/982cc452c3ac80a38b562bc8d06159c…
---
diff --git a/src/modules/app_python/Makefile b/src/modules/app_python/Makefile
index d1854c12e4..02f5fff664 100644
--- a/src/modules/app_python/Makefile
+++ b/src/modules/app_python/Makefile
@@ -22,6 +22,8 @@ ifeq ($(OS), freebsd)
LIBS+=-pthread
endif
+# python2 https://www.python.org/dev/peps/pep-3123/
+DEFS+=-fno-strict-aliasing
DEFS+=-I${PYTHON_INCDIR}
DEFS+=-DKAMAILIO_MOD_INTERFACE
Module: kamailio
Branch: master
Commit: 9425c8d582c0ed0e133dc64f64345d9e3e7e059a
URL: https://github.com/kamailio/kamailio/commit/9425c8d582c0ed0e133dc64f64345d9…
Author: Kamailio Dev <kamailio.dev(a)kamailio.org>
Committer: Kamailio Dev <kamailio.dev(a)kamailio.org>
Date: 2017-09-26T10:16:47+02:00
modules: readme files regenerated - auth ... [skip ci]
---
Modified: src/modules/auth/README
---
Diff: https://github.com/kamailio/kamailio/commit/9425c8d582c0ed0e133dc64f64345d9…
Patch: https://github.com/kamailio/kamailio/commit/9425c8d582c0ed0e133dc64f64345d9…
---
diff --git a/src/modules/auth/README b/src/modules/auth/README
index 51ba685b48..a5f879a0a4 100644
--- a/src/modules/auth/README
+++ b/src/modules/auth/README
@@ -721,8 +721,8 @@ if (has_credentials("myrealm")) {
The function challenges a user agent. It will generate a WWW-Authorize
header field containing a digest challenge, it will put the header
field into a response generated from the request the server is
- processing and send the reply. Upon reception of such a reply the user
- agent should compute credentials and retry the request. For more
+ processing and send the 401 reply. Upon reception of such a reply the
+ user agent should compute credentials and retry the request. For more
information regarding digest authentication see RFC2617. See module
parameter force_stateless_reply regarding sending of the reply.
@@ -758,10 +758,10 @@ if (!www_authenticate("$td", "subscriber")) {
The function challenges a user agent. It will generate a
Proxy-Authorize header field containing a digest challenge, it will put
the header field into a response generated from the request the server
- is processing and send the reply. Upon reception of such a reply the
- user agent should compute credentials and retry the request. For more
- information regarding digest authentication see RFC2617. See module
- parameter force_stateless_reply regarding sending of the reply.
+ is processing and send the 407 reply. Upon reception of such a reply
+ the user agent should compute credentials and retry the request. For
+ more information regarding digest authentication see RFC2617. See
+ module parameter force_stateless_reply regarding sending of the reply.
Meaning of the parameters is the same as for function
www_challenge(realm, flags)
@@ -780,7 +780,9 @@ if (!proxy_authenticate("$fd", "subscriber")) {
The function challenges a user agent for authentication. It combines
the functions www_challenge() and proxy_challenge(), by calling
internally the first one for REGISTER requests and the second one for
- the rest of other request types.
+ the rest of other request types. In other words, it challenges for
+ authentication by sending a 401 reply for REGISTER requests and 407
+ reply for the other types of SIP requests.
Meaning of the parameters the same as for function www_challenge(realm,
flags)
Module: kamailio
Branch: master
Commit: 4e2c3f2b41859767f13bef237b93ea7101f36d12
URL: https://github.com/kamailio/kamailio/commit/4e2c3f2b41859767f13bef237b93ea7…
Author: Daniel-Constantin Mierla <miconda(a)gmail.com>
Committer: Daniel-Constantin Mierla <miconda(a)gmail.com>
Date: 2017-09-26T10:06:36+02:00
auth: explicit listing of status codes for replies in docs of challenge functions
---
Modified: src/modules/auth/doc/auth_functions.xml
---
Diff: https://github.com/kamailio/kamailio/commit/4e2c3f2b41859767f13bef237b93ea7…
Patch: https://github.com/kamailio/kamailio/commit/4e2c3f2b41859767f13bef237b93ea7…
---
diff --git a/src/modules/auth/doc/auth_functions.xml b/src/modules/auth/doc/auth_functions.xml
index 4bce4e5510..0f56d0b0b7 100644
--- a/src/modules/auth/doc/auth_functions.xml
+++ b/src/modules/auth/doc/auth_functions.xml
@@ -63,10 +63,10 @@ if (has_credentials("myrealm")) {
The function challenges a user agent. It will generate a
WWW-Authorize header field containing a digest challenge, it will
put the header field into a response generated from the request the
- server is processing and send the reply. Upon reception of such a
+ server is processing and send the 401 reply. Upon reception of such a
reply the user agent should compute credentials and retry the
request. For more information regarding digest authentication
- see RFC2617. See module parameter force_stateless_reply
+ see RFC2617. See module parameter force_stateless_reply
regarding sending of the reply.
</para>
<para>Meaning of the parameters is as follows:</para>
@@ -136,7 +136,7 @@ if (!www_authenticate("$td", "subscriber")) {
The function challenges a user agent. It will generate a
Proxy-Authorize header field containing a digest challenge, it will
put the header field into a response generated from the request the
- server is processing and send the reply. Upon reception of such a
+ server is processing and send the 407 reply. Upon reception of such a
reply the user agent should compute credentials and retry the request.
For more information regarding digest authentication see RFC2617.
See module parameter force_stateless_reply regarding sending of the reply.
@@ -166,7 +166,9 @@ if (!proxy_authenticate("$fd", "subscriber")) {
The function challenges a user agent for authentication. It combines
the functions www_challenge() and proxy_challenge(), by calling
internally the first one for REGISTER requests and the second one for
- the rest of other request types.
+ the rest of other request types. In other words, it challenges for
+ authentication by sending a 401 reply for REGISTER requests and 407
+ reply for the other types of SIP requests.
</para>
<para>Meaning of the parameters the same as for function
www_challenge(realm, flags)</para>
Hello Everyone,
We are having three server
p-server : 103.211.109.229
i-server : 103.211.109.230
s-server : 103.211.109.231
hss-server : 103.211.109.228 (mysql is installed in this server)
With this configuration, 15 days ago it was working fine and we were able
to make calls.
Recently we installed MySql data base and other application which are not
related to IMS IN s-server for some other application.
When we tried to make call we are unable to make call. i am unable to
isolate the problem.
The registration process seems to be normal.
Below is wire-shark logs taken at p-server for registration:
------------------------------------------------------------
684 10:42:22.053646 10.0.39.143 103.211.109.229 SIP 454
Request: REGISTER sip:koffee-ims.in:5060 <http://apsfl-ims.in:5060> (1
binding) |
685 10:42:22.054160 103.211.109.229 10.0.39.143 SIP 402
Status: 100 Trying |
695 10:42:22.058374 103.211.109.229 103.211.109.230 SIP
671 Request: REGISTER sip:koffee <http://apsfl-ims.in:5060>-ims.in
<http://apsfl-ims.in> (1 binding) |
696 10:42:22.082870 103.211.109.230 103.211.109.229 SIP
484 Status: 100 Trying |
704 10:42:22.350949 103.211.109.230 103.211.109.229 SIP
708 Status: 401 Unauthorized - Challenging the UE |
705 10:42:22.351346 103.211.109.229 10.0.39.143 SIP 620
Status: 401 Unauthorized - Challenging the UE |
706 10:42:22.669278 10.0.39.143 103.211.109.229 SIP 454
Request: REGISTER sip:koffee <http://apsfl-ims.in:5060>-ims.in:5060
<http://apsfl-ims.in:5060> (1 binding) |
708 10:42:22.672436 10.0.39.143 103.211.109.229 SIP 725
Request: REGISTER sip:koffee <http://apsfl-ims.in:5060>-ims.in:5060
<http://apsfl-ims.in:5060> (1 binding) |
709 10:42:22.672647 103.211.109.229 10.0.39.143 SIP 402
Status: 100 Trying |
710 10:42:22.673109 103.211.109.229 103.211.109.230 SIP
942 Request: REGISTER sip:koffee <http://apsfl-ims.in:5060>-ims.in
<http://apsfl-ims.in> (1 binding) |
713 10:42:22.674295 103.211.109.230 103.211.109.229 SIP
484 Status: 100 Trying |
717 10:42:22.900508 103.211.109.230 103.211.109.229 SIP
694 Status: 200 OK (1 binding) |
723 10:42:22.903436 103.211.109.229 10.0.39.143 SIP 606
Status: 200 OK (1 binding) |
I found that s-server behaving differently, the below is logs at s-server.
----------------------------------------------------------------------------
2928 10:47:11.266333 103.211.109.229 103.211.109.231 SIP/SDP
1359 Request: INVITE sip:5858@ <http://sip:5858@apsfl-ims.in:5060>koffee
<http://apsfl-ims.in:5060>-ims.in:5060 <http://sip:5858@apsfl-ims.in:5060>
|
2929 10:47:11.266763 103.211.109.231 103.211.109.229 SIP
460 Status: 100 Trying |
2936 10:47:11.268515 103.211.109.231 103.211.109.229 SIP/SDP
1511 Request: INVITE sip:5858@ <http://sip:5858@apsfl-ims.in:5060>koffee
<http://apsfl-ims.in:5060>-ims.in:5060 <http://sip:5858@apsfl-ims.in:5060>
|
"2937","10:47:11.268771","103.211.109.229","103.211.109.231","SIP","569","Status:
100 Trying | "
2938 10:47:11.268911 103.211.109.229 103.211.109.231 SIP
665 Status: 403 Forbidden - You must register first with a S-CSCF |
2939 10:47:11.269178 103.211.109.231 103.211.109.229 SIP
413 Request: ACK sip:5858@ <http://sip:5858@apsfl-ims.in:5060>koffee
<http://apsfl-ims.in:5060>-ims.in:5060 <http://sip:5858@apsfl-ims.in:5060>
|
2940 10:47:11.269463 103.211.109.231 103.211.109.229 SIP
561 Status: 403 Forbidden - You must register first with a S-CSCF |
2941 10:47:11.269656 103.211.109.229 103.211.109.231 SIP
449 Request: ACK sip:5858@ <http://sip:5858@apsfl-ims.in:5060>koffee
<http://apsfl-ims.in:5060>-ims.in:5060 <http://sip:5858@apsfl-ims.in:5060>
|
My observation is instead of sending the received INVITE packet to
i-server, it is sending to p-server.
Kindly help me to resolve the issue.
If further info is needed, let me know.
Thanking you,
Regards
Hello,
Kamailio will be present at Astricon 2017 having a stand in the expo
area (Orlando, FL, during October 3-5 -- more details at www.astricon.net).
Should you participate at the event and have flyers/other materials with
products/solutions/services that use Kamailio or giveaways, you are
welcome to join the booth or just drop them there, we are more than
happy to promote and spread them. Also, you are very welcome to just
stop by and have a chat.
Besides the activity in the exhibition area, I and Fred Posner will have
presentations about using Kamailio together with Asterisk or other VoIP
applications. Be sure you do not miss them, the agenda is available at:
- http://www.asterisk.org/community/astricon-user-conference/schedule
Expect a consistent group from Kamailio community, it's a great event to
be at!
Looking forward to meeting many of you next week in Orlando!
Cheers,
Daniel
--
Daniel-Constantin Mierla
www.twitter.com/miconda -- www.linkedin.com/in/miconda
Kamailio Advanced Training - www.asipto.com
Kamailio World Conference - www.kamailioworld.com