VoIP Mailing List Archives

[moises.silva at gmail.com]

What kind of problems are you talking about and what you want to modify?

On Thu, Mar 6, 2008 at 2:42 PM, Jessica Gonzalez Arriagada
<jgonzalez82 at gmail.com> wrote:

[jgonzalez82 at gmail.com]

The standard G.732 :

*Multiframe Aligment Signal:
*
When Timeslot 16 of the E1 frame is used for Channel Associated Signaling
purposes, Frame 0 contains information that is used by the receiver to
identify the incoming frame. Specifically, this pattern in Timeslot 0,
Frame 0 is called the Multiframe Alignment Signal (MFAS).

| *Bit 1* | *Bit 2* | *Bit 3* | *Bit 4* | *Bit 5* | *Bit 6*|
*Bit 7* | *Bit 8 |*
Frame 0 | ------- | ------- | ------- | ------- | ------- | ------- |
------- | -------- |
| 0 | 0 | 0 | 0 | *X* | *Y*
| * X* | *X * |
X = Spare Bits, set to 1 if not used.
Y = Yellow Alarm (Loss of* *MultiFrame Alignment Signal)
(0 = Normal | 1 = Loss of MFAS)

But, I used a analyser and I saw :

0000 0000 and must be 0000 1000

i need to change the bit *X*
**
Regards,
Jessi





On 3/6/08, Moises Silva <moises.silva at gmail.com> wrote:

[moises.silva at gmail.com]

Well, then it is irrelevant what version of unicall, spandsp, asterisk
etc you are using.

All that it could matter is your zaptel version and zaptel.conf
configuration. I ignore why you need to control the bit pattern at
that level, but AFAIK zaptel only let you control the CAS ABCD bits in
E1 timeslot 16 using ioctl()'s. Regarding bits in timeslot 0 and MFAS,
I suppose that is in complete control of the zaptel drivers. You have
the code available to dig into it.

- Mois?s Silva

On Fri, Mar 7, 2008 at 8:52 AM, Jessica Gonzalez Arriagada
<jgonzalez82 at gmail.com> wrote: