I'm struggling to implement voice/video call to real phone number on website. If I use a SIP account of any VoIP provider as callee, will it be possible to call to phone number which is not registered to any SIP account?
I hope someone help me on this issue.
--
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/2002
Remove unnecessary quotation marks in the examples.
<!-- 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 -->
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/1999
-- Commit Summary --
* Update README
-- File Changes --
M src/modules/usrloc/README (4)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/1999.patchhttps://github.com/kamailio/kamailio/pull/1999.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/1999
Module: kamailio
Branch: master
Commit: d0919a004b3bab58c47d9842fc77c19c5a8fed31
URL: https://github.com/kamailio/kamailio/commit/d0919a004b3bab58c47d9842fc77c19…
Author: Daniel-Constantin Mierla <miconda(a)gmail.com>
Committer: Daniel-Constantin Mierla <miconda(a)gmail.com>
Date: 2019-07-05T13:22:03+02:00
uac: docs - note about frequency limit for rpc reload command
---
Modified: src/modules/uac/doc/uac_admin.xml
---
Diff: https://github.com/kamailio/kamailio/commit/d0919a004b3bab58c47d9842fc77c19…
Patch: https://github.com/kamailio/kamailio/commit/d0919a004b3bab58c47d9842fc77c19…
---
diff --git a/src/modules/uac/doc/uac_admin.xml b/src/modules/uac/doc/uac_admin.xml
index 097609f13f..d9fe2a1de2 100644
--- a/src/modules/uac/doc/uac_admin.xml
+++ b/src/modules/uac/doc/uac_admin.xml
@@ -1193,7 +1193,10 @@ event_route[uac:reply] {
<function moreinfo="none">uac.reg_reload</function>
</title>
<para>
- Reload the records from database for remote registrations.
+ Reload the records from database for remote registrations. There is
+ a limit of how often the reload command can be executed, by default
+ is 150 seconds between reloads -- see the reg_gc_interval parameter
+ for more details.
</para>
<example>
<title><function>uac.reg_reload</function> usage</title>
Hello,
In both rtpproxy and rtpengine modules, they use SOCK_DGRAM type to
connect to their sockets. At some lines below, they use connect
command to connect to RTP proxy,too.
Why they use this command "connect" while their socket type are connectionless?
Another question is at send_rtpp_command function, when both module
want to send command to RTPProxy, why they create another stream
socket (AF_LOCAL)?
fd = socket(AF_LOCAL, SOCK_STREAM, 0);
These question have raised because in LRE module which i have been
developing on it, i need to found out the LRE module can't connect to
LRE_Proxy.
Actually when i want to send a command to LRE_Proxy with "write"
command which it's socket had disconnected before, I didn't get any
error! I have faced with this problem. It's strange why in both
rtpengine and rtpproxy modules it works!
do {
len = writev(fd, v + 1, vcnt - 1);
} while (len == -1 && errno == EINTR);
if (len <= 0) {
close(fd);
LM_ERR("can't send command to a RTP proxy\n");
goto badproxy;
}
Would you please help me.
With Best Regards.
--
--Mojtaba Esfandiari.S
Module: kamailio
Branch: 5.2
Commit: c23ea82a80c3e66a11b3c1f0bb0ea22e0e7985bb
URL: https://github.com/kamailio/kamailio/commit/c23ea82a80c3e66a11b3c1f0bb0ea22…
Author: Henning Westerholt <hw(a)skalatan.de>
Committer: Henning Westerholt <hw(a)skalatan.de>
Date: 2019-07-03T22:10:36+02:00
acc: extend description in docs for log_missed_calls flag
(cherry picked from commit f7f3222ec03b2a1e9260a79e737cc55c7dac169f)
---
Modified: src/modules/acc/doc/acc_admin.xml
---
Diff: https://github.com/kamailio/kamailio/commit/c23ea82a80c3e66a11b3c1f0bb0ea22…
Patch: https://github.com/kamailio/kamailio/commit/c23ea82a80c3e66a11b3c1f0bb0ea22…
---
diff --git a/src/modules/acc/doc/acc_admin.xml b/src/modules/acc/doc/acc_admin.xml
index a0d0710ccb..48e8c6ac31 100644
--- a/src/modules/acc/doc/acc_admin.xml
+++ b/src/modules/acc/doc/acc_admin.xml
@@ -688,6 +688,14 @@ modparam("acc", "log_flag", 2)
<title><varname>log_missed_flag</varname> (integer)</title>
<para>
Request flag which needs to be set to account missed calls via syslog.
+ This can be used to e.g. account failures during the call setup phase
+ from the callee side, for example if you do forking to several
+ destinations.
+ </para>
+ <para>
+ Keep in mind that this flag is reset after processing. Therefore it is
+ necessary to set it again e.g. in a failure_route if you do serial
+ forking and want to log all attempts.
</para>
<para>
Default value is not-set (no flag).