I've been testing through all revisions from 652 to 663
patch 661 is breaks (at least audio) connections an ppc - It did work without an bigendian-patch before, but commenting out the bigendian-part has no effect. Where must be something different but couldn't find it :(

Dirk Rieger schrieb:
problems visdn-patch-663 & asterisk-1.2.7.1 on ppc

1xhfc-pci TE-mode
1xhfc-pci NT-mode

I split up the log to show what happens..

Asterisk Ready.
INCOMING CALL via PSTN
*CLI>     -- Executing Goto("VISDN/visdn0/1.I", "demo|s|1") in new stack
   -- Goto (demo,s,1)
   -- Executing Wait("VISDN/visdn0/1.I", "1") in new stack
   -- Executing Answer("VISDN/visdn0/1.I", "") in new stack
   -- Executing Set("VISDN/visdn0/1.I", "TIMEOUT(digit)=5") in new stack
   -- Digit timeout set to 5
-- Executing Set("VISDN/visdn0/1.I", "TIMEOUT(response)=10") in new stack
   -- Response timeout set to 10
-- Executing BackGround("VISDN/visdn0/1.I", "demo-congrats") in new stack
   -- Playing 'demo-congrats' (language 'de')

ASTERISK HANGUP THE LINE

May 25 10:58:05 WARNING[6019]: file.c:584 ast_readaudio_callback: Failed to writ e frame

LIFTING HANDSET FROM ISDN-PHONE (NT)

   -- Executing VISDNOverlapDial("VISDN/visdn1/1.I", "") in new stack

NO SOUND
PUT DOWN HANDSET

   -- Executing VISDNOverlapDial("VISDN/visdn1/2.I", "") in new stack

LIFTING HANDSET 2.TIME - CHANNEL IS BLOCKED BY OTHER THREAD

   -- Executing Playback("VISDN/visdn1/2.I", "invalid") in new stack
May 25 11:03:09 WARNING[6016]: channel.c:2248 ast_write: Thread 810226928 Blocki ng 'VISDN/visdn1/2.I', already blocked by thread 811275504 in procedure ast_wait for_nandfds
   -- Playing 'invalid' (language '')
 == Auto fallthrough, channel 'VISDN/visdn1/2.I' status is 'UNKNOWN'



_______________________________________________
Visdn-hackers mailing list
[email protected]
https://mailman.uli.it/mailman/listinfo/visdn-hackers




_______________________________________________
Visdn-hackers mailing list
[email protected]
https://mailman.uli.it/mailman/listinfo/visdn-hackers

Reply via email to