search for: ptime

We have a customer with a system rejecting calls from Asterisk. It's indicating the ptime is 60, but the system admin is saying they only support 20. They are running asterisk 16.2.1 and using chan_sip Is there a way to specify this with chan_sip? Also, for my own curiosity, is there a way to specify this with PJSIP? (Trying to migrate customers to PJSIP, but we are holding until ast...

.../20/08 17:03:00 2 2030 90 90.0 12/20/08 18:41:00 3 2030 45 43.8 12/21/08 14:36:00 4 2030 0 -23.8 12/21/08 19:30:00 5 2030 90 90.2 12/21/08 21:48:00 6 2030 45 48.6 12/22/08 13:02:00 I wan to convert the format of Date and Time, so I did this: pdate <- as.POSIXct(strptime(FormatedData$Date,"%m/%d/%Y")) ptime <- as.POSIXct(strptime(FormatedData$Time,"%H:%M:%S")) but I get the following format: > head(NewFormatedData) ID Target Actual Date Time pdate ptime 1 2030 0 -57.0 12/20/08 17:03:00 8-12-20 2009-03-...

Hi, Does anyboody have insight into what this error terminating "R CMD check" on an in-house package may imply? > ### > cat("Time elapsed: ", proc.time() - get("ptime", pos = 'CheckExEnv'),"\n") Error in get("ptime", pos = "CheckExEnv") : unused argument(s) (pos = "CheckExEnv") Calls: cat -> cat.default -> <Anonymous> -> get Execution halted It happens in the "* checking examples ... ER...

...6) and R version 2.6.1 Patched (2008-01-19 r44061) on openSUSE 10.2 (X86-64) > gctorture() > proc.time() Error: protect(): protection stack overflow The problem with this is that then R CMD check --use-gct foo ALWAYS FAILS with > cat("Time elapsed: ", proc.time() - get("ptime", pos = 'CheckExEnv'),"\n") Error in proc.time() - get("ptime", pos = "CheckExEnv") : non-numeric argument to binary operator This does not happen in R version 2.4.1 (2006-12-18) I was going to have my computing class try out --use-gct. I guess not unt...

...ason or another, some modes may be left out in implementations (e.g. for RAM or network reasons). What we're saying here is that you should make an effoft to at least support (and offer) the 8 kbps mode to maximise compatibility. > Page 8: > > Optional parameters: > > ptime: see RFC 4566. SHOULD be a multiple of 20 msec. > > maxptime: see RFC 4566. SHOULD be a multiple of 20 msec. > > In real world, many SIP application use either 20 or 30ms. This > ptime parameter is really not reliable for negotiation... On possible > way to handle non mu...

I''ve been testing ZFS since it came out on b27 and this week I BFUed to b30. I''ve seen two problems, one I''ll call minor and the other major. The hardware is a Dell PowerEdge 2600 with 2 3.2GHz Xeons, 2GB memory and a perc3 controller. I have created a filesystem for over 1000 users on it and take hourly snapshots, which destroy the one from 24 hours ago, except the

Hi When returning data from a database column set as a date field I get ''2006-06-06'' I am then have these two lines of code in my controller, taht gain the date I require. pNow = Time.now @pDate = Time.local(pNow.year, pNow.month, 1) At the monment one is set to a date data type while one is set to a Time data type. how can i change these to be the same data type so i can

The problem with the extra ptime descriptions in the SDP has been fixed in Asterisk (see http://lists.digium.com/pipermail/svn-commits/2006-October/017694.html). I've got the latest version of the 1.4 branch from SVN and have verified that the codec negotiation is working again. If you don't want to try the latest SVN ve...

...edia types and names associated with this payload format. The section registers the media types, as per RFC4288 [RFC4288] 4.1.1. Registration of media type audio/speex Media type name: audio Media subtype name: speex Required parameters: None Optional parameters: ptime: see RFC 4566. SHOULD be a multiple of 20 msec. maxptime: see RFC 4566. SHOULD be a multiple of 20 msec. Encoding considerations: This media type is framed and binary, see section 4.8 in [RFC4288]. Security considerations: See Section 6 Interoperability considerati...

...bda, the two approaches give much different power > estimates (96% vs. 55% or so). My problem may be better addressed > as binomial logistic regression, maybe then the simulation and the > asymptotic estimates my agree better. > > sim.pwr<-function(means=c(0.0065,0.0003),ptime=c(1081,3180),nsim=1000) > { # a two group poisson regression power computation # based > simulating lots of Poisson r.v.'s # input rates followed by a vector > of the corresponding person times # the most time consuming part is > the r.v. generation. > # power is determined by...

...d advise in the specification to always support all "modes". I understand this can be seen as a limitation, but in real world, it will not be acceptable to support only a few mode among the provided ones. >> Page 8: >> >> Optional parameters: >> >> ptime: see RFC 4566. SHOULD be a multiple of 20 msec. >> >> maxptime: see RFC 4566. SHOULD be a multiple of 20 msec. >> >> In real world, many SIP application use either 20 or 30ms. This >> ptime parameter is really not reliable for negotiation... On possible >&gt...

...HOULD support 8 kbps bitrate. The sampling rate MUST be 8, 16 or 32 kHz. There is a type above after (narrowband), there is a " extra character. I don't understand what is the motivation to specify "SHOULD support 8 kbps bitrate". Page 8: Optional parameters: ptime: see RFC 4566. SHOULD be a multiple of 20 msec. maxptime: see RFC 4566. SHOULD be a multiple of 20 msec. In real world, many SIP application use either 20 or 30ms. This ptime parameter is really not reliable for negotiation... On possible way to handle non multiple would be to take the r...

I''m moving some data off an old machine to something reasonably new. Normally, the new machine performs better, but I have one case just now where the new system is terribly slow. Old machine - V880 (Solaris 8) with SVM raid-5: # ptime du -kds foo 15043722 foo real 6.955 user 0.964 sys 5.492 And now the new machine - T5140 (latest Solaris 10) with ZFS striped atop a bunch of 2530 arrays: # ptime du -kds foo 15343120 foo real 2:55.210 user 2.559 sys 2:05.788 It''s no...

Hi folks I have a handset talking to Asterisk, which in turn puts the call through to an ITSP. The handsets likes to send audio in 40ms frames (even though Asterisk requests 20ms frames with a ptime header in the SDP). The ITSP doesn't request any particular frame length (with ptime) or state a maximum length (with maxptime), so when Asterisk receives the 40ms media frames from the handset, it simply relays it on to the ITSP. Unfortunately the ITSP doesn't support this, and the result...

Hello there, I have built a kernel module that is responsible for sip and rtp encryption/decryption, padding/depadding, ptime decrease (splitting a large rtp packet to splitting into smaller packets of ptime 20) for incoming packets and ptime increase (merging small rtp packets into a big rtp packet of desired ptime) for outgoing packets. This is meant to be a faster process and indeed it is. The whole purpose is to takin...

...Use Reason : No Encryption : No When the call comes in the SDP contains :- v=0. o=root 973184584 973184584 IN IP4 81.x.x.x s=session. c=IN IP4 81.x.x.x t=0 0. m=audio 11370 RTP/AVP 8 101. a=rtpmap:8 PCMA/8000. a=rtpmap:101 telephone-event/8000. a=fmtp:101 0-16. a=silenceSupp:off - - - -. a=ptime:20. a=sendrecv. and we reply back with :- v=0. o=root 822402971 822402971 IN IP4 88.x.x.x s=Asterisk PBX 11.2-cert2. c=IN IP4 88.x.x.x t=0 0. m=audio 10428 RTP/AVP 8 101. a=rtpmap:8 PCMA/8000. a=rtpmap:101 telephone-event/8000. a=fmtp:101 0-16. a=silenceSupp:off - - - -. a=ptime:20. a=sendrecv....

Is it possible for Asterisk to set the ptime attribute on outbound calls in SDP invite? -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20060405/7e1e68d1/attachment.htm

Hi all, I would like to estimate power and necessary sample size for a GLM with a response variable that has a poisson distribution. Do you have any suggestions for how I can do this in R? Thank you for your help. Sincerely, Craig -- Craig A. Faulhaber Department of Forest, Range, and Wildlife Sciences Utah State University 5230 Old Main Hill Logan, UT 84322 (435)797-3892

...e VoIP GW c=IN IP4 192.168.2.1 t=0 0 m=audio 7070 RTP/AVP 8 0 3 97 18 112 101 a=rtpmap:8 PCMA/8000 a=rtpmap:0 PCMU/8000 a=rtpmap:3 GSM/8000 a=rtpmap:97 iLBC/8000 a=fmtp:97 mode=30 a=rtpmap:18 G729/8000 a=fmtp:18 annexb=no a=rtpmap:112 G726-32/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-16 a=ptime:20 a=sendrecv <--- Transmitting SIP response (733 bytes) to UDP:217.10.79.9:5060 ---> SIP/2.0 100 Trying Via: SIP/2.0/UDP 217.10.79.9;rport=5060;received=217.10.79.9;branch=z9hG4bK56ac.c519528374e3101a61791cf5a0ad1aae.0 Via: SIP/2.0/UDP 172.20.40.6;branch=z9hG4bK56ac.2ecd3532ae51c927dabcc6...

...egisters the media types, as per > RFC4288 [RFC4288] > > 4.1.1. Registration of media type audio/speex > > Media type name: audio > > Media subtype name: speex > > Required parameters: > > None > > Optional parameters: > > ptime: SHOULD be a multiple of 20 msec [RFC4566] > > maxptime: SHOULD be a multiple of 20 msec [RFC4566] > > Encoding considerations: > > This media type is framed and binary, see section 4.8 in > [RFC4288]. > > Security considerations: See Section 6...