Search results for query: *

Actually, I think I have had mostly the right setup. A little elaboration. All calls are going out through the merlin's pri into an asterisk system (restrictions are handled here based on legend extension's 4-digit cid). These will be routed via Voip. If a path can't be made or the network is...

I would like to have a remote system (connected via pri) utilize legend loop start trunks for some outbound calls. What parameters do I have to fill out?

Well, I can control the text portion of cid easy enough within my system - but external callers are able to send in larger strings (we have national PRIs from our local telco - I think these support 64 characters). It is my suspicion that this may be responsible for many people's troubles with...

...well, I'll assume you are unfamiliar with asterisk. It is an open source pbx that runs on linux (bsd, or osX). That can deployed with modest hardware costs. http://asteriskpbx.com/ As such, it offers a great deal of flexibility where it can integrate with traditional telephony & be a voip...

...a little trivia. This is the board where >15 character caller ID name strings are causing resets. 100d-U 517M15 Hardware Vintage: 0A Firmware Vintage: 91 Application Vintage: 18 ...timming incoming strings (I'm using asterisk which gives you a lot of latitude) makes the board workable...

I have 2 Legend w PRI systems. I traced a disconnect problem on one of them to callerid strings longer than 15 characters causing the dchannel to drop and reset all the bchannels - disconnecting any calls in progress. I'll find out what vintage the T board is. Anyway you may want to test...

I have been meaning to put together some documentation (to post here and the asterisk wiki) on integrating asterisk and the legend over PRI. Got things working pretty nicely. Illuminating message waiting lamps is one of the final hurtles. John

Found out what is happening... longer caller ID name strings are causing the d-channel to reset and drop calls in progress. Does anyone know what the maximum length of this parameter is (for 5ess - and does the Legend match this spec)? There will be a fix for this in Asterisk soon.

One more thing... I had this port configured as a standard T. It may have been a DID. I think I have removed all the old configuration but who knows? Is there a way I can 'wash' all the past configuration for a slot (in this case 5 - and there are cards to the right)? John

I have a Legend connected to a PC running asterisk via a PRI. Certain calls coming in on a 5ess PRI are being rejected. Here is the setup telco_PRI -> Asterisk_1 -> Asterisk_2 -> Merlin_Legend_2 ...are accepted. System_75_T1 -> Asterisk_1 -> Asterisk_2 -> Merlin_Legend_2 ...are rejected when...

I'm connected to Legend 7.0 via 5ess PRI to an asterisk pbx. I am routing unanswed (both extenal & internal) calls back out through the PRI to UDP extension 6799 for voicemail - which is working fine and asterisk is capturing the called extension number. I would like to turn on the message...

I'd like to ask the same question - but for legend 7.0

Yes, the loopback test is successful. By the way, the board is a 517E15 with Hardware: 2B & Firmware 90.

I have tried a 100D T interface in slots 3 & 5. It is failing Maintenance/Slot/3or5/Demand Test/BoardCntrlr/Test Once ...while busyed-out. Is this test applicable to the 100D? Thanks, John

I have been getting stumped getting a PRI between asterisk and a legend. (I think it is the particular 100D module in the legend: 517M15. Does the Magic use the 100D?) I am in the processes of caving in and setting up the T as tie lines - which work. Please shoot me an email if you have tips for...

...back down to a 517E15?? Is this a re-load of firmware - or a different module?

...back down to a 517E15... ?? I assume you can re-load firmware. Where can I get this? jharragi@mw.k12.ny.us ...here is the pri output - this has been freshly reconfigured. (Channel 23 is now comming up. I'm sure that was due to the million things I was playing around with.) John A PRI...

You guys helped me over the first hurdle on another thread by getting the 100D out of slot 1 (That cleared the endless SABME requests). Current card count and order: Processor 3 - 008 1 - 100D -- 517M15 1 - 408 GS/LD-MLX ...and in expansion cabinet... 1 - 008 3 - 012

It seems I have a classic legend problem, as described below. Does anyone know the cause of this? My config is 5ess, esf, b8zs. Additionally, each of the b-channels except 23 come up as described. When the T is idling, supervisory frames transfer back and forth every few seconds. When I try to...

Looks like you guys are steering me in the right direction... Just started reconfiguring the whole system - but just supervisory frames in pri output now. I'll do a writeup on how to get legend running with asterisk when I'm done. John