[asterisk-users] dahdi-tools 2.8.0-rc4 - udev rules not installed?
Hi, I just looked at 2.8.0-rc4 and noticed the udev rules/apps change which are now supposed to be part dahdi-tools. After make, make install and make config it seems the dahdi.rules are not installed. I couldn't find a reference to it in the Makefile either. Did I miss something or has the move to dahdi-linux not yet been completed? Regards, Patrick -- _ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- New to Asterisk? Join us for a live introductory webinar every Thurs: http://www.asterisk.org/hello asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
[asterisk-users] DAHDI-Linux and DAHDI-Tools 2.8.0-rc4 Now Available
The Asterisk Development Team has announced the releases of: DAHDI-Linux-v2.8.0-rc4 DAHDI-Tools-v2.8.0-rc4 dahdi-linux-complete-2.8.0-rc4+2.8.0-rc4 This release is available for immediate download at: http://downloads.asterisk.org/pub/telephony/dahdi-linux http://downloads.asterisk.org/pub/telephony/dahdi-tools http://downloads.asterisk.org/pub/telephony/dahdi-linux-complete *** THIS RC FIXES CENTOS 6.5 "PDE_DATA" build issue *** In version 2.8 we have introduced two new drivers: wcte43x - For Digium's new line of 2/4 span T1/E1 cards wcaxx - For Digium's new line of analog fxs/fxo cards We introduced a common library called "wcxb" which ties the previous two drivers, plus the recently introduced wcte13xp driver, together into one common base. dahdi-linux-complete tarballs now include all firmware necessary to build without an internet connection. Shortlog of changes since v2.7.0.1: Oron Peled (16): xpp: Serialize dahdi registration xpp: refactor FXS ring settings xpp: FXS: ring/mwi settings: a sysfs interface xpp: ring/mwi settings: add to FXS init script add a 'location' attribute to sysfs (dahdi_device): dahdi: add "tools_rootdir" module parameter Also send DAHDI_TOOLS_ROOTDIR with device events live_dahdi: load "dahdi" with tools_rootdir=$DESTDIR remove udev rules: moved to dahdi-tools sysfs: create symlink "ddev" to device of span dahdi: Rename span 'master' as 'master_span' .gitignore: *.ko.unsigned Rename "pinned spans" to "assigned spans" xpp: automatic dahdi_registration by default sysfs: new driver attribute: master_span Makefile: new 'make-dist' target Russ Meyerriecks (3): wcte13xp: Migrate to wcxb library wcte13xp: Hold framer in reset to stop xmit on modprobe -r wcte13xp: Improve maintenance functions and error counters Shaun Ruffell (28): dahdi_config: Remove unused NO_DCDC definition. dahdi: Clear DAHDI_ALARM_NOTOPEN when spans are re-initialized. dahdi: Fix placement of '/' in output of /proc/dahdi/x dahdi: Work around missing KBUILD_MODNAME dahdi: Backport try_wait_for_completion() and list_first_entry() wct4xxp: Print warning in dmesg if span priority is not set correctly. wct4xxp: Fix bipolar error insertion test mode. wct4xxp: VPM companding switch print is now debug only. wct4xxp: If linemode changed via sysfs, reset the complete part. wct4xxp, wcte13xp: Move the octasic DSP code into separate module. wcaxx: New driver for A4A/A4B/A8A/A8B analog cards. wcaxx: Update A4B firmware to version 0b0017 wcxb: Update the firmware meta block during flash update. wcte43x: Do not grab reglock in handle_transmit/handle_receive. wcte43x: Remove 'dcxo' debug attribute. oct612x: Make dependent on dahdi.ko dahdi_dynamic: Create a span type for dynamic spans. wcaxx: Use startup/shutdown callbacks to protect access to channel registers. wctdm24xxp: Remove assigned callback. dahdi: Remove "ddev" symlink before unregistering the span device. dahdi: CentOS 6.5 backported PDE_DATA definition. wcxb: is_pcie -> pci_is_pcie() wcxb: Do not access cur_transfer/cur_msg outside of lock. wcaxx: Add extra dummy read when checking for single fxs modules. wcte43x: Update firmware to version e0017. dahdi: Replace drv_attr with drv_groups on kernels > 3.12. Revert "wcaxx: Use startup/shutdown callbacks to protect access to channel registers." dahdi: Fix previous CentOS 6.5 commit. Shaun RuffellL (1): wcaxx: Remove some left over debugging trace statements. Tzafrir Cohen (6): xpp: Firmware for Astribanks 2.02 xpp: Firmware for Astribanks 2.02: Makefile xpp: USB_FW.202.hex: provide as a symlink xpp: mark an AB as failed if it gives bad desc xpp: Fail loading if no module on first slot Ignore some more firmware files Wendell Thompson (2): wcte13xp: Use interrupts for Falc alarms and signaling wcte43x: Add driver for TE435/TE235 digital cards. The diffstat from the v2.7.0.1 release: .gitignore|9 + Makefile | 28 +- README| 17 +- build_tools/genudevrules | 40 - build_tools/live_dahdi|2 +- build_tools/make_dist | 26 + drivers/dahdi/Kbuild | 21 +- drivers/dahdi/dahdi-base.c| 74 +- drivers/dahdi/dahdi-sysfs.c | 150 +- drivers/dahdi/dahdi_dynamic.c |4 + drivers/dahdi/firmware/Makefile | 71 +- drivers/dahdi/oct612x/Kbuild | 32 + drivers/dahdi/oct612x/oct612x-user.c | 200 + drivers/dahdi/oct612x/oct612x.h | 49 + drivers/dahdi/wca
Re: [asterisk-users] DAHDI 2.7.0.1 and CentOS 6.5
Hello, thank you for the information. I'll wait the new release. Regards El 02/12/2013 16:21, Patrick Lists escribió: On 12/02/2013 10:09 PM, Bakko wrote: Hello, during DAHDI 2.7.0.1 compilation on CentOS 6.5 64bit, I have this error: [snip] This was discussed earlier today and Russ pointed to the fixes: http://git.asterisk.org/gitweb/?p=dahdi/linux.git;a=summary http://git.asterisk.org/gitweb/?p=dahdi/linux.git;a=commitdiff;h=5ec9d756aac1a0eb5c1f48eb110e80946b43f41a https://issues.asterisk.org/jira/browse/DAHLIN-330 The fix will be in 2.8.0-rc3. Either wait for the rc3 or add the patch to your build (don't know if it works on 2.7.0.1). Regards, Patrick -- _ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- New to Asterisk? Join us for a live introductory webinar every Thurs: http://www.asterisk.org/hello asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] DAHDI 2.7.0.1 and CentOS 6.5
On 12/02/2013 10:09 PM, Bakko wrote: > Hello, > > during DAHDI 2.7.0.1 compilation on CentOS 6.5 64bit, I have this error: [snip] This was discussed earlier today and Russ pointed to the fixes: http://git.asterisk.org/gitweb/?p=dahdi/linux.git;a=summary http://git.asterisk.org/gitweb/?p=dahdi/linux.git;a=commitdiff;h=5ec9d756aac1a0eb5c1f48eb110e80946b43f41a https://issues.asterisk.org/jira/browse/DAHLIN-330 The fix will be in 2.8.0-rc3. Either wait for the rc3 or add the patch to your build (don't know if it works on 2.7.0.1). Regards, Patrick -- _ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- New to Asterisk? Join us for a live introductory webinar every Thurs: http://www.asterisk.org/hello asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
[asterisk-users] DAHDI 2.7.0.1 and CentOS 6.5
Hello,
during DAHDI 2.7.0.1 compilation on CentOS 6.5 64bit, I have this error:
In file included from
/usr/src/dahdi-linux-2.7.0.1/drivers/dahdi/dahdi-base.c:66:
/usr/src/dahdi-linux-2.7.0.1/include/dahdi/kernel.h:1407: error:
redefinición de 'PDE_DATA'
include/linux/proc_fs.h:328: nota: la definición previa de 'PDE_DATA'
estaba aquí
make[2]: *** [/usr/src/dahdi-linux-2.7.0.1/drivers/dahdi/dahdi-base.o]
Error 1
make[1]: *** [_module_/usr/src/dahdi-linux-2.7.0.1/drivers/dahdi] Error 2
make[1]: se sale del directorio `/usr/src/kernels/2.6.32-431.el6.x86_64'
make: *** [modules] Error 2
I don't know if is the right wayt to solve it but in the:
nano include/dahdi/kernel.h
I commented out these lines:
/*static inline void *PDE_DATA(const struct inode *inode)
{
return PDE(inode)->data;
}
*/
then make and make install work.
I think the problem is there is similar declaration on the linux-kernel
source, file:
/usr/src/kernels/2.6.32-431.el6.x86_64/include/linux/proc_fs.h
Regards
--
_
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
New to Asterisk? Join us for a live introductory webinar every Thurs:
http://www.asterisk.org/hello
asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] Asterisk RTP Questions
Heh, should have guessed it would be you that replied Gareth ;) Sorry yes, this box is on public IP with no NAT as is the upstream providers box (or so they say). So we have had audio cease outbound towards the provider. We have a couple of volunteer customers who are being routed via this new test upstream. It's very difficult (basically impossible!) to replicate the failure it's so infrequent. Looking at PCAPs between us and the upstream we stop sending them audio for example and then a little while later the call drops. Without PCAPs between us and the customer at the same time I can't say why we stopped sending audio (where we receiving any from the customer, did their connection drop for example). We have also had the reverse where we stop receiving audio then a short period later, SIP BYE from us to them! I have read up on rtpkeepalive and rtptimeout. I will put this to one side for now until we have a direct connect to the new test provider there are to many variables in the equation. Thanks for your input though Gareth!. Kind regards, James. -- _ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- New to Asterisk? Join us for a live introductory webinar every Thurs: http://www.asterisk.org/hello asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] Not able to get remote channel variables containing RTCP values
Hello Matt Your best option would be to parse out the values in the various channel variables and store the ones you want. thx, then i am gonna go this route. I got the CDR anyway displayed via Perl already. This usually works pretty well, except for CDRs, which are generally a mess no matter what. :-) In 1.6 the default was really a mess because "" was not consistent used, making parsing a nightmare. -- _ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- New to Asterisk? Join us for a live introductory webinar every Thurs: http://www.asterisk.org/hello asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] Not able to get remote channel variables containing RTCP values
On Mon, Dec 2, 2013 at 10:54 AM, Thomas Rechberger
wrote:
> I am not sure if its just me, but i am able to get only local channel
> variables containing RTCP QOS values.
> The Version is 1.8.14.
> I want to store values of bridged channel in CDR.
>
> Phone is Cisco 7941 SIP and with sip show channelstats i see all the
> relevant information (jitter,packet loss) i want to get. It even calculates
> packet loss in %. But i am not able to store it to CDR.
>
> Asterisk 1.4 seems to have had a function ast_rtp_get_quality but i cant
> find any information about that in sources from 1.8, only a short reference
> in 1.4.
>
> Channel variables like CHANNEL(rtpqos,audio,rxjitter) show only
> information about the local channel. So not really usefull.
> In some old version they seemed to have it changed from remote_jitter to
> rxjitter, local_jitter to txjitter and so on. Was not even documented.
>
The values that can be extracted are documented:
https://wiki.asterisk.org/wiki/display/AST/Function_CHANNEL
I'll admit the description of each parameter isn't terribly verbose, but
there is documentation for what they are. The local/remote refers to the
values reported by Asterisk (local) and the endpoint it is communicating
with (remote). This is only for a single channel; bridged channels are not
accessed by this function.
> The 2 variables RTPAUDIOQOSBRIDGED and RTPAUDIOQOS show exactly the things
> i want, but all information is stored in one field so its not really usable
> because it looks ugly in CDR report and doesnt show packet loss in %.
>
If you wanted, you could parse the values in those channel variables. They
are semi-colon delineated lists with fixed fields, so if there are
particular values you want you can extract them. This does mean doing a bit
of string parsing in the dialplan, but it is a viable option.
>
> The following interesting variables are completely empty (show 0), here is
> how i write it to CDR in h:
> exten => s,n,Set(CDR(txj)=${RTPAUDIOQOSJITTER})
> exten => s,n,Set(CDR(rxj)=${RTPAUDIOQOSJITTERBRIDGED})
> exten => s,n,Set(CDR(txpl)=${RTPAUDIOQOSLOSS})
> exten => s,n,Set(CDR(rxpl)=${RTPAUDIOQOSLOSSBRIDGED})
> exten => s,n,Set(CDR(txrtt)=${RTPAUDIOQOSRTT})
> exten => s,n,Set(CDR(rxrtt)=${RTPAUDIOQOSRTTBRIDGED})
>
> I also checked variables during call with featurecode, but also empty.
>
> Did i oversee something? Is it the same in Version 11 ?
> I dont want to mess with Voipmonitor because i only need 2 variables of
> remote channel. If sip show channelstats is showing everything correctly,
> it should be not that hard to get that information.
Since you want to write this into the inbound channel's CDR, there isn't
much of another option other than to parse out the channel variables, even
in Asterisk 11.
Technically, in 11, you can use a Pre-Dial handler to attach a Hangup
Handler to the outbound channel. The hangup handler is a subroutine that
will be executed on the outbound channel when it is hung up. In the hangup
handler, you can use the CHANNEL function to extract the values directly
from the outbound channel - however, you can't use that to modify the CDR
on the inbound channel, so that's of limited use to how you want to use it.
Your best option would be to parse out the values in the various channel
variables and store the ones you want.
As an aside: as time has gone on, the idea of always reaching across a
bridge to get another channel's values has become less favoured. Such a
concept doesn't do well with ad-hoc multi-party bridges or conferences, and
thus isn't always sustainable in all scenarios. For the most part, the
emphasis in latter versions is to give people access to the specific
channel that they want to manipulate/retrieve information from, as opposed
to relying on the two-party nature of bridges.
This usually works pretty well, except for CDRs, which are generally a mess
no matter what. :-)
Matt
--
Matthew Jordan
Digium, Inc. | Engineering Manager
445 Jan Davis Drive NW - Huntsville, AL 35806 - USA
Check us out at: http://digium.com & http://asterisk.org
--
_
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
New to Asterisk? Join us for a live introductory webinar every Thurs:
http://www.asterisk.org/hello
asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] Basic quetion on Asterisk usage
Am 02.12.2013 15:02, schrieb Raghav Goud: Hi all, I want peer-peer communication between two clients (soft phones) both are behind NAT.I have an accounts with SIP proxy for two clients. To communicate these two clients do i need to use Asterisk ? As per my understanding Asterisk acts like Gateway where conventional phone calls data transfer into internet voice calls. If am wrong please correct me . Thanks, Raghav. Asterisk is not required. In your soft phone you only need to enter SIP Account from ITSP and it is then "converted" by Provider from SIP to plain telephony or routed directly to the other VoIP user which is all transparent for you. 2 users on the same Provider, usually can call 4 free but this depends. When Asterisk is installed, both phones can be registered to it and both phones can communicate over Asterisk directly without even needing an ITSP, it goes all over IP. This requires good configuration to prevent "hackers" from misusing the system and generating high bills. -- _ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- New to Asterisk? Join us for a live introductory webinar every Thurs: http://www.asterisk.org/hello asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
[asterisk-users] Not able to get remote channel variables containing RTCP values
I am not sure if its just me, but i am able to get only local channel
variables containing RTCP QOS values.
The Version is 1.8.14.
I want to store values of bridged channel in CDR.
Phone is Cisco 7941 SIP and with sip show channelstats i see all the
relevant information (jitter,packet loss) i want to get. It even
calculates packet loss in %. But i am not able to store it to CDR.
Asterisk 1.4 seems to have had a function ast_rtp_get_quality but i cant
find any information about that in sources from 1.8, only a short
reference in 1.4.
Channel variables like CHANNEL(rtpqos,audio,rxjitter) show only
information about the local channel. So not really usefull.
In some old version they seemed to have it changed from remote_jitter to
rxjitter, local_jitter to txjitter and so on. Was not even documented.
The 2 variables RTPAUDIOQOSBRIDGED and RTPAUDIOQOS show exactly the
things i want, but all information is stored in one field so its not
really usable because it looks ugly in CDR report and doesnt show packet
loss in %.
The following interesting variables are completely empty (show 0), here
is how i write it to CDR in h:
exten => s,n,Set(CDR(txj)=${RTPAUDIOQOSJITTER})
exten => s,n,Set(CDR(rxj)=${RTPAUDIOQOSJITTERBRIDGED})
exten => s,n,Set(CDR(txpl)=${RTPAUDIOQOSLOSS})
exten => s,n,Set(CDR(rxpl)=${RTPAUDIOQOSLOSSBRIDGED})
exten => s,n,Set(CDR(txrtt)=${RTPAUDIOQOSRTT})
exten => s,n,Set(CDR(rxrtt)=${RTPAUDIOQOSRTTBRIDGED})
I also checked variables during call with featurecode, but also empty.
Did i oversee something? Is it the same in Version 11 ?
I dont want to mess with Voipmonitor because i only need 2 variables of
remote channel. If sip show channelstats is showing everything
correctly, it should be not that hard to get that information.
--
_
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
New to Asterisk? Join us for a live introductory webinar every Thurs:
http://www.asterisk.org/hello
asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] Problems compiling dahdi modules
There is a 100% chance that this will be rolled into v2.8.0-rc3 :-) On Mon, Dec 2, 2013 at 9:26 AM, Patrick Lists < asterisk-l...@puzzled.xs4all.nl> wrote: > On 12/02/2013 04:19 PM, Russ Meyerriecks wrote: > > This is fixed on the dahdi-linux master branch and will be included in > > the next release: > > > > More info: > > http://git.asterisk.org/gitweb/?p=dahdi/linux.git;a=summary > > > http://git.asterisk.org/gitweb/?p=dahdi/linux.git;a=commitdiff;h=5ec9d756aac1a0eb5c1f48eb110e80946b43f41a > > https://issues.asterisk.org/jira/browse/DAHLIN-330 > > Thanks Russ. Any chance there will be a v2.8.0-rc3 release with these > fixes? > > Regards, > Patrick > > -- > _ > -- Bandwidth and Colocation Provided by http://www.api-digital.com -- > New to Asterisk? Join us for a live introductory webinar every Thurs: >http://www.asterisk.org/hello > > asterisk-users mailing list > To UNSUBSCRIBE or update options visit: >http://lists.digium.com/mailman/listinfo/asterisk-users > -- Russ Meyerriecks Digium, Inc. | Linux Kernel Developer 445 Jan Davis Drive NW - Huntsville, AL 35806 - USA direct: +1 256-428-6025 Check us out at: www.digium.com & www.asterisk.org -- _ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- New to Asterisk? Join us for a live introductory webinar every Thurs: http://www.asterisk.org/hello asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] Problems compiling dahdi modules
On 12/02/2013 04:19 PM, Russ Meyerriecks wrote: > This is fixed on the dahdi-linux master branch and will be included in > the next release: > > More info: > http://git.asterisk.org/gitweb/?p=dahdi/linux.git;a=summary > http://git.asterisk.org/gitweb/?p=dahdi/linux.git;a=commitdiff;h=5ec9d756aac1a0eb5c1f48eb110e80946b43f41a > https://issues.asterisk.org/jira/browse/DAHLIN-330 Thanks Russ. Any chance there will be a v2.8.0-rc3 release with these fixes? Regards, Patrick -- _ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- New to Asterisk? Join us for a live introductory webinar every Thurs: http://www.asterisk.org/hello asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] Problems compiling dahdi modules
This is fixed on the dahdi-linux master branch and will be included in the next release: More info: http://git.asterisk.org/gitweb/?p=dahdi/linux.git;a=summary http://git.asterisk.org/gitweb/?p=dahdi/linux.git;a=commitdiff;h=5ec9d756aac1a0eb5c1f48eb110e80946b43f41a https://issues.asterisk.org/jira/browse/DAHLIN-330 On Mon, Dec 2, 2013 at 8:37 AM, Matias Kreder wrote: > Hi, > > I am having the following issue after upgrading the kernel in a CentOS > machine. > > [root@localhost dahdi-linux-complete-2.7.0.1+2.7.0.1]# make > make -C linux all > make[1]: Entering directory > `/usr/src/dahdi-linux-complete-2.7.0.1+2.7.0.1/linux' > make -C drivers/dahdi/firmware firmware-loaders > make[2]: Entering directory > `/usr/src/dahdi-linux-complete-2.7.0.1+ > 2.7.0.1/linux/drivers/dahdi/firmware' > make[2]: Leaving directory > `/usr/src/dahdi-linux-complete-2.7.0.1+ > 2.7.0.1/linux/drivers/dahdi/firmware' > make -C /lib/modules/2.6.32-431.el6.x86_64/build > M='/usr/src/dahdi-linux-complete-2.7.0.1+ > 2.7.0.1/linux/drivers/dahdi/oct612x' > make[2]: Entering directory `/usr/src/kernels/2.6.32-431.el6.x86_64' > Building modules, stage 2. > MODPOST 0 modules > make[2]: Leaving directory `/usr/src/kernels/2.6.32-431.el6.x86_64' > make -C /lib/modules/2.6.32-431.el6.x86_64/build > SUBDIRS=/usr/src/dahdi-linux-complete-2.7.0.1+2.7.0.1/linux/drivers/dahdi > DAHDI_INCLUDE=/usr/src/dahdi-linux-complete-2.7.0.1+2.7.0.1/linux/include > DAHDI_MODULES_EXTRA=" " HOTPLUG_FIRMWARE=yes modules DAHDI_BUILD_ALL=m > make[2]: Entering directory `/usr/src/kernels/2.6.32-431.el6.x86_64' > CC [M] /usr/src/dahdi-linux-complete-2.7.0.1+ > 2.7.0.1/linux/drivers/dahdi/dahdi-base.o > In file included from > /usr/src/dahdi-linux-complete-2.7.0.1+ > 2.7.0.1/linux/drivers/dahdi/dahdi-base.c:66: > /usr/src/dahdi-linux-complete-2.7.0.1+ > 2.7.0.1/linux/include/dahdi/kernel.h:1407: > error: redefinition of ‘PDE_DATA’ > include/linux/proc_fs.h:328: note: previous definition of ‘PDE_DATA’ was > here > make[3]: *** [/usr/src/dahdi-linux-complete-2.7.0.1+ > 2.7.0.1/linux/drivers/dahdi/dahdi-base.o] > Error 1 > make[2]: *** [_module_/usr/src/dahdi-linux-complete-2.7.0.1+ > 2.7.0.1/linux/drivers/dahdi] > Error 2 > make[2]: Leaving directory `/usr/src/kernels/2.6.32-431.el6.x86_64' > make[1]: *** [modules] Error 2 > make[1]: Leaving directory `/usr/src/dahdi-linux-complete-2.7.0.1+ > 2.7.0.1/linux' > make: *** [all] Error 2 > > I have the correct kernel-devel and kernel-headers version installed > > # uname -a > Linux localhost.localdomain 2.6.32-431.el6.x86_64 #1 SMP Fri Nov 22 > 03:15:09 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux > # rpm -q kernel-devel > kernel-devel-2.6.32-431.el6.x86_64 > # rpm -q kernel-headers > kernel-headers-2.6.32-431.el6.x86_64 > > Regards > Matias > > -- > _ > -- Bandwidth and Colocation Provided by http://www.api-digital.com -- > New to Asterisk? Join us for a live introductory webinar every Thurs: >http://www.asterisk.org/hello > > asterisk-users mailing list > To UNSUBSCRIBE or update options visit: >http://lists.digium.com/mailman/listinfo/asterisk-users > -- Russ Meyerriecks Digium, Inc. | Linux Kernel Developer 445 Jan Davis Drive NW - Huntsville, AL 35806 - USA direct: +1 256-428-6025 Check us out at: www.digium.com & www.asterisk.org -- _ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- New to Asterisk? Join us for a live introductory webinar every Thurs: http://www.asterisk.org/hello asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
[asterisk-users] Problems compiling dahdi modules
Hi, I am having the following issue after upgrading the kernel in a CentOS machine. [root@localhost dahdi-linux-complete-2.7.0.1+2.7.0.1]# make make -C linux all make[1]: Entering directory `/usr/src/dahdi-linux-complete-2.7.0.1+2.7.0.1/linux' make -C drivers/dahdi/firmware firmware-loaders make[2]: Entering directory `/usr/src/dahdi-linux-complete-2.7.0.1+2.7.0.1/linux/drivers/dahdi/firmware' make[2]: Leaving directory `/usr/src/dahdi-linux-complete-2.7.0.1+2.7.0.1/linux/drivers/dahdi/firmware' make -C /lib/modules/2.6.32-431.el6.x86_64/build M='/usr/src/dahdi-linux-complete-2.7.0.1+2.7.0.1/linux/drivers/dahdi/oct612x' make[2]: Entering directory `/usr/src/kernels/2.6.32-431.el6.x86_64' Building modules, stage 2. MODPOST 0 modules make[2]: Leaving directory `/usr/src/kernels/2.6.32-431.el6.x86_64' make -C /lib/modules/2.6.32-431.el6.x86_64/build SUBDIRS=/usr/src/dahdi-linux-complete-2.7.0.1+2.7.0.1/linux/drivers/dahdi DAHDI_INCLUDE=/usr/src/dahdi-linux-complete-2.7.0.1+2.7.0.1/linux/include DAHDI_MODULES_EXTRA=" " HOTPLUG_FIRMWARE=yes modules DAHDI_BUILD_ALL=m make[2]: Entering directory `/usr/src/kernels/2.6.32-431.el6.x86_64' CC [M] /usr/src/dahdi-linux-complete-2.7.0.1+2.7.0.1/linux/drivers/dahdi/dahdi-base.o In file included from /usr/src/dahdi-linux-complete-2.7.0.1+2.7.0.1/linux/drivers/dahdi/dahdi-base.c:66: /usr/src/dahdi-linux-complete-2.7.0.1+2.7.0.1/linux/include/dahdi/kernel.h:1407: error: redefinition of ‘PDE_DATA’ include/linux/proc_fs.h:328: note: previous definition of ‘PDE_DATA’ was here make[3]: *** [/usr/src/dahdi-linux-complete-2.7.0.1+2.7.0.1/linux/drivers/dahdi/dahdi-base.o] Error 1 make[2]: *** [_module_/usr/src/dahdi-linux-complete-2.7.0.1+2.7.0.1/linux/drivers/dahdi] Error 2 make[2]: Leaving directory `/usr/src/kernels/2.6.32-431.el6.x86_64' make[1]: *** [modules] Error 2 make[1]: Leaving directory `/usr/src/dahdi-linux-complete-2.7.0.1+2.7.0.1/linux' make: *** [all] Error 2 I have the correct kernel-devel and kernel-headers version installed # uname -a Linux localhost.localdomain 2.6.32-431.el6.x86_64 #1 SMP Fri Nov 22 03:15:09 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux # rpm -q kernel-devel kernel-devel-2.6.32-431.el6.x86_64 # rpm -q kernel-headers kernel-headers-2.6.32-431.el6.x86_64 Regards Matias -- _ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- New to Asterisk? Join us for a live introductory webinar every Thurs: http://www.asterisk.org/hello asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
[asterisk-users] Basic quetion on Asterisk usage
Hi all, I want peer-peer communication between two clients (soft phones) both are behind NAT.I have an accounts with SIP proxy for two clients. To communicate these two clients do i need to use Asterisk ? As per my understanding Asterisk acts like Gateway where conventional phone calls data transfer into internet voice calls. If am wrong please correct me . Thanks, Raghav. -- _ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- New to Asterisk? Join us for a live introductory webinar every Thurs: http://www.asterisk.org/hello asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] File Leak Handle in 11.60
I have a test system with a couple of FXS (50), BRI (4)m and a few dozen SIP channels that does not show your file problem under 11.6.0. I get at most 15 open files for a standard configuration. jg -- _ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- New to Asterisk? Join us for a live introductory webinar every Thurs: http://www.asterisk.org/hello asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] AGI Script not working
Thanks... I got it working actually I found with this command /usr/bin/perl -d from this I got to know that my library is missing and installed Asterisk-perl module and now its fine. Once again thank you. On Mon, Dec 2, 2013 at 3:05 PM, Gopalakrishnan N < gopalakrishnan...@gmail.com> wrote: > Library is Asterisk Perl library and module DBI. The same script working > in different machine with same Asterisk version and same Perl version. Am > able to see Tx and Rx from script. > > > > > On Mon, Dec 2, 2013 at 8:08 AM, Eric Wieling wrote: > >> Sounds like you are violating the AGI protocol. Which Perl AGI library >> are you using? >> >> >> -Original Message- >> From: asterisk-users-boun...@lists.digium.com [mailto: >> asterisk-users-boun...@lists.digium.com] On Behalf Of Gopalakrishnan N >> Sent: Saturday, November 30, 2013 1:27 AM >> To: Asterisk Users Mailing List - Non-Commercial Discussion >> Subject: [asterisk-users] AGI Script not working >> >> I have a Perl AGI script updating some values to database like recorded >> file path, unique ID and callerid. When I run the script with test >> dialplan, its not updating to database. >> >> Whereas database connection is fine, when I run agi debug I see only Tx >> packets not Rx packets, firewall is also OFF. >> >> Any other specific reason why there is no Rx. >> >> The same script working in one more Asterisk machine. >> >> Regards >> >> -- >> _ >> -- Bandwidth and Colocation Provided by http://www.api-digital.com -- >> New to Asterisk? Join us for a live introductory webinar every Thurs: >>http://www.asterisk.org/hello >> >> asterisk-users mailing list >> To UNSUBSCRIBE or update options visit: >>http://lists.digium.com/mailman/listinfo/asterisk-users >> > > -- _ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- New to Asterisk? Join us for a live introductory webinar every Thurs: http://www.asterisk.org/hello asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] AGI Script not working
Library is Asterisk Perl library and module DBI. The same script working in different machine with same Asterisk version and same Perl version. Am able to see Tx and Rx from script. On Mon, Dec 2, 2013 at 8:08 AM, Eric Wieling wrote: > Sounds like you are violating the AGI protocol. Which Perl AGI library > are you using? > > > -Original Message- > From: asterisk-users-boun...@lists.digium.com [mailto: > asterisk-users-boun...@lists.digium.com] On Behalf Of Gopalakrishnan N > Sent: Saturday, November 30, 2013 1:27 AM > To: Asterisk Users Mailing List - Non-Commercial Discussion > Subject: [asterisk-users] AGI Script not working > > I have a Perl AGI script updating some values to database like recorded > file path, unique ID and callerid. When I run the script with test > dialplan, its not updating to database. > > Whereas database connection is fine, when I run agi debug I see only Tx > packets not Rx packets, firewall is also OFF. > > Any other specific reason why there is no Rx. > > The same script working in one more Asterisk machine. > > Regards > > -- > _ > -- Bandwidth and Colocation Provided by http://www.api-digital.com -- > New to Asterisk? Join us for a live introductory webinar every Thurs: >http://www.asterisk.org/hello > > asterisk-users mailing list > To UNSUBSCRIBE or update options visit: >http://lists.digium.com/mailman/listinfo/asterisk-users > -- _ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- New to Asterisk? Join us for a live introductory webinar every Thurs: http://www.asterisk.org/hello asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
