[Bristuff-users] "Cause 34" sum up

[Gunnar Schaller]

Hello,


> I'm surprised nobody noticed bristuff 0.4.0-RC1 . There is also 0.0.3 -q
> with a number of small fixes, though nothing as drastic, IIRC.

OK I will try the latest Bristuff and report here. By the way I'm
using qozap.


> But I'll point to another way this error could be create on a multi-port
> cards with BRI ptmp. Just to make sure that those two issues are not
> related.

> We had a slightly related issue yesterday: 

> we have a device with two BRI TE ports. For some reason I connected the
> BRI connector to the second connetor. As of habbit, I used a "catch-all"
> trunk (Zap/g1, and all the BRI TE ports had
> group=1,<something-else,port-specific>)

> The line was originally connected to the first BRI port, and things
> worked fine. Now I connected the line to the second port, and bam, I get
> exactly the error as above. 

> Why is that? Normally if a line is disconnected, the driver tells
> Asterisk that the port is in RED alarm. A channel in alarm i not taken
> into account when choosing the one to call through.


This is definitly not the case at my side. Every port is in a separate
group. After restarting Asterisk I can use the group again after
having "cause 34". It is a software problem.


> (And thus: use ptp if you can)


Not possible here. In Switzerland you cannot port your numbers to a
ptp connection. With ptmp you have multiple separate numbers (msn) and
with ptp you have a did.


Regards,
Gunnar