Hello,
Im looking to buy a digium phone D70 unit just for testing on lab; to
really understand the phone and features.
I cant find any website with opinions; any here? Are they really valuable
to the price? (D70 quite expensive)
Does the SDK for building apps is usable? Can you build powerfull a
I understand why do I get call twice to my mobile when I execute the
following AMI command sets:
ACTION: Originate
Channel: Local/800@test
Timeout: 6
Priority: 1
and my dialplan look like this:
[test]
exten => 800,1,DIAL(SIP/447xx@voip);
exten => 800,n,Hangup()
How to prevent getting c
The solution:
Stop the Asterisk, made a backup of configuration files, delete files
and modules previously installed.
Then Reinstall with default config files with "make samples" and I only
insert the configuration of Broadvoice and immediately worked. Then I
restore the configuration files /etc
Please just reply to the mailing list.
- Original Message -
> Right you are,
>
> but when using bri_cpe I get:
>
> [May 9 23:08:45] WARNING[2775]: sig_pri.c:6969 pri_dchannel: PRI
> Error
> on span 4: Received MDL/TEI managemement message, but configured for
> mode other than PTMP!
>
>
Right you are,
but when using bri_cpe I get:
[May 9 23:08:45] WARNING[2775]: sig_pri.c:6969 pri_dchannel: PRI Error
on span 4: Received MDL/TEI managemement message, but configured for
mode other than PTMP!
This repeats itself every second.
The
bri_cpe_ptmp
settings seems to give the lea
> Hi Khalid,
>
> my setup is almost identical
>
> except for
> loadzone = be
> defaultzone = be
>
> (obviously)
>
> and in
>
> chan_dahdi.conf:
>
> [isdn4]
> signaling = bri_cpe_ptmp
> switchtype = euroisdn
> group = 2
> context = isdn
> dahdichan = 10,11
>
>
> this results into:
>
> ERROR
Hi Khalid,
my setup is almost identical
except for
loadzone = be
defaultzone = be
(obviously)
and in
chan_dahdi.conf:
[isdn4]
signaling = bri_cpe_ptmp
switchtype = euroisdn
group = 2
context = isdn
dahdichan = 10,11
this results into:
ERROR[1021]: chan_dahdi.c:14182 dahdi_pri_error: PRI
Hi Bart,
here is a working configuration in Netherlands:
/etc/dahdi/system.conf:
span = 1,1,0,ccs,ami
bchan = 1,2
hardhdlc = 3
span = 2,1,0,ccs,ami
bchan = 4,5
hardhdlc = 6
span = 3,1,0,ccs,ami
bchan = 7,8
hardhdlc = 9
span = 4,1,0,ccs,ami
bchan = 10,11
hardhdlc = 12
loadzone= nl
defaultzo
Yeah they have a wonderful policy that says "ISDN team are not contactable"
:( thanks a lot!!
On Wed, May 9, 2012 at 3:06 PM, Patrick Lists <
asterisk-l...@puzzled.xs4all.nl> wrote:
> On 09-05-12 20:57, khalid touati wrote:
> > Yeah sorry for that, I realized something is missing after I se
On 05/09/2012 12:59 PM, Bart Coninckx wrote:
Hi,
I'm experiencing difficulties to get a B410P running with Asterisk
10.3.1 and DAHDI 2.6.1.
Am I supposed to use DAHDI for this card and ISDN BRI for my country
(Belgium)?
That is the supported method to use in standard Asterisk, yes. DAHDI,
lib
On 09-05-12 20:57, khalid touati wrote:
> Yeah sorry for that, I realized something is missing after I sent the
> email, but it is exactly what I have (other than order here, which
> doesn't really matter: you posted ami,te,term, I have ami,term,te).
> Actually I had couple technicians from digium
Yeah sorry for that, I realized something is missing after I sent the
email, but it is exactly what I have (other than order here, which doesn't
really matter: you posted ami,te,term, I have ami,term,te).
Actually I had couple technicians from digium look at it and they said BT
equipements is not r
On 09-05-12 19:54, khalid touati wrote:
> Thank you for your answer, I think I posted dhadi version and so but
> let me add more details and recap them below:
>
> We are using asterisk 1.8.12.0 with dahdi 2.6.0, on CentOS 6.2. it's a
> digium card 1HA8-0400BLF
>
> output of dahdi_hardware: pci:0
Hi,
I'm experiencing difficulties to get a B410P running with Asterisk
10.3.1 and DAHDI 2.6.1.
Am I supposed to use DAHDI for this card and ISDN BRI for my country
(Belgium)?
thx,
BC
--
_
-- Bandwidth and Colocation Provide
Thank you for your answer, I think I posted dhadi version and so but let
me add more details and recap them below:
We are using asterisk 1.8.12.0 with dahdi 2.6.0, on CentOS 6.2. it's a
digium card 1HA8-0400BLF
output of dahdi_hardware: pci::04:08.0 wctdm24xxp+ d161:8008
HB8-
>From
On 09-05-12 18:46, khalid touati wrote:
> Should I understand that no Asterisk user has issues with ISDN "system
> access" configuration from UK? or maybe no one is using Asterisk In UK :) ?
I have no idea. But other than the error you have given very little
information to go on. Which card are yo
Problem SOLVED.
You'r right, this is a problem of codec mismatching. Activating sip debug i
can see it:
Capabilities: us - 0x802 (gsm|g726), peer - audio=0x10d
(g723|ulaw|alaw|g729)
[May 9 17:16:37] NOTICE[6444]: chan_sip.c:9188 process_sdp: No compatible
codecs, not accepting this offer!
I solv
Should I understand that no Asterisk user has issues with ISDN "system
access" configuration from UK? or maybe no one is using Asterisk In UK :) ?
On Tue, May 8, 2012 at 12:46 PM, khalid touati wrote:
> Hi All,
> I am posting this thread with the hope that someone in UK (or elsewhere)
> had a sim
On 5/9/2012 11:56 AM, Ricardo Carvalho wrote:
That's weird, because it's negotiated with success the codec ulaw for
outbound calls through the same SIP trunk.
My guess is the incoming call is not being matched with the peer you are
expecting. Do a sip debug and watch the output to see what pe
Do a "sip show peer PEERNAME" and check the codecs allowed for that specific
peer.
-Original Message-
From: asterisk-users-boun...@lists.digium.com
[mailto:asterisk-users-boun...@lists.digium.com] On Behalf Of Ricardo Carvalho
Sent: Wednesday, May 09, 2012 11:56 AM
To: Asterisk Users Mai
That's weird, because it's negotiated with success the codec ulaw for
outbound calls through the same SIP trunk.
Besides, ulaw and alaw shows up when i do "core show codecs audio" in the
asterisk CLI, and there exists both codec_ulaw.so and codec_alaw.so modules
under the path /usr/lib/asterisk/mo
On Wednesday 09 May 2012, Ricardo Carvalho wrote:
> [May 8 17:45:30] NOTICE[6444]: chan_sip.c:9188 process_sdp: No compatible
> codecs, not accepting this offer!
>
> Any help?
Are you sure you compiled all the codecs you need?
What happens if you run `make menuselect` in both the 1.4 source tre
Hi,
I've upgraded my asterisk 1.4 to the version 1.8.11. After making some
adjustments to the configuration files to port it to the new version, calls
between registered phones in asterisk, work fine, but inbound calls coming
from the SIP trunk I have with a telco to asterisk, don't work anymore.
I agree with Chad on this one. FreePBX is for a different kind of installs
from what you described. I believe if you pitch it as your solution; as you
have stated you will be disappointing. Before you start offering it up to
the bosses as the silver bullet. I would do a test install on some spar
24 matches
Mail list logo
