Users registered through Postgres DB are offline when try to route calls to them

CPU load 99,9 % with wpcard module (Sangoma) on SVN 4538

Hi all !

I've upgraded Yate from version 3.0 to 3.3 (svn 4538). I use 1 E1  
interface (PRI) on Sangoma card. After upgrade I see CPU load 98-99 %  
permanently. When I turn off module wpcard.yate in yate.conf & restart  
Yate CPU load is return to normal state. But system doesn't work  
without PRI ...

What happens ? I only upgrade Yate and didn't touch Sangoma drivers.  
I've compiled Yate on the same computer where successfully worked the  
previous version 3.0.

Used modules in yate.conf

[modules]
accfile.yate=on
callfork.yate=on
cdrbuild.yate=on
conference.yate=on
dumbchan.yate=on
extmodule.yate=on
faxchan.yate=on
gsmcodec.yate=on
moh.yate=on
mysqldb.yate=on
park.yate=on
pbx.yate=on
queues.yate=on
regexroute.yate=on
register.yate=on
rmanager.yate=on
tonedetect.yate=on
tonegen.yate=on
wavefile.yate=on
wpcard.yate=on
yrtpchan.yate=on
ysipchan.yate=on
ysigchan.yate=on
ystunchan.yate=on
msgsniff.yate=on

I put in attachment Yate start log

Please help.

Konstantin.

Re: Users registered through Postgres DB are offline when try to route calls to them

Hi!

Your users table is too simple, it can only handle authentication.

For registration you need to have at least two extra columns:
- location - a string that holds the target to send the call to
- expires - a timestamp of when the registration will expire

Please look in register.conf.sample for the queries in sections 
[user.register], [user.unregister], [engine.timer] and [call.route]

If you already used the [call.route] query for something else you should 
combine the queries - perhaps using an UNION ... LIMIT 1

Additionally, if the new TCP/TLS or separate UDP listeners are used you will 
also need a "connection" string column that will record on which connection 
the REGISTER was received and the call should be sent on.

Paul

On Thursday 04 August 2011 08:04:07 am a.andreev wrote:
> Hi, Marian! Hi, Paul!
>
>
>
>
> I try to use Postgres DB to register sip-users (Now I use a database to
> record the cdr and call routing. It works fine).
>
> I created a users table, that has two fields: username & pass.
>
> The users from this table have successfully registered.
>
> but they can not call each other:
>
> Yate reports:
>
> <sip/7:MILD> Call rejected error='offline' reason='Offline' [0xb6407b90]
> <sip/7:ALL> YateSIPConnection::hangup() state=0 trans=0xb6405e20
> error='noroute' code=404 reason='Offline' [0xb6407b90]
>
>
>
>
> ===register.conf=====
>
> user.auth=yes
>
> user.register=yes
>
> user.unregister=yes
>
>
>
>
>
>
>
> But when the same users I write to a regfile.conf, they are registered and
> are calling to each other.
>
>
>
> Thanks,
>
> A. Andreev.

Re: CPU load 99,9 % with wpcard module (Sangoma) on SVN 4538

Hi!

What did you encode or compress the log with???

yate.log: AppleSingle encoded Macintosh file

Also please describe the wanrouter version and attach the wpcard.conf file and 
possibly ysigchan.conf. Do you use E1 PRI with ISDN or SS7 signaling?

Did you "make uninstall; make clean" before updating the SVN and rebuilding 
Yate?

Another thing to check is if there are other copies of Yate installed in some 
other directory. Check for duplicate libraries and modules.

Paul

On Thursday 04 August 2011 08:25:33 am Konstantin Reshetnikov wrote:
> Hi all !
>
> I've upgraded Yate from version 3.0 to 3.3 (svn 4538). I use 1 E1
> interface (PRI) on Sangoma card. After upgrade I see CPU load 98-99 %
> permanently. When I turn off module wpcard.yate in yate.conf & restart
> Yate CPU load is return to normal state. But system doesn't work
> without PRI ...
>
> What happens ? I only upgrade Yate and didn't touch Sangoma drivers.
> I've compiled Yate on the same computer where successfully worked the
> previous version 3.0.
>
> Used modules in yate.conf
>
> [modules]
> accfile.yate=on
> callfork.yate=on
> cdrbuild.yate=on
> conference.yate=on
> dumbchan.yate=on
> extmodule.yate=on
> faxchan.yate=on
> gsmcodec.yate=on
> moh.yate=on
> mysqldb.yate=on
> park.yate=on
> pbx.yate=on
> queues.yate=on
> regexroute.yate=on
> register.yate=on
> rmanager.yate=on
> tonedetect.yate=on
> tonegen.yate=on
> wavefile.yate=on
> wpcard.yate=on
> yrtpchan.yate=on
> ysipchan.yate=on
> ysigchan.yate=on
> ystunchan.yate=on
> msgsniff.yate=on
>
> I put in attachment Yate start log
>
> Please help.
>
> Konstantin.

Re: CPU load 99,9 % with wpcard module (Sangoma) on SVN 4538

Hi all !

Latest information about this problem.

I've take another one server (Test Server) with Sangoma card, install  
wanpipe driver version 3.3.14.11. Then install old Yate SVN 3693 (It  
worked on target server about 1 year without any problem). CPU load  
was from 0 to 2 %

Then I installed SVN 4538 with steps:

make uninstall
make clean
./autogen.sh
./configure
make
make install
ldconfig

The situation is absolutelly repeats itself CPU load about 100 % !!!

l put config files and Yate log  in attachment

Can anybody try to install this SVN to the system with Sangoma T1/E1  
card ?

> От: Konstantin Reshetnikov <kosta@...>
> Дата: 4 августа 2011 г. 12:39:05 GMT+04:00
> Кому: Paul Chitescu <paulc@...>
> Тема: Ответ: [yate] CPU load 99,9 % with wpcard module  
> (Sangoma) on SVN 4538
>
> 1. Oops, I use MAC as my work computer, there was small mistake with  
> log attachment. The target system works on Debian Lenny. See text  
> file yate.log in attachment.
> 2. Version wanpipe drivers as recommended on your site 3.3.14.11 -  
> there was no problem with Yate 3.0. I use ISDN PRI.
> 3. I put two configuration files you asked in attachment
> 4. I never done make uninstall; make clean before updating. Is it  
> big mistake ?
> 5. Every time I make update Yate I create new folder and then follow  
> by instructions to install Yate from SNV.
>
> K.
>
> 04.08.2011, × 12:02, Paul Chitescu:
>
>> Hi!
>>
>> What did you encode or compress the log with???
>>
>> yate.log: AppleSingle encoded Macintosh file
>>
>> Also please describe the wanrouter version and attach the  
>> wpcard.conf file and
>> possibly ysigchan.conf. Do you use E1 PRI with ISDN or SS7 signaling?
>>
>> Did you "make uninstall; make clean" before updating the SVN and  
>> rebuilding
>> Yate?
>>
>> Another thing to check is if there are other copies of Yate  
>> installed in some
>> other directory. Check for duplicate libraries and modules.
>>
>> Paul
>>
>>
>> On Thursday 04 August 2011 08:25:33 am Konstantin Reshetnikov wrote:
>>> Hi all !
>>>
>>> I've upgraded Yate from version 3.0 to 3.3 (svn 4538). I use 1 E1
>>> interface (PRI) on Sangoma card. After upgrade I see CPU load  
>>> 98-99 %
>>> permanently. When I turn off module wpcard.yate in yate.conf &  
>>> restart
>>> Yate CPU load is return to normal state. But system doesn't work
>>> without PRI ...
>>>
>>> What happens ? I only upgrade Yate and didn't touch Sangoma drivers.
>>> I've compiled Yate on the same computer where successfully worked  
>>> the
>>> previous version 3.0.
>>>
>>> Used modules in yate.conf
>>>
>>> [modules]
>>> accfile.yate=on
>>> callfork.yate=on
>>> cdrbuild.yate=on
>>> conference.yate=on
>>> dumbchan.yate=on
>>> extmodule.yate=on
>>> faxchan.yate=on
>>> gsmcodec.yate=on
>>> moh.yate=on
>>> mysqldb.yate=on
>>> park.yate=on
>>> pbx.yate=on
>>> queues.yate=on
>>> regexroute.yate=on
>>> register.yate=on
>>> rmanager.yate=on
>>> tonedetect.yate=on
>>> tonegen.yate=on
>>> wavefile.yate=on
>>> wpcard.yate=on
>>> yrtpchan.yate=on
>>> ysipchan.yate=on
>>> ysigchan.yate=on
>>> ystunchan.yate=on
>>> msgsniff.yate=on
>>>
>>> I put in attachment Yate start log
>>>
>>> Please help.
>>>
>>> Konstantin.
>>
>>
>
>

CiscoSM+MGCP - dummy RTP sessions

Hi yate,

What can be the reason of the following situation when I have steady growing number of dummy RTP sessions?

At the moment I have only 9 active calls from SIP to SLT/MGCP

AS5350#show mgcp connection 
Endpoint        Call_ID(C) Conn_ID(I) (P)ort (M)ode (S)tate (CO)dec (E)vent[SIFL] (R)esult[EA]
1. S3/DS1-0/2   C=2894830002000000,9300545,9300546  I=0x518309  P=17286,29822  M=3  S=4,4 CO=1 E=3,0,1,3  R=0,0
2. S3/DS1-0/3   C=2894830003000000,9300553,9300554  I=0x51830D  P=17052,26642  M=3  S=4,4 CO=1 E=3,0,3,3  R=0,0
3. S3/DS1-0/4   C=2894830004000000,9300565,9300566  I=0x518313  P=16586,22398  M=3  S=4,4 CO=1 E=3,0,0,3  R=0,0
4. S3/DS1-0/5   C=2894830005000000,9300557,9300558  I=0x51830F  P=18640,23418  M=3  S=4,4 CO=1 E=0,0,0,0  R=0,0
5. S3/DS1-0/6   C=2894830006000000,9300561,9300562  I=0x518311  P=16418,32146  M=3  S=4,4 CO=1 E=0,0,1,0  R=0,0
6. S3/DS1-0/7   C=2894830007000000,9300567,9300568  I=0x518314  P=18336,20374  M=3  S=4,4 CO=1 E=0,0,1,0  R=0,0
7. S3/DS1-6/29  C=28948300dd000000,9300563,9300564  I=0x518312  P=16938,10676  M=3  S=4,4 CO=1
E=0,0,1,0  R=0,0
8. S3/DS1-6/30  C=28948300de000000,9300537,9300538  I=0x518305  P=18582,2264  M=3  S=4,4 CO=6 E=0,0,0,0  R=0,0
9. S3/DS1-6/31  C=28948300df000000,9300559,9300560  I=0x518310  P=18178,11934  M=3  S=4,4 CO=1
E=0,0,1,0  R=0,0

and and the same time I see 124 RTP sessions which produse about 10Mbit RTP from yate to the cisco.

When I restart yate all is OK but from day to day I see growing number of such dummy RTP sessions.

Is there any way to kill those dummy RTP sssions without restarting the yate? 

I use SVN R4438. Current yate status report enclosed.

Regards,
Andrew Checkov

Uptime: 20 00:21:53 (1729313) user: 29712.020 kernel: 21926.675

%%+status
name=rmanager,type=misc;listeners=1,conn=1
name=engine,type=system,version=3.3.3,nodename=sl-gw1.iconnect.ru;plugins=65,inuse=3,handlers=414,messages=0,supervised=true,runattempt=77,threads=284,workers=10,mutexes=952,locks=0,semaphores=1,waiting=0,acceptcalls=accept;sharedpath=/usr/local/share/yate,configpath=/usr/local/etc/yate,usercfgpath=/root/.yate,modulepath=/usr/local/lib/yate,workpath=/var/log/munin
name=callgen,type=varchans,format=Status|Callto;total=0,ring=0,answered=0,chans=0;
name=cdrbuild,type=cdr,format=Status|Caller|Called|BillId|Duration;cdrs=18,hungup=0;sip/1151794=answered|74991000000|6161#79670584639|1310999134-1151824|986,sig/1151745=answered|9019042157|89670584639|1310999134-1151824|986,sig/1151749=answered|9036816663|9019041350.|1310999134-1151828|767,sip/1151798=answered|79036816663|9019041350.|1310999134-1151828|767,sig/1151753=answered|4991225055|9019041350.|1310999134-1151832|73,sip/1151802=answered|74991225055|9019041350.|1310999134-1151832|72,sig/1151755=incoming|9262223581|59595.|1310999134-1151834|45,sip/1151804=progressing|79262223581|59595.|1310999134-1151834|45,sip/1151805=progressing|79262223581|6160#359880041465|1310999134-1151835|43,sig/1151756=outgoing|9262223581|810359880041465|1310999134-1151835|43,sig/1151757=answered|9015120646|59595.|1310999134-1151836|31,sip/1151806=answered|79015120646|59595.|1310999134-1151836|31,sip/1151807=answered|79015120646|6160#37493294195|1310999134-1151837|28,sig/1151758=answered|9015120646|81037493294195|1310999134-1151837|28,sig/1151759=answered|9035233498|9019041350.|1310999134-1151838|25,sip/1151808=answered|79035233498|9019041350.|1310999134-1151838|25,sig/1151760=answered|9266164833|9019041352.|1310999134-1151839|7,sip/1151809=answered|79266164833|9019041352.|1310999134-1151839|7
name=moh,type=misc;sources=0,chans=0
name=accfile,type=misc;users=5;test_sip=,test_h323=,test_iax=,101=101,102=102
name=regfile,type=misc;create=false,defined=2,users=0;
name=analogdetect,type=misc;count=0
name=wanpipe,type=misc;
name=ciscosm,type=misc;
name=mysqldb,type=database,format=Total|Failed|Errors|AvgExecTime;conns=1,failed=0;default=9410529|0|0|0
name=zaptel,type=misc,format=Type|ZaptelType|Span|SpanPos|Alarms|UsedBy;active=0,count=0
name=sigtransport,type=misc;
name=mgcpca,type=misc;spans=7,chans=0
name=tdmcard,type=misc,format=Type|TdmType|Span|SpanPos|Alarms|UsedBy;active=0,count=0
name=openssl,type=misc;contexts=0
name=mux,type=misc;count=0,format=channels|targetid
name=zlibcompress,type=misc;
name=socks,type=misc;wrappers=0;format=Notify|ConnStatus
name=callfork,type=misc;total=0,forks=0
name=jingle,type=varchans,format=Status|Address|Peer;routed=0,routing=0,total=0,chans=0
name=tone,type=misc;tones=0,chans=0
name=snmpagent,type=misc;
name=cache,format=Count;caches=0
name=queuesnotify,type=misc;calls=0;format=Queue|NotifiedQueued|Hungup
name=dumb,type=misc,format=Status|Address|Peer;routed=0,routing=0,total=0,chans=0
name=iax,type=varchans,format=Status|Address|Peer;routed=0,routing=0,total=0,chans=0
name=analyzer,type=misc,format=Status|Address|Peer;routed=0,routing=0,total=0,chans=0
name=yrtp,type=misc;chans=124,mirrors=0;yrtp/625994346=,yrtp/1726874789=,yrtp/1638062866=,yrtp/2140188845=,yrtp/447941527=,yrtp/898882191=,yrtp/1658530783=,yrtp/653128615=,yrtp/1966480963=,yrtp/410681637=,yrtp/912836801=,yrtp/1729255536=,yrtp/874646130=,yrtp/833593694=,yrtp/187732703=,yrtp/1629950521=,yrtp/1157601276=,yrtp/676719078=,yrtp/1761206832=,yrtp/393206458=,yrtp/1343604345=,yrtp/1777011532=,yrtp/953585156=,yrtp/1242694954=,yrtp/1611664306=,yrtp/414660791=,yrtp/885726975=,yrtp/192113892=,yrtp/687803739=,yrtp/379997887=,yrtp/58885016=,yrtp/1184297390=,yrtp/1443388844=,yrtp/286697916=,yrtp/195912071=,yrtp/2133304361=,yrtp/817823378=,yrtp/1216459098=,yrtp/422857862=,yrtp/1237664490=,yrtp/1684228657=,yrtp/211470397=,yrtp/1479093461=,yrtp/1028434179=,yrtp/1229766595=,yrtp/1417569587=,yrtp/605596860=,yrtp/335472819=,yrtp/1365287675=,yrtp/423787041=,yrtp/908065292=,yrtp/1889223397=,yrtp/626018791=,yrtp/971775558=,yrtp/2144368295=,yrtp/1299689498=,yrtp/2110120221=,yrtp/1896454209=,yrtp/501486267=,yrtp/1241599753=,yrtp/1242896156=,yrtp/108612900=,yrtp/1433304088=,yrtp/105228063=,yrtp/863492062=,yrtp/1330635039=,yrtp/2067394406=,yrtp/1218084571=,yrtp/2014903885=,yrtp/1330259394=,yrtp/244836913=,yrtp/966775755=,yrtp/127223588=,yrtp/975393738=,yrtp/5928306=,yrtp/1862163914=,yrtp/1166962344=,yrtp/219784494=,yrtp/1182723744=,yrtp/188238644=,yrtp/213999488=,yrtp/461689734=,yrtp/1229835149=,yrtp/283462780=,yrtp/564639478=,yrtp/1145447740=,yrtp/116043198=,yrtp/1193114147=,yrtp/749731178=,yrtp/871560228=,yrtp/991680596=,yrtp/1072186240=,yrtp/632969603=,yrtp/720171032=,yrtp/2133008885=,yrtp/372244551=,yrtp/1595908632=,yrtp/1195567977=,yrtp/460426396=,yrtp/1985881661=,yrtp/1366776599=,yrtp/652427775=,yrtp/155412257=,yrtp/1880326660=,yrtp/242162013=,yrtp/152470203=,yrtp/897996771=,yrtp/1428698005=,yrtp/1918855890=,yrtp/1387558446=,yrtp/1595042723=,yrtp/2048261668=,yrtp/1013735771=,yrtp/128640206=sip/1151798,yrtp/673351444=,yrtp/1875327793=sip/1151802,yrtp/885084681=,yrtp/690935675=sip/1151804,yrtp/539941731=,yrtp/2136523432=sip/1151806,yrtp/215622051=,yrtp/468794808=sip/1151808,yrtp/2012158235=,yrtp/1052528610=sip/1151809
name=stun,type=misc;
name=conf,type=misc,format=Status|Address|Peer;routed=0,routing=0,total=0,chans=0,rooms=0
name=pbx,type=misc;
name=enumroute,type=route;queries=0,routed=0,rerouted=0
name=wave,type=misc,format=Status|Address|Peer;play=0,record=0,routed=0,routing=0,total=0,chans=0
name=tonedetect,type=misc;count=0
name=sig,type=fixchans,format=Status|Address|Peer;routed=18405,routing=0,total=1151760,chans=9;sig/1151745=answered|link1/222|sip/1151794,sig/1151749=answered|link1/2|sip/1151798,sig/1151753=answered|link1/3|sip/1151802,sig/1151755=progressing|link1/5|sip/1151804,sig/1151756=progressing|link1/223|sip/1151805,sig/1151757=answered|link1/6|sip/1151806,sig/1151758=answered|link1/221|sip/1151807,sig/1151759=answered|link1/4|sip/1151808,sig/1151760=answered|link1/7|sip/1151809
name=register,type=database;critical=false
name=queues,type=misc;queues=0
name=monitoring,type=misc;
name=mrcp,type=misc;count=0,total=0
name=park,type=misc;
name=analog,type=varchans,format=Status|Address|Peer;routed=0,routing=0,total=0,chans=0
name=users,type=misc;
name=mgcpgw,type=misc,format=Status|Address|Peer;routed=0,routing=0,total=0,chans=0
name=sipfeatures,type=misc;
%%-status

Using dispatch on regexroute.conf

delay before H323

<sip:WARN> Transport(general) Socket send error: Invalid argument (22) [0x9c14648]

Re: <sip:WARN> Transport(general) Socket send error: Invalid argument (22) [0x9c14648]

Hi!

This warning does not exist in any released version of Yate (and 3.2.2 doesn;t 
exist either). What exact version are you trying to run?

Please install Yate from one of the released packages or tarballs, the newest 
being 3.3.2 (12.04.2011)

http://yate.null.ro/pmwiki/index.php?n=Main.Download

Regards,

Paul

On Monday 08 August 2011 09:47:22 pm Paul Mathebula wrote:
> Hi,
>
> I'm new to Yate and followed instructions to install, configure and run ! I
> get the following error whenever i try to call any of my extensions;
>
> <sip:WARN> Transport(general) Socket send error: Invalid argument (22)
> [0x9c14648]
>
> I have installed yate-3.2.2, can anyone kindly expalin what causes this
> error and how it may be resolved.
>
> Modules activated:
>
> ;route sip requests to other gateways
> regexroute.yate=on
> ;register users of this switch
> regfile.yate=on
> ;use this switch as a registrar
> register.yate=on
> ;tonegen.yate=on
> ;allow rtp channeling
> yrtpchan.yate=on
> ;allow sip signaling
> ysipchan.yate=on
> ;accfile.yate=on
> rmanager.yate=on
>
> Regexroute file snippet:
>
> I cannot even call these numbers !
>
> ^99991001$=tone/dial
> ^99991002$=tone/busy
> ^99991003$=tone/ring
> ^99991004$=tone/specdial
> ^99991005$=tone/congestion
> ^99991006$=tone/outoforder
> ^99991007$=tone/milliwatt
> ^99991008$=tone/info
> ${rtp_forward}possible=;rtp_forward=yes
> ${formats}^\([^,]*\)=;formats=\1
>
>
> Thanks in advance.
>
> Paul