[Asterisk-Dev] libpri changes break functionality - take 2

[Matthew Boehm]

I hate to bring it up again, but the problem still exists and I've heard
nothing from anybody. I just updated our primary * server last night to
newest everything and we can't make outbound calls using our PRI. Inbound
works fine.

    -- Executing Dial("SIP/3044-a372", "ZAP/R1d/7134687866|60|WT") in new
stack
    -- Requested transfer capability: 0x00 - SPEECH
    -- Called R1d/7134687866
    -- Channel 0/8, span 1 got hangup
    -- Channel 0/8, span 1 received AOC-E charging 808597303 units
May 12 08:45:02 WARNING[21772]: chan_zap.c:7483 zt_pri_error: PRI: Call
Reference Length not supported: 0
    -- Zap/8-1 is circuit-busy
    -- Hungup 'Zap/8-1'
  == Everyone is busy/congested at this time (1:0/1/0)

libpri versions prior to April 22 work fine. This "AOC-E" stuff was added
around 4/22 and breaks outbound calls.

Normally I would not have updated my libpri but there were some changes to
chan_zap that forced me to upgrade libpri.

Any ideas? Should I create a bug note?

-Matthew



Matthew Boehm wrote:
>> Something changed in libpri from 04/21/05 to 04/22/05 which causes
>> our asterisk to be unable to send calls via PRI.
>>
>> I did the following steps to find where the breakage was (I actually
>> started with 4/18 and progressed up daily until I got breakage):
>>
>> cvs co -D "April 21, 2005" libpri
>> cd libpri/
>> make; make install
>> cd ../asterisk/
>> make bininstall
>> Start up asterisk
>> load chan_zap.so
>> All 96 channels started, B and D
>> Able to recieve calls via PRI. Able to send calls via PRI
>>
>> stop asterisk.
>> rm -f libpri/
>>
>> cvs co -D "April 22, 2005" libpri
>> cd libpri/
>> make; make install
>> cd ../asterisk/
>> make bininstall
>> Start up asterisk
>> load chan_zap.so
>> All 96 channels started, B and D
>> Able to recieve calls via PRI
>> ** NOT able to send calls via PRI **
>>
>> I've attached 2 intense pri debugs. The date in the debug file
>> corresponds to which cvs version I checked out.
>>
>> In both cases the call was sent from primary asterisk server to this
>> server over IAX.
>> Each debug has the info for 1 call: 7134687866
>>
>> Let me know if you need debug traces from the CO side. I can get
>> them.
>>
>> Hope this helps,
>> Matthew