search for: bitis

Displaying 9 results from an estimated 9 matches for "bitis".

Did you mean: bites
2023 Oct 16
2
creating a time series
Hello everyone, ? had 15 minutes of data from 2017-11-02 13:30:00 to 2022-11-26 23:45:00 and number of data is 177647 ? would like to ask why my time series are less then my expectation. baslangic <- as.POSIXct("2017-11-02 13:30:00", tz = "CET") bitis <- as.POSIXct("2022-11-26 23:45:00", tz = "CET") # zaman_seti <- seq.POSIXt(from = baslangic, to = bitis, by = 60 * 15) length(zaman_seti) [1] 177642 but it has to be 177647 and secondly ? have times in this format ( 2.11.2017 13:30/DD-MM-YYYY HH:MM:SS) su_seviyel...
2007 Dec 28
2
Problems with zaptel and HFC-S PCI card
...the CLI: Dec 27 15:46:42 WARNING[12484]: chan_zap.c:2512 pri_find_dchan: No D-channels available! Using Primary channel 3 as D-channel anyway! == Primary D-Channel on span 1 down Second, the syslog and the kern.log were quickly filling up with messages like these: Dec 27 16:52:53 bitis kernel: zaphfc: sync lost, cpu throtteling enabled. Dec 27 16:52:53 bitis kernel: zaphfc: sync lost, pci performance too low. you might have some cpu throtteling enabled. Dec 27 16:52:53 bitis last message repeated 31 times Dec 27 16:52:53 bitis kernel: zaphfc: bchan rx fifo not enough bytes to rec...
2023 Oct 16
1
creating a time series
Why did you expect to have 177647 elements ? I found that 177642 is the correct number: Marc baslangic <- as.POSIXct("2017-11-02 13:30:00", tz = "CET") bitis <- as.POSIXct("2022-11-26 23:45:00", tz = "CET")? # zaman_seti <- seq.POSIXt(from = baslangic, to = bitis, by = 60 * 15) y2017_11_02 <- seq(from=as.POSIXct("2017-11-02 13:30:00", tz = "CET"), to=as.POSIXct("2017-11-02 23:45:00", tz = &quo...
2023 Oct 16
1
Ynt: creating a time series
...2023 Pazartesi 13:43 Kime: r-help at r-project.org <r-help at r-project.org> Konu: Re: [R] creating a time series Why did you expect to have 177647 elements ? I found that 177642 is the correct number: Marc baslangic <- as.POSIXct("2017-11-02 13:30:00", tz = "CET") bitis <- as.POSIXct("2022-11-26 23:45:00", tz = "CET") # zaman_seti <- seq.POSIXt(from = baslangic, to = bitis, by = 60 * 15) y2017_11_02 <- seq(from=as.POSIXct("2017-11-02 13:30:00", tz = "CET"), to=as.POSIXct("2017-11-02 23:45:00", tz = &quot...
2008 Feb 13
2
MWI problem with Siemens Gigaset S675 IP
...ndle_response: Remote host can't match request NOTIFY to call '1742fb0c598dc6ec444a5ea64a2103ae at 192.168.10.10'. Giving up. The IP address belongs to my server. At the same time, I used tcpdump to see what else might be going on. I found the following: 19:18:22.540113 IP bitis.umrk.to.sip > gigaset.umrk.to.sip: SIP, length: 545 E..=.... at ...... .........)..NOTIFY sip:1000 at 192.168.10.5:5060 SIP/2.0 Via: SIP/2.0 19:18:22.571452 IP gigaset.umrk.to.sip > bitis.umrk.to.sip: SIP, length: 308 E..P.......f....... .....<a_SIP/2.0 481 Call Leg/Trans...
2008 Feb 27
1
SPA3102 registration problem
...Status 4000 (Unspecified) D 0 UNKNOWN After some tests, I found out that the SPA3102 is indeed trying to register, but that Asterisk seems to be ignoring it. Using tcpdump, I can see that registration packets are regularly being sent to the Asterisk server (bitis): 15:30:49.567288 IP spa3102.umrk.to.sip > bitis.umrk.to.sip: SIP, length: 482 Eh........%........ .......xREGISTER sip:192.168.1.10 SIP/2.0 Via: SIP/2.0/UDP 12 15:30:49.568390 IP spa3102.umrk.to.sip-tls > bitis.umrk.to.sip: SIP, length: 492 Eh........%x....... .......%REGISTER sip:192.168...
2007 Dec 29
2
Cirpack KeepAlive packets causing SIP errors
Hi list, After a recent upgrade to Asterisk v1.4.14, my message log is now filling up with the following error messages: <-------------> [Dec 29 17:24:52] WARNING[10655]: chan_sip.c:6645 determine_firstline_parts: Bad request protocol Packet --- (1 headers 0 lines) --- bitis*CLI> <--- SIP read from 82.101.62.99:5060 ---> Cirpack KeepAlive Packet <-------------> Seeing as these packets are being sent by one of my service providers, I can't just turn them off. What's the best solution for this problem? Thanks, Jaap
2014 Aug 11
0
Novi Zakon o radu stupio je na snagu 7.kolovoza 2014
Ako ova poruka nije prikazama u cjelini, mo&#158;ete je pogledati na webu.. Dana 15. srpnja 2014. u Saboru je izglasan Novi Zakon o radu! Novi Zakon o radu stupio je na snagu 7. kolovoza 2014. Novo stru??no izdanje! 30% popusta u prednarud??bi! komentar uz svaki pojedini ??lanak, iz kojega ??e ??itatelji mo??i saznati kako se pojedina odredba zakona u praksi primjenjuje,
2005 Aug 09
4
Too slow computer?
Hello! I''ve put some questions on this list some weeks ago and I''ve got good answers. Thank you! Now I''ve finished my (beautyful) script and I ran it on my router... About my script: It routes packages based on their destination on the Internet. I have about 1650 preffered destination networks listed in some file. The script read this file and marks every package for