I have to configure the rtp proxy. The sip is working fine . But also i
need to transmit the rtp packets also through kamailio.
I was using kamailio version
==============
version: kamailio 5.1.4 (x86_64/linux) 9e6f13
flags: STATS: Off, USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS, USE_RAW_SOCKS,
DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MEM, 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
ADAPTIVE_WAIT_LOOPS=1024, MAX_RECV_BUFFER_SIZE 262144, MAX_LISTEN 16,
MAX_URI_SIZE 1024, BUF_SIZE 65535, DEFAULT PKG_SIZE 8MB
poll method support: poll, epoll_lt, epoll_et, sigio_rt, select.
id: 9e6f13
compiled on 12:13:17 Jul 24 2018 with gcc 5.4.0
====================
But using this version, Sip proxy is working but rtp proxy not.
I think you have removed the mi_fifo in this version. I have reported this
before and did not get any response from you.
So i have installed kamailio version
==========================
version: kamailio 4.1.9 (x86_64/linux) ed7bb1
flags: STATS: Off, USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS, USE_RAW_SOCKS,
DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MEM, SHM_MMAP, PKG_MALLOC,
DBG_QM_MALLOC, USE_FUTEX, FAST_LOCK-ADAPTIVE_WAIT, USE_DNS_CACHE,
USE_DNS_FAILOVER, USE_NAPTR, USE_DST_BLACKLIST, HAVE_RESOLV_RES
ADAPTIVE_WAIT_LOOPS=1024, MAX_RECV_BUFFER_SIZE 262144, MAX_LISTEN 16,
MAX_URI_SIZE 1024, BUF_SIZE 65535, DEFAULT PKG_SIZE 4MB
poll method support: poll, epoll_lt, epoll_et, sigio_rt, select.
id: ed7bb1
compiled on 11:24:29 Aug 7 2018 with gcc 5.4.0
===============================
Now i have installed rtp proxy and and it is running in my server.
kamctl fifo nh_show_rtpp
udp:127.0.0.1:7722:: set=0
index:: 0
disabled:: 0
weight:: 1
recheck_ticks:: 0
.
But when i use the rtpproxy it says some error in log file as below.
Aug 8 07:34:51 ip-172-30-0-26 rtpproxy[1521]: DBUG:handle_command:
received command "9834_10 Uc0,8,3,111,9,101
75bf3d1c656eb3c8560952220cc6cabd@52.90.183.183:5060 52.90.183.183 15712
as60627a88;1"
Aug 8 07:34:51 ip-172-30-0-26 rtpproxy[1521]: INFO:handle_command: new
session 75bf3d1c656eb3c8560952220cc6cabd@52.90.183.183:5060, tag
as60627a88;1 requested, type strong
Aug 8 07:34:51 ip-172-30-0-26 rtpproxy[1521]: ERR:create_twinlistener:
can't bind to the IPv4 port 63826: Cannot assign requested address
Aug 8 07:34:51 ip-172-30-0-26 rtpproxy[1521]: ERR:handle_command: can't
create listener
Aug 8 07:34:51 ip-172-30-0-26 rtpproxy[1521]: DBUG:doreply: sending reply
"9834_10 E10#012"
Also the header is not changing for the sip packets.
Please help me. I did not find a complete documentation anywhere. Need your
support as soon as possible.
I here by attaching my kamailio.cfg file for the current version and oldest
one. Please check it and tell me if any changes needed.
Am Donnerstag, 9. August 2018, 14:27:44 CEST schrieb Abdulaziz Alghosh:
> thanks a lot for your response and explanation. strutils.[c,h] and
> strcommon.[c,h] are almost the same. So I modified my included header from
> stcommon[] to strutils as you mentioned.
> Unfortunately, I surfed sequentially Kamailio version upgrades. Even
> though, i did not found such hints about this modification. So I have some
> doubts the called headers and codes from our own module. Hence, I am asking
> for yor advice.
Hello Abdul,
lets move this discussion to the sr-dev list, as its a development related
topic.
> What I am trying to do now is compiliing our module separately under it is
> own directory so I gain the Shared Object file (.so). Somehow our Module is
> requring cds, presence and xcap libraries. But the strange thing is that
> headers from these libraries are #including other headers assuming these
> included header files are under the same library's directory (but in fact
> most of the header files are under ../src/core/). For example :
Do you placed your own module in the src/modules directory as well? If not, I
would suggest to place it there. Its hard to find the issue just with the
logs, there are also many errors here.
My suggestion would be to go from your own module and try to compile a single
file with gcc (for the actual command you can call "make quiet=0" and copy-
paste it). I would try to investigate one error a time, in the end they should
be all mostly related.
There were also some changes in the Makefile logic, maybe you should compare
your Makefile to one of the official modules.
> Making in cds
> CC (gcc) [L libser_cds.so.0.1] cds.o
> In file included from cds.c:2:
> /Abdul/install/clean_test/kamailio-5.1.4/src/lib/cds/../cds/memory.h:125:21:
> warning: mem/mem.h: No such file or directory
> /Abdul/install/clean_test/kamailio-5.1.4/src/lib/cds/../cds/memory.h:126:25:
> warning: mem/shm_mem.h: No such file or directory
> In file included from cds.c:3:
> /Abdul/install/clean_test/kamailio-5.1.4/src/lib/cds/../cds/sync.h:30:22:
> warning: locking.h: No such file or directory
> In file included from cds.c:4:
> /Abdul/install/clean_test/kamailio-5.1.4/src/lib/cds/../cds/logger.h:42:20:
> error: dprint.h: No such file or directory
> make[2]: *** [cds.o] Error 1
> make[1]: [cds] Error 2 (ignored)
>
>
> Those libraries are delivered with version 5.1.4 itself so i do not think
> it is a good idea to modify the paths of the included header files to
> compile my module. because most probably these libraries are needed by
> standard default modules of kamailio.
>
> I hope this is not too much for you to inspect.
> Note: The attached has the log files ( resulting from make all and install
> ) .
>
> Your kind response is highly appreciated
> BR
> Abdulaziz
>
> On Thu, Aug 9, 2018 at 11:31 AM, Abdulaziz Alghosh <aziz647(a)gmail.com>
>
> wrote:
> > Hello Henning,
> >
> > thanks a lot for your response and explanation. strutils.[c,h] and
> > strcommon.[c,h] are almost the same. So I modified my included header from
> > stcommon[] to strutils as you mentioned.
> > Unfortunately, I surfed sequentially Kamailio version upgrades. Even
> > though, i did not found such hints about this modification. So I have some
> > doubts the called headers and codes from our own module. Hence, I am
> > asking
> > for yor advice.
> >
> > What I am trying to do now is compiliing our module separately under it is
> > own directory so I gain the Shared Object file (.so). Somehow our Module
> > is
> > requring cds, presence and xcap libraries. But the strange thing is that
> > headers from these libraries are #including other headers assuming these
> > included header files are under the same library's directory (but in fact
> > most of the header files are under ../src/core/). For example :
> >
> > Making in cds
> > CC (gcc) [L libser_cds.so.0.1] cds.o
> > In file included from cds.c:2:
> > /Abdul/install/clean_test/kamailio-5.1.4/src/lib/cds/../cds/memory.h:125:2
> > 1: warning: mem/mem.h: No such file or directory
> > /Abdul/install/clean_test/kamailio-5.1.4/src/lib/cds/../cds/memory.h:126:2
> > 5: warning: mem/shm_mem.h: No such file or directory
> > In file included from cds.c:3:
> > /Abdul/install/clean_test/kamailio-5.1.4/src/lib/cds/../cds/sync.h:30:22:
> > warning: locking.h: No such file or directory
> > In file included from cds.c:4:
> > /Abdul/install/clean_test/kamailio-5.1.4/src/lib/cds/../cds/logger.h:42:20
> > :
> > error: dprint.h: No such file or directory
> > make[2]: *** [cds.o] Error 1
> > make[1]: [cds] Error 2 (ignored)
> >
> >
> > Those libraries are delivered with version 5.1.4 itself so i do not think
> > it is a good idea to modify the paths of the included header files to
> > compile my module. because most probably these libraries are needed by
> > standard default modules of kamailio.
> >
> > I hope this is not too much for you to inspect.
> > Note: The attached has the log files ( resulting from make all and install
> > ) .
> >
> > Your kind response is highly appreciated
> > Abdulaziz
> >
> >
> > On Thu, Aug 9, 2018 at 8:11 AM, Henning Westerholt <hw(a)kamailio.org>
> >
> > wrote:
> >> Am Mittwoch, 8. August 2018, 17:47:07 CEST schrieb Abdulaziz Alghosh:
> >> > i am somehow newbie with Kamailio and trying to migrate from kamailio
> >> > version 3.0.3 to 5.1.4. Former fellows had developed own modules which
> >> > needed "strcommon.h" and "strcommon.c".
> >> >
> >> > These last two files are not delievered with version 5.1.4. but I
> >> > copied
> >> > them under ../src/core/ thinking it would be beneficial. Unfortunately,
> >> > after make prefix / (and including our own module) all, it seem that
> >> > several dependencies exist. Especially from header files under
> >> > ..src/lib/xcap/ and ../src/lib/presence
> >> >
> >> > Can somebody tell me how "strcommon.h" and "strcommon.c" where
> >>
> >> replaced in
> >>
> >> > version 5.1.4 ?
> >>
> >> Hello Abdul,
> >>
> >> the functions in strcommon.[c,h] were moved into src/core/strutils.[c,h]
> >> in
> >> releases starting from 5.0. I'd suggest to have a look to the file to
> >> verify
> >> if there are no other changes.
Best regards,
--
Henning Westerholt
https://skalatan.de/blog/
#### 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
- [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
Defined correct dependences for perl module
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/1615
-- Commit Summary --
* pkg/kamailio: Defined correct dependences for perl module (#1613)
-- File Changes --
M pkg/kamailio/obs/kamailio.spec (4)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/1615.patchhttps://github.com/kamailio/kamailio/pull/1615.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/1615