similar to: Asterisk RFC 3261 Compliance

Displaying 20 results from an estimated 60000 matches similar to: "Asterisk RFC 3261 Compliance"

2013 Oct 17
0
Asterisk is fully Complaint to RFC 3261 ? issue with Max- forward Range.
Is Asterisk is fully Complaint to RFC 3261 ? I am facing issue with expire Header , Contact header expire parameter, Max forward header range.?For e.g RFC 3261 say Max-Forward Header range should be 0-255 Data from RFC-> 20.22 Max-Forwards The Max-Forwards header field must be used with any SIP method to limit the number of proxies or gateways that can forward the request to the
2013 Jan 24
1
How configure asterisk server extension.conf.
Hi, I have to create scenario like following, I have 2 sip soft phone.I configured Asterisk server on local network, on Linux.With two soft-phone , local asterisk sever, i able to communicate.Now i have communicate with other network SIP client.For that i have opened account at @sip2sip.info, they provided me credentials.Then i registered one SIP phone to local Asterisk sever and another to
2015 Apr 13
0
Regarding Opus Codec Input output file.
Hi Sakharam, I see 2 potential issues with what you are doing. 1. ./opus_demo -e voip 48000 2 16 music_orig.wav testcase30.opus in above command, "16" for bits/sec seems too low. I'm no audio expert, but just cant convince myself you can get any reasonable audio data with 16 bits/sec. FYI, I was able to encode and decode with 16 bits/sec, but when I played the decode file with
2010 May 19
1
Asterisk and RFC 3261
Greetings List,Trying to interconnect with a new provider.. the require a?compliance?with?RFC 3261 ?so knowing less than needed about RFC documentations.. i would like to know if Asterisk is actually in compliance with?RFC 3261 or not..?Can any one help with this? Regards -- Tarek Sawah Integrated Digital Systems CCNA, MCSE, RHCE, VoIP USA: +1 347 562 2308
2015 Apr 13
2
Regarding Opus Codec Input output file.
Hi All, Need Help ! I am interested testing opus codec encoding decoding qaulity. for this have complied opus code codec from souce. After compiling i got opus_demo app. for Encoding i followed below steps: 1) Reference file used music_orig.wav (http://www.opus-codec.org/examples/samples/music_orig.wav) Number of samples : 4358219 (90.8 s) 2015-04-13 10:40:07 UTC Sampling
2008 Feb 26
5
[Bug 1443] New: Missing terminating CR in identification string (RFC non-compliance)
https://bugzilla.mindrot.org/show_bug.cgi?id=1443 Summary: Missing terminating CR in identification string (RFC non-compliance) Classification: Unclassified Product: Portable OpenSSH Version: 4.7p1
2006 May 15
2
RFC 3501 compliance issue: body-type-msg incorrect
Hi, I am using Dovecot 1.0 beta 7, moving to beta8 probably tomorrow. I am seeing a few RFC compliance issues with IMAP responses. I have an in-house IMAP client that caches IMAP data for a web mail system (it parses millions of IMAP interactions a day), and it reports whenever it gets a line that does not look RFC compliant. Unfortunately, users modify their mailboxes before I can get a copy
2003 Nov 03
1
Asterisk compliance with RFC 2617 (qop, nc and cnonce) - in relation to sipcall.co.uk
Hi All, I am attempting to setup Asterisk with sipcall.co.uk. They use Intertex kit to provide the SIP service. Unfortunately Asterisk cannot seem to authenticate against Intertex. Having provided SIP debug info the provider has informed me that Asterisk does not appear to support 'qop', 'nc' and 'cnonce' which are used to stop replay attacks. So, does Asterisk support
2014 Sep 23
0
[PATCH RFC] virtio_pci: fix virtio spec compliance on restore
On Tue, Sep 23, 2014 at 3:32 AM, Michael S. Tsirkin <mst at redhat.com> wrote: > On restore, virtio pci does the following: > + set features > + init vqs etc - device can be used at this point! > + set ACKNOWLEDGE,DRIVER and DRIVER_OK status bits > > This is in violation of the virtio spec, which > requires the following order: > - ACKNOWLEDGE > - DRIVER > -
2006 Feb 15
1
Dovecot RFC non-compliance: Mailbox names
Hi, I think I already know the answer to this and I agree with it, but I have a question about "invalid" mailbox naming decisions in dovecot. Technically, RFC3501 (Section 5.1, pg. 18, client consideration 3) says that * and % are legal in mailbox names, though it implicitly discourages their use. We just migrated to dovecot, and unfortunately have a few users who used * in their
2012 Feb 16
0
How to configure PE 2.0 compliance ?
Hi , I want to use PE 2.0 compliance feature , however i am not seeing any data on puppet-dashboard on compliance tab , it says no baseline set , reviewed NA etc..... I have written audit manifests class foo { file {''/etc/resolv.conf'': audit => all, } file {''/etc/services'': audit => all, } } and
2007 Feb 02
1
asterisk server RFC conformance
Hi Asterisk Gurus, I am new to Asterisk server. We are trying to use Asterisk for testing one of our new products. I was wondering if anyone can tell me if it is RFC compliant or how can i use Asterisk to test it for some basic RFC compliance. Thanks in Advance, -------------- next part -------------- An HTML attachment was scrubbed... URL:
2012 Feb 01
3
Configuration Compliance auditing for many CentOS 5.x boxes
Hi CentOS experts,* Short Version* I would like to produce a weekly report in HTML for each CentOS 5.x server we have indicating configuration compliance with some industry benchmark. I am looking for a tool or tools to implement this, I am happy to use 3rd party proprietary stuff if necessary. * Long(er) Version* Current Situation.. I have a client with many (200x) CentOS 5.x servers
2011 May 24
0
Asterisk 1.8.4.1 Now Available
The Asterisk Development Team has announced the release of Asterisk 1.8.4.1. This release is available for immediate download at http://downloads.asterisk.org/pub/telephony/asterisk/ The release of Asterisk 1.8.4.1 resolves several issues reported by the community. Without your help this release would not have been possible. Thank you! Below is a list of issues resolved in this release: * Fix
2011 May 24
0
Asterisk 1.8.4.1 Now Available
The Asterisk Development Team has announced the release of Asterisk 1.8.4.1. This release is available for immediate download at http://downloads.asterisk.org/pub/telephony/asterisk/ The release of Asterisk 1.8.4.1 resolves several issues reported by the community. Without your help this release would not have been possible. Thank you! Below is a list of issues resolved in this release: * Fix
2005 Jan 14
1
[Fwd: password quality compliance]
-------- Original Message -------- Subject: password quality compliance Date: Fri, 14 Jan 2005 10:45:37 +0100 From: fandino <fandino@ng.fadesa.es> Reply-To: fandino@ng.fadesa.es To: samba@lists.samba.org Hello list, I'd like to have an advice about how to configure samba with password quality compliance. My file server is running samba 3.0.10 with a ldap backend and the users
2006 Oct 16
2
[Patch] Fix a failure in PCI Compliance Test
The Xen platform device (introduced in changeset 11161) would cause HCT''s PCI Compliance Test to generate a failure message. The patch fixes this. Thanks Dexuan Cui Signed-off-by: Dexuan Cui <dexuan.cui@intel.com> _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
2012 Mar 21
1
UPS compliance/certification procedures
Dear Sirs, we currently manufacture/import UPS units in Italy and distribute them all over the country. How can we obtain an official certification to offer our products with full compliance with QNAP, Synology and similar hardware? Looking forward to hearing from you, Best Regards ________________________ Alessandro Gualtieri LAER Accumulatori Srl Via Pio XII, 65/c 20060 - Pozzuolo
2023 Apr 18
1
FIPS compliance efforts in Fedora and RHEL
On 4/18/23 05:05, Norbert Pocs wrote: > Hi OpenSSH mailing list, > > I would like to announce the newly introduced patch in Fedora rawhide [0] > for FIPS compliance efforts. The change will be introduced in an upcoming RHEL 9 > version. Why does Fedora care about FIPS 140? To me, this seems like it should be specific to RHEL and maybe CentOS Stream, not Fedora. My understanding
2023 Apr 19
1
FIPS compliance efforts in Fedora and RHEL
On Tue, 18 Apr 2023, Norbert Pocs wrote: > Hi OpenSSH mailing list, > > I would like to announce the newly introduced patch in Fedora rawhide [0] > for > > FIPS compliance efforts. The change will be introduced in an upcoming RHEL 9 > > version. > > The patch targets OpenSSL support of OpenSSH, specifically the usage of > > old low level API. The new