On 2014-08-19 23:56, Jeff LaCoursiere wrote:
Hello,
I wrote earlier today about a new PRI installation in the Caribbean, where all outbound
calls are functioning fine *except* calls to Sprint phone numbers, which get rejected
immediately as "busy".
The telco has been working with their switch
Doubtful that T309 or T316 are causing the problem, but you can always change
them to correspond with their defaults.
http://www.nmscommunications.com/manuals/6272-16/appendxe.htm
--Don
From: asterisk-users-boun...@lists.digium.com
[mailto:asterisk-users-boun...@lists.digium.com]
Hello,
I wrote earlier today about a new PRI installation in the Caribbean,
where all outbound calls are functioning fine *except* calls to Sprint
phone numbers, which get rejected immediately as "busy".
The telco has been working with their switch manufacturer and took the
output of "pri sh
Grepping the output of the strace revealed this:
stat("/root/.terminfo", 0x7fff8622ed50) = -1 EACCES (Permission denied)
open("/root/.asterisk_history", O_RDONLY) = -1 EACCES (Permission denied)
open("/root/.odbcinst.ini", O_RDONLY) = -1 EACCES (Permission denied)
[this one many times]
That
On Tue, Aug 19, 2014 at 11:36 AM, Mitch Claborn
No, that's not it. The wording is different.
Can you run Asterisk via strace? Something like:
sudo -u asterisk strace /usr/sbin/asterisk -c -p -U asterisk
--
Thanks in advance,
On Tue, Aug 19, 2014 at 3:38 PM, Asterisk Development Team
wrote:
> The Asterisk Development Team has announced the release of Asterisk 12.5.0.
> This release is available for immediate download at
> http://downloads.asterisk.org/pub/telephony/asterisk
>
> The release of Asterisk 12.5.0 resolves s
Asterisk 11.8.1
Today our Asterisk server locked up. Looking through the asterisk full log, I
see the following over and over again and the log just continues to grow until
we reboot Asterisk. Has anyone seen anything like this before or have any idea
what may cause it?
[Aug 19 14:41:26] DEB
I tried grep too.
No 3rd party modules - this is an out-of-the box download and build.
I'm guessing that some library function is being called to read a file
and the error is happening there?
Mitch
On 08/19/2014 02:33 PM, Matthew Jordan wrote:
On Tue, Aug 19, 2014 at 11:36 AM, Mitch Clabo
The Asterisk Development Team has announced the release of Asterisk 12.5.0.
This release is available for immediate download at
http://downloads.asterisk.org/pub/telephony/asterisk
The release of Asterisk 12.5.0 resolves several issues reported by the
community and would have not been possible wit
The Asterisk Development Team has announced the release of Asterisk 11.12.0.
This release is available for immediate download at
http://downloads.asterisk.org/pub/telephony/asterisk
The release of Asterisk 11.12.0 resolves several issues reported by the
community and would have not been possible w
The Asterisk Development Team has announced the release of Asterisk 1.8.30.0.
This release is available for immediate download at
http://downloads.asterisk.org/pub/telephony/asterisk
The release of Asterisk 1.8.30.0 resolves several issues reported by the
community and would have not been possible
On Tue, Aug 19, 2014 at 11:36 AM, Mitch Claborn wrote:
> No, that's not it. The wording is different.
>
grep doesn't turn up your phrase:
~/projects/12$ grep --include=*.c --include=*.h -r "Error opening file" .
~/projects/12$
Are you using any 3rd party modules that aren't delivered with Aste
Perfect! Exactly what I was looking for.
Cheers,
j
On 08/19/2014 12:23 PM, Eric Wieling wrote:
I doubt PBX settings (other than CallerID) would break calling to only one
specific carrier.
Have you tried pri show span X?
From one of our boxes:
pbx*CLI> pri show span 1
Primary D-channel:
I doubt PBX settings (other than CallerID) would break calling to only one
specific carrier.
Have you tried pri show span X?
>From one of our boxes:
pbx*CLI> pri show span 1
Primary D-channel: 24
Status: Up, Active
Switchtype: National ISDN
Type: CPE
Remote type: Unknown node type
Overlap Dial:
Hello,
I am having odd issues with a new PRI based installation. Outbound
calls work for all numbers except those that terminate at Sprint! The
telco is new to PRI (this is in the Caribbean) and say that Sprint is
rejecting the calls, and asked for our PRI settings so they can work
with thei
No, that's not it. The wording is different.
Mitch
On 08/18/2014 02:28 PM, Paul Greenberg wrote:
Mitch,
Is it the below error?
if ((fd = open(filename, O_RDONLY)) < 0) {
ast_log(LOG_WARNING, "Cannot open file '%s' for reading:
%s\n", filename, strerror(errno));
Hello All;
After trying A2Billing and certainly when the trunk is analogue lines (FXO
ports), I faced a problem that the channels were not hanged up properly from
time to time which cause us to do restart for the dahdi. Without A2Billing, I
was able to handle the Dial scenario properly and no h
17 matches
Mail list logo
