search for: isdn_in

Displaying 3 results from an estimated 3 matches for "isdn_in".

2010 Mar 17
1
BT ISDN-30 Call Failures
...ger.c: -- Hungup 'Zap/30-1' [Mar 17 16:58:50] VERBOSE[6630] logger.c: == Spawn extension (from-sip, 01780471800, 18) exited non-zero on 'SIP/197-b6726980' Here's an example of the inbound failure: [Mar 17 17:04:46] VERBOSE[13006] logger.c: -- Executing [846092 at isdn_in:1] Ringing("Zap/20-1", "") in new stack [Mar 17 17:04:46] VERBOSE[13006] logger.c: q931.c:2844 q931_alerting: call 79 on channel 20 enters state 7 (Call Received) [Mar 17 17:04:46] VERBOSE[13006] logger.c: > Protocol Discriminator: Q.931 (8) len=9 [Mar 17 17:04:46] VERBOS...
2006 Oct 18
2
echotraining=yes in misdn.conf is invalid or out of range.
...sdn reload". ------------------------------------------------- And here is my misdn.conf: [general] debug=1 bridging=no tracefile=/var/log/asterisk/misdn.trace [default] echocancel=yes echotraining=yes hold_allowed=yes screen=-1 presentation=-1 senddtmf=yes [isdn_call] ports=1,2,3 context=isdn_in msns=* ------------------------------------------------- Have you got any idea what is causing this and how I could get the echo training working? Thank you for your help. Jarkko
2008 Dec 19
3
Pre-routing manipulation of calls
This is concerning an Asterisk 1.4.18 server. We have approximately 70 DID numbers. Incoming calls are placed into the "incoming" context (by zapata.conf) and are routed based on the dialed number. I want to do some manipulation (CallerID name override) to all incoming calls before they are routed. I would prefer to avoid duplicating the necessary code in each DID extension stanza,