[Asterisk-Users] Re: Asterisk and Pleiades P32mxi [followup]

Peter Nixon listuser at peternixon.net
Tue Apr 20 04:30:09 MST 2004


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Thursday 15 April 2004 00:38, Peter Nixon wrote:
> Hi Guys
>
> I have an Asterisk box with an E100P card connected to a Pleiades P32mxi
> (http://www.pleiadescom.com/p32mxi.html)
>
> When I set the channel bank and asterisk to use Loop Start (or Kewl Start)
> to communicate calls can happily go from asterisk, via the channel bank to
> PSTN. However, Asterisk sees these calls as being answered immediately
> regardless of if the call is still ringing or actually answered. The
> channel bank has Answer Supervision installed (Voice Activity Detection)
> and the debug messages on the channel bank show that this is working
> correctly.
>
> It appears that Loop Start signaling does not contain enough information
> for Asterisk to detect the ringing state of the call, and at the
> recommendation of Pleiades I would like to change my signaling to "E & M"
> or "E & M Wink" (Actually they recommend to use "R2 Digital" signaling but
> I dont think asterisk supports this).
>
> The problem is when I configure E & M (Or E & M Wink) on both the channel
> bank and asterisk the channel bank fails to see ANY signaling comming over
> the E1 interface. Nada, nothing, zilch.. I have spent MANY hours on this
> problem with Pleiades tech support, and quite a few calls to Digium also
> but I cannot get this working. Does anyone else have a Pleiades channel
> bank?? Has anyone else gotten one working with E & M?

In a followup to this, so that the list archives will have an answer, and to 
answer the people who have mailed me privately with the same problem.

This problem was due to a bug in Asterisk. Mark has kindly fixed the problem, 
and CVS dated 2004-04-19 or later should have the fix.

The problem is that E&M signaling on E1 trunks actually uses different 
characters for the signaling to E&M on T1 trunks. Asterisk did not know about 
E&M E1 signaling so therefore any E1 devices connected to Asterisk via E1 
using E&M signaling would not understand what Asterisk was saying 

The new code in CVS adds a "signalling=em_e1" type for use in zapata.conf 
which works in the same manner as "signalling=em" but for E1 trunks.

Mark has not yet added support for E&M Wink on E1 but hopefully he will do so 
in the future.

Regards

- -- 

Peter Nixon
http://www.peternixon.net/
PGP Key: http://www.peternixon.net/public.asc
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)

iD4DBQFAhQnHAcdsUt9pJjwRAp57AJYuhfm6f1zRyCEAoNWRESXCIbKXAKCBiCNC
WPtXrWKuVf1PwT1wTmphnQ==
=+UpN
-----END PGP SIGNATURE-----



More information about the asterisk-users mailing list