El mar, 25-09-2007 a las 17:51 +0200, Mikael Bjerkeland escribió: > > Internal calls between the SIP extensions works perfectly, as well as > > the outbound context. The problem is the incoming context: here's the > > output from the CLI: > > > > -- Starting simple switch on 'Zap/3-1' > > Sep 25 09:27:58 ERROR[3085245328]: chan_zap.c:5998 ss_thread: Zap/3-1: > > ring timeout reached with no data or events?!? > > -- Hungup 'Zap/3-1' > > -- Starting simple switch on 'Zap/3-1' > > Sep 25 09:28:08 ERROR[3085245328]: chan_zap.c:5998 ss_thread: Zap/3-1: > > ring timeout reached with no data or events?!? > > -- Hungup 'Zap/3-1' > > -- Starting simple switch on 'Zap/3-1' > > Sep 25 09:28:18 ERROR[3085245328]: chan_zap.c:5998 ss_thread: Zap/3-1: > > ring timeout reached with no data or events?!? > > -- Hungup 'Zap/3-1' > > -- Starting simple switch on 'Zap/3-1' > > Sep 25 09:28:28 ERROR[3085245328]: chan_zap.c:5998 ss_thread: Zap/3-1: > > ring timeout reached with no data or events?!? > > -- Hungup 'Zap/3-1' > > -- Starting simple switch on 'Zap/3-1' > > Sep 25 09:28:38 ERROR[3085245328]: chan_zap.c:5998 ss_thread: Zap/3-1: > > ring timeout reached with no data or events?!? > > -- Hungup 'Zap/3-1' > > -- Starting simple switch on 'Zap/3-1' > > -- Zap/3-1: Done CID/distinctive ring detection: > > cadence=1280,4060,960,0,0 > > == Starting Zap/3-1 at incoming,,1 failed so falling back to exten 's' > Take a look at the line above. It tries to send the call to > incoming,NOTHING,1 and probably falls back to exten s after the 40 > seconds you mentioned. I have no experience with analog Zap so I don't > know if what you are seeing is normal behaviour, although I doubt it, > but I do believe that if you add the following it will work: > > exten => !,1,Dial(SIP/lclaros&SIP/mvasquez,10,o) > exten => !,2,Dial(SIP/fmartinez&SIP/ovaldez,10,o) > exten => !,3,Dial(SIP/csermeno&SIP/rgamez,30,o) > exten => !,4,Hangup > > ( ! wildcard, matches zero or more characters immediately) > > > This is probably just a workaround. It _should_ go to the s exten > immediately.
But the line you point to happens after 40 seconds of ringing, and only after "Zap/3-1: Done CID/distinctive ring detection: cadence=1280,4060,960,0,0". Could the behaviour I'm observing be caused by failed attempts to detect CID? I'll disable caller id and report back. Also, what's the meaning of these repeating lines: > > chan_zap.c:5998 ss_thread: Zap/3-1: > > ring timeout reached with no data or events?!? > > -- Hungup 'Zap/3-1' > > -- Starting simple switch on 'Zap/3-1' -- Oscar _______________________________________________ Callweaver-users mailing list [email protected] http://lists.callweaver.org/mailman/listinfo/callweaver-users
