yeti-switch / sems-yeti Goto Github PK

View Code? Open in Web Editor NEW

15.0 7.0 14.0 1.51 MB

YETI application for SEMS core

Home Page: https://yeti-switch.org/

CMake 0.65% Shell 0.29% C++ 95.45% Makefile 0.14% C 1.44% Python 1.08% GDB 0.03% Lua 0.91%

sip voip softswitch telecommunications sbc

sems-yeti's People

Contributors

Stargazers

Watchers

Forkers

furmur dmitry-sinina vdedyukhin jiaojian8063868 summitrabz rabbani2611 summit-internet ihabhamad geejay101 cloudunicom roccoder ca4ti oliverv linlin2018

sems-yeti's Issues

active_resource field transformation in clickhouse serialiser

for example we have

active_resources: [{"type":5,"id":390390,"takes":1}, {"type":12,"id":1231, takes":2} ]

We should add such fields to request :

active_resource_5_id: 390390
active_resource_5_used: 1
active_resource_12_id: 1231
active_resource_12_used: 2

OptionsProberManager - Error1

Hi, I was trying to build from source (1.11.10) on deb10 as per the instructon but ran into an error below:

compilation terminated.
make[3]: *** [CMakeFiles/sems_yeti.dir/build.make:157: CMakeFiles/sems_yeti.dir/src/OptionsProberManager.cpp.o] Error 1
make[3]: *** Waiting for unfinished jobs....
make[3]: Leaving directory '/opt/sems-yeti/build'
make[2]: *** [CMakeFiles/Makefile2:76: CMakeFiles/sems_yeti.dir/all] Error 2
make[2]: Leaving directory '/opt/sems-yeti/build'
make[1]: *** [Makefile:133: all] Error 2
make[1]: Leaving directory '/opt/sems-yeti/build'
dh_auto_build: cd build && make -j4 returned exit code 2
make: *** [debian/rules:9: build] Error 2
dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2
debuild: fatal error at line 1182:
dpkg-buildpackage -us -uc -ui -b -j4 failed

Thread #17 unlocked a not-locked lock at 0x2A6DD9B0

==2981== ---Thread-Announcement------------------------------------------
==2981== 
==2981== Thread #17 was created
==2981==    at 0x6E78ABE: clone (clone.S:73)
==2981==    by 0x5562229: create_thread (createthread.c:102)
==2981==    by 0x5563C52: pthread_create@@GLIBC_2.2.5 (pthread_create.c:679)
==2981==    by 0x4C32B07: pthread_create_WRK (hg_intercepts.c:427)
==2981==    by 0x4FC2651: AmThread::start() (AmThread.cpp:118)
==2981==    by 0x4F9E0FB: AmSessionProcessor::addThreads(unsigned int) (AmSessionProcessor.cpp:67)
==2981==    by 0x124CF9: main (sems.cpp:628)
==2981== 
==2981== ----------------------------------------------------------------
==2981== 
==2981== Thread #17 unlocked a not-locked lock at 0x2A6DD9B0
==2981==    at 0x4C30604: mutex_unlock_WRK (hg_intercepts.c:1086)
==2981==    by 0xCA5D2B3: ~AmLock (AmThread.h:72)
==2981==    by 0xCA5D2B3: Cdr::update_internal_reason(DisconnectInitiator, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, int) (Cdr.cpp:400)
==2981==    by 0xC9F576E: SBCCallLeg::onCallStatusChange(CallLeg::StatusChangeCause const&) (SBCCallLeg.cpp:2569)
==2981==    by 0xC99BE45: CallLeg::updateCallStatus(CallLeg::CallStatus, CallLeg::StatusChangeCause const&) (CallLeg.cpp:1117)
==2981==    by 0xC99C3C4: CallLeg::onNoAck(unsigned int) (CallLeg.cpp:989)
==2981==    by 0x4FA04F1: AmSipDialog::uasTimeout(AmSipTimeoutEvent*) (AmSipDialog.cpp:495)
==2981==    by 0x4FA89AB: AmSipTimeoutEvent::operator()(AmBasicSipDialog*) (AmSipEvent.cpp:12)
==2981==    by 0x4F88BC0: AmSession::process(AmEvent*) [clone .part.31] (AmSession.cpp:720)
==2981==    by 0xCA0A62A: SBCCallLeg::process(AmEvent*) (SBCCallLeg.cpp:2074)
==2981==    by 0x4F43E04: AmEventQueue::processEvents() (AmEventQueue.cpp:86)
==2981==    by 0x4F8B96B: AmSession::processEventsCatchExceptions() (AmSession.cpp:376)
==2981==    by 0x4F8AD50: AmSession::processingCycle() (AmSession.cpp:407)
==2981==  Lock at 0x2A6DD9B0 was first observed
==2981==    at 0x4C3400A: pthread_mutex_init (hg_intercepts.c:779)
==2981==    by 0x4FC2264: AmMutex::AmMutex(bool) (AmThread.cpp:48)
==2981==    by 0xCA64873: Cdr::Cdr() (Cdr.cpp:79)
==2981==    by 0xCA6571B: Cdr::Cdr(SqlCallProfile const&) (Cdr.cpp:123)
==2981==    by 0xC99958A: CallCtx::getFirstProfile() (CallCtx.cpp:45)
==2981==    by 0xC9E67A1: SBCFactory::onInvite(AmSipRequest const&, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, std::map<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, std::less<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > >, std::allocator<std::pair<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > > > > const&) (SBC.cpp:254)
==2981==    by 0x4F98F62: AmSessionContainer::createSession(AmSipRequest const&, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >&, AmArg*) (AmSessionContainer.cpp:547)
==2981==    by 0x4F9AADE: AmSessionContainer::startSessionUAS(AmSipRequest&) (AmSessionContainer.cpp:301)
==2981==    by 0x4FA7A46: AmSipDispatcher::handleSipMsg(AmSipRequest&) (AmSipDispatcher.cpp:121)
==2981==    by 0x4FED4EB: _SipCtrlInterface::handle_sip_request(trans_ticket const&, sip_msg*) (SipCtrlInterface.cpp:819)
==2981==    by 0x5032B5E: _trans_layer::process_rcvd_msg(sip_msg*, trsp_acl const&, trsp_acl const&) (trans_layer.cpp:1819)
==2981==    by 0x50333F0: _trans_layer::received_msg(sip_msg*, trsp_acl const&, trsp_acl const&) (trans_layer.cpp:1680)
==2981==  Address 0x2a6dd9b0 is 32 bytes inside a block of size 1,368 alloc'd
==2981==    at 0x4C2D63F: operator new(unsigned long) (vg_replace_malloc.c:334)
==2981==    by 0xC99957C: CallCtx::getFirstProfile() (CallCtx.cpp:45)
==2981==    by 0xC9E67A1: SBCFactory::onInvite(AmSipRequest const&, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, std::map<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, std::less<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > >, std::allocator<std::pair<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > > > > const&) (SBC.cpp:254)
==2981==    by 0x4F98F62: AmSessionContainer::createSession(AmSipRequest const&, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >&, AmArg*) (AmSessionContainer.cpp:547)
==2981==    by 0x4F9AADE: AmSessionContainer::startSessionUAS(AmSipRequest&) (AmSessionContainer.cpp:301)
==2981==    by 0x4FA7A46: AmSipDispatcher::handleSipMsg(AmSipRequest&) (AmSipDispatcher.cpp:121)
==2981==    by 0x4FED4EB: _SipCtrlInterface::handle_sip_request(trans_ticket const&, sip_msg*) (SipCtrlInterface.cpp:819)
==2981==    by 0x5032B5E: _trans_layer::process_rcvd_msg(sip_msg*, trsp_acl const&, trsp_acl const&) (trans_layer.cpp:1819)
==2981==    by 0x50333F0: _trans_layer::received_msg(sip_msg*, trsp_acl const&, trsp_acl const&) (trans_layer.cpp:1680)
==2981==    by 0x503972D: udp_trsp::run() (udp_trsp.cpp:423)
==2981==    by 0x4FC23A6: AmThread::_start(void*) (AmThread.cpp:86)
==2981==    by 0x4C32D06: mythread_wrapper (hg_intercepts.c:389)
==2981==  Block was alloc'd by thread #76
==2981==

Can't write CDR to master database

Logs from SEMS node:

[31839/yeti:cdr/CdrWriter.cpp:579] ERROR: Cant write record to master database

Logs from DB server:

2022-08-16 12:11:30.124 AWST [11270] ltscdr@cdr STATEMENT:  SELECT writecdr($1,$2,$3,$4,$5,$6,$7,$8,$9,$10,$11,$12,$13,$14,$15,$16,$17,$18,$19,$20,$21,$22,$23,$24,$25,$26,$27,$28,$29,$30,$31,$32,$33,$34,$35,$36,$37,$38,$39,$40,$41,$42,$43,$44,$45);
2022-08-16 12:11:30.418 AWST [11272] ltscdr@cdr ERROR:  no partition of relation "streams" found for row
2022-08-16 12:11:30.418 AWST [11272] ltscdr@cdr DETAIL:  Partition key of the failing row contains (time_start) = (2022-08-16 12:02:25.113414+08).
2022-08-16 12:11:30.418 AWST [11272] ltscdr@cdr CONTEXT:  SQL statement "INSERT INTO rtp_statistics.streams VALUES( v_rtp_stream_data.*)"
        PL/pgSQL function writecdr(boolean,integer,integer,integer,boolean,smallint,character varying,integer,character varying,integer,smallint,character varying,integer,character varying,integer,character varying,character varying,json,boolean,integer,character varying,integer,integer,character varying,integer,character varying,character varying,character varying,character varying,character varying,character varying,integer,boolean,json,json,character varying,character varying,json,smallint,bigint,json,json,boolean,json,json) line 258 at SQL statement

Versions:

postgresql-13-yeti/1.11,now 1.3.3p4 amd64 [installed]
sems-modules-yeti/1.11,now 1.11.15core53p1 amd64 [installed]
yeti-web/1.11,now 1.11.20 amd64 [installed]

I've re-run the migrations with the following commands as per docs:

# cd /opt/yeti-web
# su -s /bin/bash yeti-web
$ RAILS_ENV=production ./bin/bundle.sh exec rake db:migrate
$ RAILS_ENV=production ./bin/bundle.sh exec rake db:second_base:migrate

This error is only occuring on successful calls, failed calls log a CDR as normal.

sems-yeti config ERROR: missed 'cdr_completed_dir'' parameter

Hi team,

I tried to post this error in the community forum, but there seems to be an https issue with opening the community forum page.

Here is the error I'm seeing with sems-yeti 1.9

I was testing failover to file config and sems could not start due to some missing parameter in cdr_completed_dir

yeti/system.cfg
..........
failover_requeue = true
failover_to_file = true
serialize_dynamic_fields = true
batch_size = 1
batch_timeout = 5000
..........

systemctl restart yeti-management restart
systemctl restart sems

sems/sems.log
sems[11935]: [11935/11935] [yeti:SqlRouter.cpp:230] INFO: SqlRouter::db_configure: config successfuly readed
sems[11935]: [11935/11935] [yeti:cdr/CdrWriter.cpp:873] ERROR: missed 'cdr_completed_dir'' parameter
sems[11935]: [11935/11935] [yeti:SqlRouter.cpp:244] INFO: Cdr writer pool config loading error
sems[11935]: [11935/11935] [yeti:yeti.cpp:354] ERROR: SqlRouter configure failed
sems[11935]: [11935/11935] [yeti:SBC.cpp:119] ERROR: yeti configuration error

Recommend Projects

React

A declarative, efficient, and flexible JavaScript library for building user interfaces.
Vue.js

🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
Typescript

TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
TensorFlow

An Open Source Machine Learning Framework for Everyone
Django

The Web framework for perfectionists with deadlines.
Laravel

A PHP framework for web artisans
D3

Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

javascript

JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
web

Some thing interesting about web. New door for the world.
server

A server is a program made to process requests and deliver data to clients.
Machine learning

Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Visualization

Some thing interesting about visualization, use data art
Game

Some thing interesting about game, make everyone happy.

Recommend Org

Facebook

We are working to build community through open source technology. NB: members must have two-factor auth.
Microsoft

Open source projects and samples from Microsoft.
Google

Google ❤️ Open Source for everyone.
Alibaba

Alibaba Open Source for everyone
D3

Data-Driven Documents codes.
Tencent

China tencent open source team.