In fact, with EWSD V13 you can't remove CRC4 in PRI mode. Regards,
Gus ----- Original Message ----- From: "Storer, Darren" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, April 07, 2004 8:32 PM Subject: RE: [Asterisk-Users] Siemens EWSD 13 > Hi, > > I had exactly the same symptoms today with a co-located * connected to a > Public Switch here in the UK. The problem was solved by insisting that the > Telco turned on CRC4 at their end and then, after an 'init 6', layer two > settled down on both systems. > > I was taught that if you are connecting to a full specification Q.931 > circuit, CRC4 should be enabled by default; in the event that one end does > not support CRC4 the other end should auto-negotiate back and the circuit > should still align without problems. Having said all of this I have yet to > see auto-negotiation of CRC4 on any equipment (Public Network or CPE) and > suspect that I was not told the truth in the first place... > > Selection of CRC4 seems to be random from Telco to Telco even on an install > by install basis within the same Carrier. It's the first thing to check when > new kit appears to be unstable.. > > HTH > > Darren > -- > Comgate > Telco>Internet<Broadcast > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] Behalf Of > [EMAIL PROTECTED] > Sent: 07 April 2004 14:59 > To: [EMAIL PROTECTED] > Subject: [Asterisk-Users] Siemens EWSD 13 > > > Hi all, > > Has anyone got any experience with hooking Asterisk up with a > Siemens EWSD 13 switch over a E1/PRI ? > We're located in Belgium (Europe) and one of our telecom partners > uses this switch. > > We connected one of our TE410P ports with their switch, but the status > light on the TE410P card keeps blinking red. > On their side they are getting a DSA (distance service alarm) error, so > this normally means the devices 'see' eachother.. but there are still > problems with the signalling. > > Our config below is the same as we are using for MCI, one of our other > telecom partners. > > We tried changing the LBO and timing, but no luck. > As you see the signalling is carried over channel 16 (default). > > TX and RX have also been regularly switched, so no luck.. > > Their switch is providing the timing. > > The telecom operator has double checked the asterisk config several > times, and it's conform to their setup. > > The only thing they couldn't find in the Asterisk config is a > 'multiframing' option. But I presume this is automatically detected or > set by default ? > They also tried normal/single(?) framing, but no difference. > > The card has also been tested with our MCI E1, and works flawlessly, so > no hardware issue. > > Anyone got any further ideas ? > > Any info or help greatly appreciated! > > Our config, > > *** zaptel.conf *** > span=1,1,6,ccs,hdb3,crc4,yellow > bchan=1-15 > bchan=17-31 > dchan=16 > > *** zapata.conf *** > [channels] > switchtype=euroisdn > signalling=pri_cpe > pridialplan=unknown > > group=1 > channel => 1-15,17-31 > > <other zapata standard config> > > > > _______________________________________________ > Asterisk-Users mailing list > [EMAIL PROTECTED] > http://lists.digium.com/mailman/listinfo/asterisk-users > To UNSUBSCRIBE or update options visit: > http://lists.digium.com/mailman/listinfo/asterisk-users > > _______________________________________________ > Asterisk-Users mailing list > [EMAIL PROTECTED] > http://lists.digium.com/mailman/listinfo/asterisk-users > To UNSUBSCRIBE or update options visit: > http://lists.digium.com/mailman/listinfo/asterisk-users _______________________________________________ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
