Hello,
we have an asterisk (1.4.21.2) with ZAP and mISDN channels, the mISDN are 2
incoming GSM Modems, each with 2 simcards.
No, the mISDN line one and two are fine, but when I get a call on line 3
something with the time is wrong. Timeconditions fall through to off-hours even
if the time of the call is clearly inside business hours, here a log excerpt:
[Aug 26 11:04:36] VERBOSE[3112] logger.c: Really destroying SIP dialog
'39992a2d3d4aae816ff4d5f04710e...@10.10.254.254' Method: OPTIONS
[Aug 26 11:04:37] VERBOSE[9172] logger.c: -- Executing [2...@from-pstn:1]
Set("mISDN/3-u10744", "__FROM_DID=2000") in new stack
[Aug 26 11:04:37] VERBOSE[9172] logger.c: -- Executing [2...@from-pstn:2]
GotoIf("mISDN/3-u10744", "0 ?cidok") in new stack
[Aug 26 11:04:37] VERBOSE[9172] logger.c: -- Executing [2...@from-pstn:3]
Set("mISDN/3-u10744", "CALLERID(name)=6019") in new stack
[Aug 26 11:04:37] VERBOSE[9172] logger.c: -- Executing [2...@from-pstn:4]
NoOp("mISDN/3-u10744", "CallerID is "6019" <6019>") in new stack
[Aug 26 11:04:37] VERBOSE[9172] logger.c: -- Executing [2...@from-pstn:5]
Set("mISDN/3-u10744", "__CALLINGPRES_SV=allowed_not_screened") in new stack
[Aug 26 11:04:37] VERBOSE[9172] logger.c: -- Executing [2...@from-pstn:6]
SetCallerPres("mISDN/3-u10744", "allowed_not_screened") in new stack
[Aug 26 11:04:37] VERBOSE[9172] logger.c: -- Executing [2...@from-pstn:7]
Goto("mISDN/3-u10744", "timeconditions|4|1") in new stack
[Aug 26 11:04:37] VERBOSE[9172] logger.c: -- Goto (timeconditions,4,1)
[Aug 26 11:04:37] VERBOSE[9172] logger.c: -- Executing
[...@timeconditions:1] GotoIfTime("mISDN/3-u10744",
"15:00-18:59|mon-thu|*|*?ivr-7|s|1") in new stack
[Aug 26 11:04:37] VERBOSE[9172] logger.c: -- Executing
[...@timeconditions:2] Goto("mISDN/3-u10744", "timeconditions|5|1") in new stack
[Aug 26 11:04:37] VERBOSE[9172] logger.c: -- Goto (timeconditions,5,1)
[Aug 26 11:04:37] VERBOSE[9172] logger.c: -- Executing
[...@timeconditions:1] GotoIfTime("mISDN/3-u10744",
"08:01-14:59|fri|*|*?ivr-7|s|1") in new stack
[Aug 26 11:04:37] VERBOSE[9172] logger.c: -- Executing
[...@timeconditions:2] Goto("mISDN/3-u10744", "ivr-5|s|1") in new stack
[Aug 26 11:04:37] VERBOSE[9172] logger.c: -- Goto (ivr-5,s,1)
[Aug 26 11:04:37] VERBOSE[9172] logger.c: -- Executing [...@ivr-5:1]
Set("mISDN/3-u10744", "LOOPCOUNT=0") in new stack
[Aug 26 11:04:37] VERBOSE[9172] logger.c: -- Executing [...@ivr-5:2]
Set("mISDN/3-u10744", "__DIR-CONTEXT=default") in new stack
[Aug 26 11:04:37] VERBOSE[9172] logger.c: -- Executing [...@ivr-5:3]
Set("mISDN/3-u10744", "_IVR_CONTEXT_ivr-5=") in new stack
[Aug 26 11:04:37] VERBOSE[9172] logger.c: -- Executing [...@ivr-5:4]
Set("mISDN/3-u10744", "_IVR_CONTEXT=ivr-5") in new stack
[Aug 26 11:04:37] VERBOSE[9172] logger.c: -- Executing [...@ivr-5:5]
GotoIf("mISDN/3-u10744", "0?begin") in new stack
[Aug 26 11:04:37] VERBOSE[9172] logger.c: -- Executing [...@ivr-5:6]
Answer("mISDN/3-u10744", "") in new stack
[Aug 26 11:04:37] VERBOSE[9172] logger.c: -- Executing [...@ivr-5:7]
Wait("mISDN/3-u10744", "1") in new stack
[Aug 26 11:04:38] VERBOSE[9172] logger.c: -- Executing [...@ivr-5:8]
Set("mISDN/3-u10744", "TIMEOUT(digit)=3") in new stack
[Aug 26 11:04:38] VERBOSE[9172] logger.c: -- Digit timeout set to 3
[Aug 26 11:04:38] VERBOSE[9172] logger.c: -- Executing [...@ivr-5:9]
Set("mISDN/3-u10744", "TIMEOUT(response)=12") in new stack
[Aug 26 11:04:38] VERBOSE[9172] logger.c: -- Response timeout set to 12
[Aug 26 11:04:38] VERBOSE[9172] logger.c: -- Executing [...@ivr-5:10]
BackGround("mISDN/3-u10744", "custom/Cerrado_Normal_2") in new stack
As you can see, it's clearly not off-hours but the line is treated as such, so
I am confused, where does the time come from? Is it not the current computer
system time?
I also checked and the only nominater is mISDN/3 and mISDN/4, served on
different threads etc. Other calls (mISDN/1, mISDN/2, Zaps) all behave fine.
Does anyone have an iDea what's going on? I requested to have the GSM modems
resetted but it seems to have no effect!
for comparision, an mISDN/2 channel:
[Aug 26 09:56:30] VERBOSE[8890] logger.c: -- Executing [...@ext-did:7]
SetCallerPres("mISDN/2-u10712", "allowed_not_screened") in new stack
[Aug 26 09:56:30] VERBOSE[8890] logger.c: -- Executing [...@ext-did:8]
Goto("mISDN/2-u10712", "timeconditions|3|1") in new stack
[Aug 26 09:56:30] VERBOSE[8890] logger.c: -- Goto (timeconditions,3,1)
[Aug 26 09:56:30] VERBOSE[8890] logger.c: -- Executing
[...@timeconditions:1] GotoIfTime("mISDN/2-u10712",
"08:00-12:59|mon-thu|*|*?ivr-7|s|1") in new stack
[Aug 26 09:56:30] VERBOSE[8890] logger.c: -- Goto (ivr-7,s,1)
[Aug 26 09:56:30] VERBOSE[8890] logger.c: -- Executing [...@ivr-7:1]
Set("mISDN/2-u10712", "LOOPCOUNT=0") in new stack
[Aug 26 09:56:30] VERBOSE[8890] logger.c: -- Executing [...@ivr-7:2]
Set("mISDN/2-u10712", "__DIR-CONTEXT=default") in new stack
-
RunSolutions
Open Source It Consulting
-
Email: r...@runsolutions.com
Parc Bit - Centro Empresarial Son Espanyol
Edificio Estel - Local 3D
07121 - Palma de Mallorca
Baleares
----- Mensaje original -----
> Send asterisk-users mailing list submissions to
> asterisk-users@lists.digium.com
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://lists.digium.com/mailman/listinfo/asterisk-users
> or, via email, send a message with subject or body 'help' to
> asterisk-users-requ...@lists.digium.com
>
> You can reach the person managing the list at
> asterisk-users-ow...@lists.digium.com
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of asterisk-users digest..."
>
> Today's Topics:
>
> 1. Re: Dahdi install gone wrong (A J Stiles)
> 2. AEL - what is error: ael.flex:647 ael_yylex: Unhandled
> char(s): (Zeeshan Zakaria)
> 3. Re: Should I move to 1.6 or 1.8, or stay with 1.4?
> (Zeeshan Zakaria)
> 4. Re: AEL - what is error: ael.flex:647 ael_yylex:Unhandled
> char(s): (Danny Nicholas)
> 5. Re: AEL - what is error: ael.flex:647 ael_yylex:Unhandled
> char(s): (Zeeshan Zakaria)
> 6. Re: AEL - what is error: ael.flex:647 ael_yylex:Unhandled
> char(s): (Watkins, Bradley)
> 7. Re: AEL - what is error: ael.flex:647 ael_yylex:Unhandled
> char(s): (Zeeshan Zakaria)
> 8. Re: Should I move to 1.6 or 1.8, or stay with 1.4? (Leif Madsen)
> 9. Re: How to debug this specific issue? (Steve Davies)
> 10. Re: Should I move to 1.6 or 1.8, or stay with 1.4?
> (Zeeshan Zakaria)
>
> _______________________________________________
> --Bandwidth and Colocation Provided by http://www.api-digital.com--
>
> AstriCon 2010 - October 26-28 Washington, DC
> Register Now: http://www.astricon.net/
>
> asterisk-users mailing list
> To UNSUBSCRIBE or update options visit:
> http://lists.digium.com/mailman/listinfo/asterisk-users
--
_____________________________________________________________________
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
New to Asterisk? Join us for a live introductory webinar every Thurs:
http://www.asterisk.org/hello
asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users
