[asterisk-dev] Moving call from channel x to channel x

[Håkon Nessjøen]

Hi,

The sync problems was not the cause of the pri 'fix up' messages. Our telco
provider says now that the sync signals is correct.

But I am still getting a lot of these messages:
[Jan 18 15:32:24] WARNING[21581] chan_dahdi.c: Call specified, but not
found?
[Jan 18 15:32:24] WARNING[21581] chan_dahdi.c: Hangup on bad channel 0/8 on
span 1
[Jan 18 15:32:29] WARNING[21581] chan_dahdi.c: Call specified, but not
found?
[Jan 18 15:32:29] WARNING[21581] chan_dahdi.c: Hangup on bad channel 0/8 on
span 1
[Jan 18 15:33:52] WARNING[21581] chan_dahdi.c: Can't fix up channel from 2
to 3 because 3 is already in use
[Jan 18 15:33:52] WARNING[21581] chan_dahdi.c: Answer requested on channel
0/3 not in use on span 1
[Jan 18 15:33:52] WARNING[21581] chan_dahdi.c: Can't fix up channel from 3
to 2 because 2 is already in use
[Jan 18 15:33:52] WARNING[21581] chan_dahdi.c: Hangup REQ on bad channel 0/2
on span 1

Also on a unrelated note these:
[Jan 18 15:47:35] WARNING[24047] chan_dahdi.c: Unrecognized prilocaldialplan
NPI modifier: k
[Jan 18 15:47:35] WARNING[24047] chan_dahdi.c: Unrecognized prilocaldialplan
NPI modifier: o
[Jan 18 15:47:35] WARNING[24047] chan_dahdi.c: Unrecognized prilocaldialplan
NPI modifier: w

So anyone have any idea? This is *1.6.1.2 on a x86_64 with a Sangoma A104
card.

What is the function of "pri fixup"? These warning messages surely seems
everything but harmless.

Håkon


2010/1/13 Håkon Nessjøen <haakon at avelia.no>

> 2010/1/13 Håkon Nessjøen <haakon at avelia.no>
>
>> Now I'm getting these messages:
>>
>> [Jan 13 10:53:36] WARNING[31124]: chan_dahdi.c:10661 pri_fixup_principle:
>> Call specified, but not found?
>> [Jan 13 10:53:36] WARNING[31124]: chan_dahdi.c:11803 pri_dchannel: Hangup
>> on bad channel 0/13 on span 1
>> I found out via our TELCO company, that one of my ports was syncing wrong.
>>
>>
>
> So I checked the wanpipe configuration, and to my surprise, port 1 of my
> card was configured by wancfg to be master clock...
> Do you think syncronization issues like this could be the reason for these
> problems?
>
> I will reboot the system tonight, and talk with the telco provider
> tomorrow, if the signal is syncing more correct. And if I'm really lucky,
> the other problems will go away too.. (my main problem talking with the
> telco about was that faxes going through the system (pure channel bridging)
> did not come out correctly on the other side)
>
> Another thing, (i'm not sure if related to the master syncing or not) is
> that I see this in my dmesg:
> [   33.743987] wanpipe1: Card TDM Rsync Rx=1 Tx=3
> [   33.744043] wanpipe2: Card TDM Rsync Rx=0 Tx=2
> [   33.744076] wanpipe3: Card TDM Rsync Rx=0 Tx=2
> [   33.744110] wanpipe4: Card TDM Rsync Rx=0 Tx=2
>
> I'm slowly realising that my mails are becoming more -user related than
> -dev related, if this is the sollution to the "pri_fixup" problems.
> If not, I will post a bug report.
>
> Regards,
> Håkon
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.digium.com/pipermail/asterisk-dev/attachments/20100118/37ada713/attachment.htm