Module: kamailio
Branch: master
Commit: f9c336aa9a78169cf9c7f3fd9bfcfd22218078fb
URL: https://github.com/kamailio/kamailio/commit/f9c336aa9a78169cf9c7f3fd9bfcfd2…
Author: Daniel-Constantin Mierla <miconda(a)gmail.com>
Committer: Daniel-Constantin Mierla <miconda(a)gmail.com>
Date: 2021-02-24T19:09:35+01:00
ims_qos: typos in comments
---
Modified: src/modules/ims_qos/ims_qos_mod.c
Modified: src/modules/ims_qos/rx_aar.c
---
Diff: https://github.com/kamailio/kamailio/commit/f9c336aa9a78169cf9c7f3fd9bfcfd2…
Patch: https://github.com/kamailio/kamailio/commit/f9c336aa9a78169cf9c7f3fd9bfcfd2…
---
diff --git a/src/modules/ims_qos/ims_qos_mod.c b/src/modules/ims_qos/ims_qos_mod.c
index 5fa584bcd7..18d111eb67 100644
--- a/src/modules/ims_qos/ims_qos_mod.c
+++ b/src/modules/ims_qos/ims_qos_mod.c
@@ -597,7 +597,7 @@ void callback_pcscf_contact_cb(struct pcontact *c, int type, void *param)
if (type == PCSCF_CONTACT_EXPIRE || type == PCSCF_CONTACT_DELETE) {
- //we dont need to send STR if no QoS was ever succesfully registered!
+ // we dont need to send STR if no QoS was ever successfully registered!
if (must_send_str && (c->reg_state != PCONTACT_REG_PENDING) && (c->reg_state != PCONTACT_REG_PENDING_AAR)) {
LM_DBG("Received notification of contact (in state [%d] deleted for signalling bearer with with Rx session ID: [%.*s]\n",
c->reg_state, c->rx_session_id.len, c->rx_session_id.s);
diff --git a/src/modules/ims_qos/rx_aar.c b/src/modules/ims_qos/rx_aar.c
index 97d3d7a49d..6a2d60c901 100644
--- a/src/modules/ims_qos/rx_aar.c
+++ b/src/modules/ims_qos/rx_aar.c
@@ -328,7 +328,8 @@ void async_aar_reg_callback(int is_timeout, void *param, AAAMessage *aaa, long e
}
//at this point we have the contact
- /*set the contact state to say we have succesfully done ARR for register and that we dont need to do it again
+ /*set the contact state to say we have successfully done ARR for register
+ * and that we dont need to do it again
* for the duration of the registration.
* */
if (ul.update_rx_regsession(domain_t, &local_data->auth_session_id, pcontact) != 0) {
I've come across a problem with initializing the htable module based on data in MySQL. We persist a cache in MySQL during runtime and reload it on restart using the built in loading capabilities of htable. But occasionally when MySQL contains too many rows the query to MySQL times out. I've tracked it down to be due to the fact that the query wants the data to be sorted based on the column key_name (src/modules/htable/ht_db.c:236 on tag 5.4.4). Looking at the code this seems completely unnecessary and it seems to be working fine without the sorting (tested with mysql-rewriter). Any thoughts on this?
Best regards
Manfred
### Pre-Submission Checklist
- [x ] Commit message has the format required by CONTRIBUTING guide
- [ x] Commits are split per component (core, individual modules, libs, utils, ...)
- [ x] Each component has a single commit (if not, squash them into one commit)
- [ x] 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
- [ x] 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:
- [ x] PR should be backported to stable branches
- [ x] Tested changes locally
- [ ] Related to issue #XXXX (replace XXXX with an open issue number)
#### Description
Fixes minor typo in messages from database config bash scripts.
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/2648
-- Commit Summary --
* Fix typo in 'core tables successfully installed' msg
-- File Changes --
M utils/kamctl/kamdbctl.mysql (8)
M utils/kamctl/kamdbctl.oracle (6)
M utils/kamctl/kamdbctl.pgsql (8)
M utils/kamctl/kamdbctl.sqlite (6)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/2648.patchhttps://github.com/kamailio/kamailio/pull/2648.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/2648
In sip register: Request-URI: sip:ims.mnc001.mcc460.3gppnetwork.org , sip register is ok.
In sip invite: Request-URI: tel:460010120073501;phone-context=ims.mnc001.mcc460.3gppnetwork.org, return 478 Unresolvable destination .
I saw issue #2287 and #1173 . #2287 deals with register, and #1173 has no result.
I want to know how to support such RURI in sip invite, does it need a patch in code ? If so , where and how to modified it .
Thanks a lot.
--
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/2646