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
Logically yes, once the call hangup, the hangup handler will execute.
Regards,
On Mon, Aug 18, 2014 at 7:04 PM, Paul Greenberg p...@greenberg.pro wrote:
Hi,
I am mostly concerned with inbound calls.
Would it work the same?
Regards,
Paul
--
*From:*
On 08/04/2014 03:03 PM, David Duffett wrote:
Please come back to let us know if this actually does fix the issue.
So far so good the external voltage supply for the OpenVOX card has arrived and
I can confirm
that the BT Versatility PBX worked like a charm. DAHDI channel has been
configured
Great news!
On Wednesday, August 20, 2014, Roberto Fichera ker...@tekno-soft.it wrote:
On 08/04/2014 03:03 PM, David Duffett wrote:
Please come back to let us know if this actually does fix the issue.
So far so good the external voltage supply for the OpenVOX card has
arrived and I can
On Aug 19, 2014, at 5:56 PM, Jeff LaCoursiere
j...@jeff.netmailto:j...@jeff.net wrote:
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.
I don’t
On 08/20/2014 07:58 AM, Scott L. Lykens wrote:
On Aug 19, 2014, at 5:56 PM, Jeff LaCoursiere j...@jeff.net
mailto:j...@jeff.net wrote:
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,
For my NI2 PRIs I've always used 10 digits for everything and no +1
--Don
From: asterisk-users-boun...@lists.digium.com
[mailto:asterisk-users-boun...@lists.digium.com] On Behalf Of Jeff
LaCoursiere
Sent: Wednesday, August 20, 2014 9:41 AM
To: asterisk-users@lists.digium.com
Subject:
NXXNXX is the correct format of CallerID numbers in NANPA. The leading 1
is not part of any NANPA phone number. Toll free area codes are also not
valid for CallerID.
From: asterisk-users-boun...@lists.digium.com
[mailto:asterisk-users-boun...@lists.digium.com] On Behalf Of Jeff
We have a client set up with an Elastix 2.5 install running Asterisk 11 and
2.11 using Aastra 6731i IP phones.
The client would like to have the feature where all internal calls use a
distinctive ring (alert-info) so it sounds different than incoming external
calls and they want it to check if
What about the text portion? Should that never be sent? I was indeed
sending the '1', and I will remove that to see if it solves my problem,
but I also have the company name in there. I feel like a newb asking
such questions, but I've never had this issue before :)
Company 1NXXNXX
CallerID Name doesn't really matter. Either your carrier will remove it when
handing the call off to the next hop or the terminating carrier will ignore any
CallerID name data and do a name lookup in their own database using the
CallerID number. This is why your CallerID name can be
It's possible that Sprint is burping on the name. Try first dropping the
1. Then try dropping the name also, if necessary.
--Don
From: asterisk-users-boun...@lists.digium.com
[mailto:asterisk-users-boun...@lists.digium.com] On Behalf Of Jeff
LaCoursiere
Sent: Wednesday, August 20,
I would let the phone handle the different ring tones, if possible. For my phones a SIPAddHeader
with something like Alert-Info: http://127.0.0.1/Ringer3 does the trick, but the syntax
might be vendor specific. The other problem should be taken care of with call queues.
jg
--
Hello all,
I am running asterisk on VMs with standby heartbeat configuration,
Heartbeat assigns a virtual IP 172.20.255.40 on machine afterwards asterisk
is started. In the sip.conf, I have explicitly define
bindaddr=172.20.255.40 but sometimes I see packets coming from physical IP
172.20.255.41
Sadly none of these changes have made any difference. I'll report the
resolution for posterity once we find it.
Thanks,
j
On 08/20/2014 10:13 AM, Don Kelly wrote:
It’s possible that Sprint is burping on the name. Try first dropping
the “1.” Then try dropping the name also, if
PRI intense debug should show all you need to fix this.
On Wed, Aug 20, 2014 at 12:13 PM, Jeff LaCoursiere j...@jeff.net wrote:
Sadly none of these changes have made any difference. I'll report the
resolution for posterity once we find it.
Thanks,
j
On 08/20/2014 10:13 AM, Don Kelly
On 8/20/14, 11:28 AM, Steve Totaro wrote:
PRI intense debug should show all you need to fix this.
Right, the sooner you post this debug here the sooner we can help.
Otherwise its just guesswork.
On Wed, Aug 20, 2014 at 12:13 PM, Jeff LaCoursiere j...@jeff.net
mailto:j...@jeff.net wrote:
On 08/20/2014 12:04 PM, Andres wrote:
On 8/20/14, 11:28 AM, Steve Totaro wrote:
PRI intense debug should show all you need to fix this.
Right, the sooner you post this debug here the sooner we can help.
Otherwise its just guesswork.
On Wed, Aug 20, 2014 at 12:13 PM, Jeff LaCoursiere
Do you also dial only 7 digits when calling from your cellphone when it works?
Have you tried using the whole number in your dial?
From: asterisk-users-boun...@lists.digium.com
[mailto:asterisk-users-boun...@lists.digium.com] On Behalf Of Jeff LaCoursiere
Sent: Wednesday, August 20, 2014
Ok, here is an intense debug trace. I've replaced the phone numbers
to protect the innocent. The smoking gun seems to be this:
Ext: 1 Cause: Destination out of order (27)
Though I have no idea why... calling the same destination from my cell
phone works fine. We only send seven digits
Yes from the local cell phone seven digits is enough. We have tried
sending ten digits with the same result over the PRI.
Cheers,
j
On 08/20/2014 12:38 PM, Eric Wieling wrote:
Do you also dial only 7 digits when calling from your cellphone when
it works? Have you tried using the whole
I have a question about dispatching calls...
If I try to dispatch a call on line 1 using the AMI
and I check in my table to see if line 1 is available and it is
So I have done my checking now I dispatch my call
and at that same time a call comes in on line 1 and now its no longer
available
On Wed, 20 Aug 2014, Jerry Geis wrote:
I have a question about dispatching calls...
If I try to dispatch a call on line 1 using the AMI
and I check in my table to see if line 1 is available and it is
So I have done my checking now I dispatch my call
and at that same time a call comes in on
-Original Message-
From: asterisk-users-boun...@lists.digium.com
[mailto:asterisk-users-boun...@lists.digium.com] On Behalf Of Steve Edwards
Sent: Wednesday, August 20, 2014 9:01 PM
To: Asterisk Users Mailing List - Non-Commercial Discussion
Subject: Re: [asterisk-users] Dispatching calls
24 matches
Mail list logo
