## 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 -->
- [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
- [ ] Small bug fix (non-breaking change which fixes an issue)
- [x] 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
- [x] Tested changes locally
- [x] Related to https://lists.kamailio.org/pipermail/sr-dev/2020-April/056481.html
#### Description
Add functions:
__pvx.xavp_get_keys__(_rname_): get an array with the keys used in `$xavp(rname)`
__pvx.xavp_getd__(_rname_): get a dictionary with `$xavp(rname)` content
__pvx.xavp_getd__(_rname_, _idx_): get a dictionary with the `$xavp(rname[idx])` content
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/2285
-- Commit Summary --
* pv: add KEMI functions pvx.xavp_get_keys and pvx.xavp_getd
-- File Changes --
M src/modules/pv/pv.c (281)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/2285.patchhttps://github.com/kamailio/kamailio/pull/2285.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/2285
#### 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 -->
- [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
- [ ] Small bug fix (non-breaking change which fixes an issue)
- [x] 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
- [x] Tested changes locally
- [x] Related to https://lists.kamailio.org/pipermail/sr-dev/2020-April/056481.html
#### Description
Added ARRAY and DICT data types and implement support in app_lua
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/2284
-- Commit Summary --
* core: KEMI suport for ARRAY and DICT
* app_lua: add support for ARRAY and DICT types
-- File Changes --
M src/core/kemi.c (28)
M src/core/kemi.h (17)
M src/modules/app_lua/app_lua_api.c (88)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/2284.patchhttps://github.com/kamailio/kamailio/pull/2284.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/2284
Hello,
I think this thread is for Users maillist.
Anyway, first of all start scscf in debug mode and test. Then have a look
on the logs.
There is only one place in the scscf configuration where you can get
"Domain not served":
if (uri == myself || uri =~ "tel:.*") {
if (!term_impu_registered("location")) {
xlog("L_DBG", "We need to do an UNREG server SAR assignemnt");
assign_server_unreg("UNREG_SAR_REPLY", "location", "term");
exit;
}
} else {
sl_send_reply("403","Forbidden - Domain not served");
exit();
}
I personally got the same error some time ago and I didn't have enough time
to debug it. That's why I just commented all the code above so scscf can
proceed to :
route(term);
This is a temporary workaround but it is working fine for me. Most likely
this is something important but it stays in the todo to debug it in the
near future.
Regards,
Pavel Siderov
На пн, 13.04.2020 г. в 22:38 <sr-dev-request(a)lists.kamailio.org> написа:
>
> Date: Tue, 14 Apr 2020 01:07:14 +0530
> From: Pavithra M <pavimohan3096(a)gmail.com>
> To: "Kamailio (SER) - Development Mailing List"
> <sr-dev(a)lists.kamailio.org>
> Subject: Re: [sr-dev] Unable to make SIP Calls (403 Forbidden - Domain
> Not Served)
> Message-ID:
> <CAJvDr=+
> UKZ66o1ZQ-EmQ5xc70AEnZ3fJzoNair1ctCanB1DyvA(a)mail.gmail.com>
> Content-Type: text/plain; charset="utf-8"
>
> Hi ,
>
> I have configured kamailio as an IMS server as VM based .
>
> PCSCF - 10.x.x.179
> ICSCF - 10.x.x.79
> SCSCF - 10.x.x.73
> HSS - 10.x.x.75
>
> I am using zoiper client for testing the call flow . The *registration is
> happening properly* in my both zoiper clients for hss configured users
> (alice and bob).
> When i am making an *INVITE , *I am getting *403 Forbidden - Domain not
> served *error from SCSCF.
>
> The Call Flow for invite is as follows . call from alice(a)sip.example.com
>
> zoiper1 (UE) -> PCSCF ( INVITE sip:bob@sip.example.com;transport=UDP )
> PCSCF -> SCSCF ( INVITE sip:bob@sip.example.com;transport=UDP )
> SCSCF -> PCSCF (100 trying)
> SCSCF -> ICSCF ( INVITE sip:bob@sip.example.com;transport=UDP )
> ICSCF -> SCSCF (100 trying)
> ICSCF -> SCSCF ( INVITE sip:bob@sip.example.com;transport=UDP )
> SCSCF -> ICSCF (100 trying)
> SCSCF -> ICSCF (*403 Forbidden - Domain not served*)
> ICSCF -> SCSCF (Request: ACK sip:bob@sip.example.com | )
> ICSCF -> SCSCF ( 403 Forbidden - Domain not served )
> SCSCF -> PCSCF ( 403 Forbidden - Domain not served )
> PCSCF -> UE ( 403 Forbidden - Domain not served )
>
> Below are the alias configuration i have done in pcscf,icscf,scscf nodes
> *PCSCF.CFG*
> # IP-Adress for incoming SIP-Traffic, in the following format:
>
> # SIP / UDP
> listen=udp:10.x.x.179:4060
> # SIP / TCP
> listen=tcp:10.x.x.179:4060
> # SIP / TCP/TLS
> listen=tls:10.x.x.179:4060
>
> # IPSEC / UDP
> #!define IPSEC_LISTEN_ADDR "0.0.0.0"
> #!define IPSEC_CLIENT_PORT 5062
> #!define IPSEC_SERVER_PORT 5063
> #alias="sip.example.com:4060"
> alias=pcscf.sip.example.com:4060
>
> #!define MY_WS_PORT 80
> #!define MY_WSS_PORT 443
>
> #!define PCSCF_URL "sip:pcscf.sip.example.com:4060"
>
> #!define TCP_PROCESSES 8
>
> #!subst "/NETWORKNAME/sip.example.com/"
> #!subst "/HOSTNAME/pcscf.sip.example.com/"
>
> *ICSCF.CFG*
>
> # SIP / UDP
> listen=udp:10.x.x.79:4070
> # SIP / TCP
> listen=tcp:10.x.x.79:4070
> # SIP / TCP/TLS
> listen=tls:10.x.x.79:4071
>
> alias="icscf.sip.example.com:4070"
>
> #!define NETWORKNAME "sip.example.com"
> #!define HOSTNAME "icscf.sip.example.com"
>
> *SCSCF.CFG*
>
> # SIP / UDP
> listen=udp:10.x.x.73:4080
> # SIP / TCP
> listen=tcp:10.x.x.73:4080
> # SIP / TCP/TLS
> listen=tls:10.x.x.73:4081
>
> #!define NETWORKNAME "sip.example.com"
> #!define HOSTNAME "scscf.sip.example.com"
> #!define URI "sip:scscf.sip.example.com:4080"
> alias=scscf.sip.example.com:4080
>
> # ENUM-Server to query:
> #!define ENUM_SUFFIX "scscf.sip.example.com."
>
>
> Kindly let me know where i am missing . Kindly need help in this issue
> since the registration is happening successfully and dropping in the INVITE
> level.
> Kindly help.
Module: kamailio
Branch: master
Commit: 3b2a84e94da6e17c61620760fee0288d8af936b9
URL: https://github.com/kamailio/kamailio/commit/3b2a84e94da6e17c61620760fee0288…
Author: Daniel-Constantin Mierla <miconda(a)gmail.com>
Committer: Daniel-Constantin Mierla <miconda(a)gmail.com>
Date: 2020-04-15T09:21:11+02:00
presence_xml: use presence api via structure instead of declaring local function variables
- simpler overall and clearer when function is local in module or imported via
api, given that same prefix was used
---
Modified: src/modules/presence_xml/add_events.c
Modified: src/modules/presence_xml/notify_body.c
Modified: src/modules/presence_xml/pidf.c
Modified: src/modules/presence_xml/pres_check.c
Modified: src/modules/presence_xml/pres_check.h
Modified: src/modules/presence_xml/presence_xml.c
Modified: src/modules/presence_xml/presence_xml.h
Modified: src/modules/presence_xml/xcap_auth.c
Modified: src/modules/presence_xml/xcap_auth.h
---
Diff: https://github.com/kamailio/kamailio/commit/3b2a84e94da6e17c61620760fee0288…
Patch: https://github.com/kamailio/kamailio/commit/3b2a84e94da6e17c61620760fee0288…