Hello,
I need to configure apns push notification in kamailio kindly help. I have a file push.php It is capable to push notification on ios device know i want to implement in kamailio when the user is offline then push notification fire kindly help in this.
Think Out of the Box
--
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/issues/2232
### Setup Description + Problem Description
I am running a open5gs (4G Core network) in an OpenStack VM with internal IP 10.4.128.6 and Floating IP 172.24.15.10 and entire (Kamailio IMS + FoHSS) system in another OpenStack VM with internal IP 10.4.128.21 and Floating IP 172.24.15.30.
eNB (srslte) is running on a physical machine with IP 192.168.49.125.
Kamailio is built from the sources using the forked repo in this [link](https://github.com/herlesupreeth/kamailio/tree/5.3). This forked repo has a fix for handling IMS registration when 4G Core Network is behind a NAT among other fixes.
IMS config files -
[Kamailio_IMS_Config.zip](https://github.com/kamailio/kamailio/files/4255538…
PCSCF, SCSCF, ICSCF are run as separate systemctl process
LTE UEs are configured with two APNs
- "internet" APN for best effort traffic - IP range 192.168.100.0/24
- "ims" APN for IMS - IP range 192.168.101.0/24.
Upon performing the IMS registration, uac module is being used to achieve NATPING by sending OPTIONS message as per the PCSCF script. However, I observe a strange behaviour where the first OPTIONS message sent by the PCSCF is replied with 200 OK and the subsequent message times out with 408 (most of the times even the first OPTIONS message does'nt gets a 200 OK)
!!! IMPORTANT NOTE !!
This behaviour is not seen if I run the 4G Core Network and Kamailio IMS + FoHSS is run in a single VM i.e. CN not behind a NAT
#### Reproduction
Upon performing the IMS registration, uac module is being used to achieve NATPING by sending OPTIONS message as per the PCSCF script. However, I observe a strange behaviour where the first OPTIONS message sent by the PCSCF is replied with 200 OK and the subsequent message times out with 408 (most of the times even the first OPTIONS message does'nt gets a 200 OK)
#### Debugging Data
PCAP at eNB machine and VM running (Kamailio IMS + FoHSS) attached below -
[pcaps.zip](https://github.com/kamailio/kamailio/files/4255628/pcaps.zip)
#### Log Messages
Since the log message from PCSCF, SCSCF and ICSCF is too long I am attaching it as file below.
Following is the log from journalctl for PCSCF, SCSCF and ICSCF combined
[kamailio_log.txt](https://github.com/kamailio/kamailio/files/4255561/kamail…
### Additional Information
* **Kamailio Version** - output of `kamailio -v`
```
version: kamailio 5.3.2 (x86_64/linux) 842fef
flags: USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS, USE_RAW_SOCKS, DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MMAP, PKG_MALLOC, Q_MALLOC, F_MALLOC, TLSF_MALLOC, DBG_SR_MEMORY, USE_FUTEX, FAST_LOCK-ADAPTIVE_WAIT, USE_DNS_CACHE, USE_DNS_FAILOVER, USE_NAPTR, USE_DST_BLACKLIST, HAVE_RESOLV_RES, TLS_PTHREAD_MUTEX_SHARED
ADAPTIVE_WAIT_LOOPS 1024, MAX_RECV_BUFFER_SIZE 262144, MAX_URI_SIZE 1024, BUF_SIZE 65535, DEFAULT PKG_SIZE 8MB
poll method support: poll, epoll_lt, epoll_et, sigio_rt, select.
id: 842fef
compiled on 11:43:39 Feb 26 2020 with gcc 7.4.0
```
* **Operating System**:
```
NAME="Ubuntu"
VERSION="18.04.3 LTS (Bionic Beaver)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 18.04.3 LTS"
VERSION_ID="18.04"
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
VERSION_CODENAME=bionic
UBUNTU_CODENAME=bionic
```
I am not sure where to start looking for debugging this strange behaviour, any hints or pointer would be really helpful. Many thanks in advance.
Regards,
Supreeth
--
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/issues/2231
<!-- Kamailio Pull Request Template -->
<!--
IMPORTANT:
- for detailed contributing guidelines, read:
https://github.com/kamailio/kamailio/blob/master/.github/CONTRIBUTING.md
- pull requests must be done to master branch, unless they are backports
of fixes from master branch to a stable branch
- backports to stable branches must be done with 'git cherry-pick -x ...'
- code is contributed under BSD for core and main components (tm, sl, auth, tls)
- code is contributed GPLv2 or a compatible license for the other components
- GPL code is contributed with OpenSSL licensing exception
-->
#### Pre-Submission Checklist
<!-- Go over all points below, and after creating the PR, tick all the checkboxes that apply -->
<!-- All points should be verified, otherwise, read the CONTRIBUTING guidelines from above-->
<!-- If you're unsure about any of these, don't hesitate to ask on sr-dev mailing list -->
- [ ] Commit message has the format required by CONTRIBUTING guide
- [ ] Commits are split per component (core, individual modules, libs, utils, ...)
- [ ] Each component has a single commit (if not, squash them into one commit)
- [ ] No commits to README files for modules (changes must be done to docbook files
in `doc/` subfolder, the README file is autogenerated)
#### Type Of Change
- [ ] Small bug fix (non-breaking change which fixes an issue)
- [ ] New feature (non-breaking change which adds new functionality)
- [ ] Breaking change (fix or feature that would change existing functionality)
#### Checklist:
<!-- Go over all points below, and after creating the PR, tick the checkboxes that apply -->
- [ ] PR should be backported to stable branches
- [ ] Tested changes locally
- [ ] Related to issue #XXXX (replace XXXX with an open issue number)
#### Description
<!-- Describe your changes in detail -->
These commits create a CDR addressed engine, similar to the one that acc module exports for acc message accounting. Such an engine made an extension module like acc_json possible. This CDR engine is then used in acc_json to write the functionality for logging CDRs in JSON format.
I have added functions to the API exported by acc module instead of creating another separate CDR API, as I thought this is cleaner.
I only implemented the acc_json logging to syslog (no message queue support yet).
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/2107
-- Commit Summary --
* acc: adding CDR engine functionality
* acc_json: adding CDR as JSON functionality
-- File Changes --
M src/modules/acc/acc_api.h (38)
M src/modules/acc/acc_cdr.c (41)
M src/modules/acc/acc_cdr.h (6)
M src/modules/acc/acc_logic.c (10)
M src/modules/acc/acc_logic.h (2)
M src/modules/acc/acc_mod.c (93)
M src/modules/acc_json/acc_json_mod.c (131)
M src/modules/acc_json/acc_json_mod.h (4)
M src/modules/acc_json/doc/acc_json_admin.xml (54)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/2107.patchhttps://github.com/kamailio/kamailio/pull/2107.diff
--
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/2107