[Asterisk-Users] Asterisk & Meridian Tie Line

[Tim Panton]

On 17 May 2006, at 22:48, Andy Kirby wrote:

> I am new to the group but have searched the doc's FAQ's etc before  
> posting here.
>
>  We are attempting tie our asterisk server/service to the  
> building's PBX, the building is in the UK and the local PBX is a  
> meridian option 11 installed and mainteined by BT.
>
> BT Have installed a NTBK50AA E1-PRI card in the meridian with  
> daughter cards NTBK51AA (D channel) and NTAK20BD (Clocking)
>
>  I have asked BT to configure the card as a Master (Exchange end)  
> E1 Euro ISDN (Just like a standard ISDN30e)
>
>  They claim to have done this in line with the model they use to  
> interface to Cisco routers etc.
>
>  I have installed a Digium TE411P in our server looped back the  
> span 2 port (Gives a green light and OK with same config as span 1)  
> and am using a crossover cable to link the PBX to our server. (We  
> tried a pucker BT cross over cable with exactly the same results as  
> mine and a striahgt through gives us nothing at all, I guess as you  
> might expect)
>
> I have configured the Zap span for 1 clocking (Primary) 1 line  
> build out, with the framing etc as CCS, HDB3, CRC4
>
>
> But they don't appear to want to synchronise/talk to each other.
>
>
> ZTTool claims that the span is up and down more times than a  
> fiddlers elbow  and the clocking source is internal.
>
>  ( Might I expect the alarm state to be constant if the framing etc  
> was matched and the clock source to show as external ??)
>
>
> The alarms are cylcling from red to red/yellow and finaly to red/ 
> yellow/recover before falling back to red and starting again.
>
>  I think I may be missing something that is probably blindingly  
> obvious to someone in the know.
>
>  The BT guy has been very good and is trying to help us get this  
> going but seems rather nonplussed with the terms CRC4, CSS and HDB3...
>
> Please can somone help and point me (and I guess by extension the  
> BT guy) in the right direction.

When you are changing the low level params in /etc/zaptel.conf you  
may need to power cycle the
box. I found they don't seem to take unless you powercycle.


Tim.

Tim Panton
tim at mexuar.com