Module: kamailio
Branch: master
Commit: 00226fa9cef56e3447068b891b2cb14260ff5423
URL: https://github.com/kamailio/kamailio/commit/00226fa9cef56e3447068b891b2cb14…
Author: Olle E. Johansson <oej(a)edvina.net>
Committer: Olle E. Johansson <oej(a)edvina.net>
Date: 2016-02-13T19:01:46+01:00
ISSUES add link to Github
---
Modified: ISSUES
---
Diff: https://github.com/kamailio/kamailio/commit/00226fa9cef56e3447068b891b2cb14…
Patch: https://github.com/kamailio/kamailio/commit/00226fa9cef56e3447068b891b2cb14…
---
diff --git a/ISSUES b/ISSUES
index f82cfad..e1c1a7c 100644
--- a/ISSUES
+++ b/ISSUES
@@ -1,4 +1,9 @@
-#
+This file is here for old time's sake.
+Current set of issues is to be found at our
+Github Project page:
+https://github.com/kamailio/kamailio/issues
+--------------------------------------------------------------
+
This is a collection of issues which have shown up
since the version 0.8.8 was released. The issues are
# Environment
Kamailio-433 installed behind nat (Amazon EC2 or Google Compute Engine) using config
```cfg
listen=PRIVATE_IP:PORT advertise PUBLIC_IP:PORT
```
# What I wanted to do
In table `location`, the column `socket` will be stored in the form of "PROTO:**PRIVATE_IP**:PORT" while for some reasons I would like it to be stored as "PROTO:**PUBLIC_IP**:PORT"
Through the `registrar` document there is the [xavp_cfg](http://wwwkamailioorg/docs/modules/43x/modules/registrarhtml#registrarpxavp_cfg) parameter that can be used in conjunction with the attribute "socket" to specify the socket string From my understanding this might be the solution to my requirement
# Problem
The column `location``socket` wasn't changed when setting the custom socket string via `xavp_cfg`
After looking into the source code, firstly, a potential bug (correct me if I'm wrong) that it would reset the `sock_flag` to -1 (no flags) even if `reg_xavp_cfg` and `sock_flag` is set A pull request #470 has been opened for this
Secondly, if we pass the above problem, in `savec` it did grab the socket string from xavp_cfg and in function `grep_sock_info()` the socket string was checked with all the address we listen on, including the advertised public address via `socket_info->useinfo` But the returned socket structure still contains the private address info
# Conclusion so far
So, I wasn't sure if using the parameter `xavp_cfg` for setting socket string and stores it in location table make sense or not If yes, can you please giving me some hints about the potential way to extend this?
Cheers,
Ian
---
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/471
A number of additional ports have been opened on Kamailio - the relevant one here is TCP 443. An INVITE comes in from a UA whose from URI is suffixed with :443. PUA generates a PUBLISH out of this. Log is at https://gist.githubusercontent.com/phil-lavin/c381d556c22fd29b4fde/raw/77c5….
The relevant bit to the issue is the last line. PUA is trying to send the PUBLISH to the address and port taken from the from URI... however it sends it over UDP. Because Kamailio is not bound to UDP 443, the PUBLISH is not received.
A hacky "fix" is to make Kamailio bind to UDP 443 as well as TCP 443. I will dig into this deeper on Monday in an attempt to find a better fix.
Suggestions around what is the best solution would be appreciated. I'm thinking that sending this over TCP is not desirable in most instances - unless perhaps Kamailio is only bound to TCP ports?
Cheers