Thanks for the suggestion Tzafrir. I ran 2 sets of calls this morning with
this result:
Call set 1 was to dahdi/1c/ww5551212 - this set showed the dadhi answer
event when I actually picked up, but no polarity event.
Call set 2 was to dahdi/1/ww/5551212 - this set showed the dahdi answer
event immediately upon dialing; no polarity event either.
CLI settings were verbose 17, debug 3.
Here is CLI output
Connected to Asterisk 1.4.26.1 currently running on debsphoned (pid = 22427)
Verbosity is at least 17
Core debug is at least 3
Really destroying SIP dialog
'5954caba29c79bb14d192d0f3f381...@192.168.23.95' Me
thod: OPTIONS
Really destroying SIP dialog
'4202608b0d07599d62cd5c6a1bf20...@192.168.23.95' Me
thod: NOTIFY
Really destroying SIP dialog
'2e441c19715c75ff21ab67d748110...@192.168.23.95' Me
thod: OPTIONS
Really destroying SIP dialog
'02f32b3068e0b6ca42a6a6790a1bb...@192.168.23.95' Me
thod: NOTIFY
Really destroying SIP dialog
'4da2eca97cce77492854295e7fab0...@192.168.23.95' Method: OPTIONS
Really destroying SIP dialog
'22af4f885c9466ab35e931655fb0c...@192.168.23.95' Method: NOTIFY
Really destroying SIP dialog
'5ccf5fd6153b006d573d60f86444b...@192.168.23.95' Method: OPTIONS
Really destroying SIP dialog
'0f09cfe3006645e22211adb96a22b...@192.168.23.95' Method: NOTIFY
Really destroying SIP dialog
'5c1ccab644fd818007a427f911bfe...@192.168.23.95' Method: OPTIONS
Really destroying SIP dialog
'63271d0118de7d265cf288443078e...@192.168.23.95' Method: NOTIFY
Really destroying SIP dialog
'50e6bb5c16ae921a1d5db14e2af25...@192.168.23.95' Method: OPTIONS
Really destroying SIP dialog
'6cdd73f256e78acd023f2523711e5...@192.168.23.95' Method: NOTIFY
Really destroying SIP dialog
'2ac6b712601d6c784f17a57961259...@192.168.23.95' Method: OPTIONS
Really destroying SIP dialog
'42faf9990958452d1ac67a9e53110...@192.168.23.95' Method: NOTIFY
-- Attempting call on DAHDI/1c/wwww5551212 for s...@mickey:1 (Retry 1)
-- Attempting call on DAHDI/1c/wwww5551212 for s...@mickey:1 (Retry 1)
[Aug 28 07:12:06] NOTICE[18236]: channel.c:3220 __ast_request_and_dial:
Unable to request channel DAHDI/1c/wwww5551212
[Aug 28 07:12:06] NOTICE[18236]: pbx_spool.c:356 attempt_thread: Call failed
to go through, reason (0) Call Failure (not BUSY, and not NO_ANSWER, maybe
Circuit busy or down?)
Really destroying SIP dialog
'3bccf43c160374fd2de5db6c1582a...@192.168.23.95' Method: OPTIONS
Really destroying SIP dialog
'314d2892572b432d7cb4672573614...@192.168.23.95' Method: NOTIFY
> Channel DAHDI/1-1 was answered.
-- Executing [...@mickey:1] Answer("DAHDI/1-1", "") in new stack
-- Executing [...@mickey:2] GotoIf("DAHDI/1-1", "1?start") in new stack
-- Goto (mickey,s,5)
-- Executing [...@mickey:5] BackGround("DAHDI/1-1",
"telbank/firstwelcome") in new stack
-- <DAHDI/1-1> Playing 'telbank/firstwelcome' (language 'en')
-- Executing [...@mickey:6] BackGround("DAHDI/1-1", "telbank/important")
in new stack
-- <DAHDI/1-1> Playing 'telbank/important' (language 'en')
-- Executing [...@mickey:7] WaitExten("DAHDI/1-1", "5|m") in new stack
-- Started music on hold, class 'default', on channel 'DAHDI/1-1'
-- Stopped music on hold on DAHDI/1-1
== CDR updated on DAHDI/1-1
-- Executing [...@mickey:1] ForkCDR("DAHDI/1-1",
"v|s(fullcmd=/tmp/call_18205_1)") in new stack
-- Executing [...@mickey:2] BackGround("DAHDI/1-1", "/tmp/call_18205_1")
in new stack
-- <DAHDI/1-1> Playing '/tmp/call_18205_1' (language 'en')
Really destroying SIP dialog
'6da7b29262084bda3619b23936f51...@192.168.23.95' Method: OPTIONS
Really destroying SIP dialog
'11bafb7d6c40d2972b0b644630e80...@192.168.23.95' Method: NOTIFY
[Aug 28 07:13:02] NOTICE[22452]: pbx_spool.c:255 apply_outgoing: Syntax
error at line 1 of /var/spool/asterisk/outgoing/.1251461525.outgoing.swp
[Aug 28 07:13:02] WARNING[22452]: pbx_spool.c:260 apply_outgoing: At least
one of app or extension must be specified, along with tech and dest in file
/var/spool/asterisk/outgoing/.1251461525.outgoing.swp
[Aug 28 07:13:02] WARNING[22452]: pbx_spool.c:427 scan_service: Invalid file
contents in /var/spool/asterisk/outgoing/.1251461525.outgoing.swp, deleting
[Aug 28 07:13:02] WARNING[22452]: pbx_spool.c:482 scan_thread: Failed to
scan service '/var/spool/asterisk/outgoing/.1251461525.outgoing.swp'
-- Executing [...@mickey:3] BackGround("DAHDI/1-1", "telbank/repeatmsg")
in new stack
-- <DAHDI/1-1> Playing 'telbank/repeatmsg' (language 'en')
-- Attempting call on DAHDI/1/wwww5551212 for s...@mickey:1 (Retry 2)
[Aug 28 07:13:10] NOTICE[18248]: channel.c:3220 __ast_request_and_dial:
Unable to request channel DAHDI/1/wwww5551212
[Aug 28 07:13:10] NOTICE[18248]: pbx_spool.c:356 attempt_thread: Call failed
to go through, reason (0) Call Failure (not BUSY, and not NO_ANSWER, maybe
Circuit busy or down?)
-- Executing [...@mickey:4] WaitExten("DAHDI/1-1", "10|m") in new stack
-- Started music on hold, class 'default', on channel 'DAHDI/1-1'
[Aug 28 07:13:13] NOTICE[22452]: pbx_spool.c:255 apply_outgoing: Syntax
error at line 1 of /var/spool/asterisk/outgoing/.1251461526.outgoing.swp
[Aug 28 07:13:13] WARNING[22452]: pbx_spool.c:260 apply_outgoing: At least
one of app or extension must be specified, along with tech and dest in file
/var/spool/asterisk/outgoing/.1251461526.outgoing.swp
[Aug 28 07:13:13] WARNING[22452]: pbx_spool.c:427 scan_service: Invalid file
contents in /var/spool/asterisk/outgoing/.1251461526.outgoing.swp, deleting
[Aug 28 07:13:13] WARNING[22452]: pbx_spool.c:482 scan_thread: Failed to
scan service '/var/spool/asterisk/outgoing/.1251461526.outgoing.swp'
Really destroying SIP dialog
'4228bd9a2d7de69f1939558627067...@192.168.23.95' Method: OPTIONS
Really destroying SIP dialog
'48075ec437be8ee86c73408c28cc1...@192.168.23.95' Method: NOTIFY
-- Timeout on DAHDI/1-1, continuing...
-- Stopped music on hold on DAHDI/1-1
-- Executing [...@mickey:5] Playback("DAHDI/1-1", "vm-goodbye") in new
stack
-- <DAHDI/1-1> Playing 'vm-goodbye' (language 'en')
-- Executing [...@mickey:6] Hangup("DAHDI/1-1", "") in new stack
== Spawn extension (mickey, 1, 6) exited non-zero on 'DAHDI/1-1'
-- Hungup 'DAHDI/1-1'
[Aug 28 07:13:22] NOTICE[18235]: pbx_spool.c:366 attempt_thread: Call
completed to DAHDI/1c/wwww5551212
Really destroying SIP dialog
'58fa168e7617661043ad9830439cc...@192.168.23.95' Method: OPTIONS
Really destroying SIP dialog
'423474333a88bc1f5dcf5b8b6be8f...@192.168.23.95' Method: NOTIFY
Really destroying SIP dialog
'43b1e30740ab19a72ec2a7373de9a...@192.168.23.95' Method: OPTIONS
[Aug 28 07:14:17] NOTICE[22452]: pbx_spool.c:255 apply_outgoing: Syntax
error at line 1 of /var/spool/asterisk/outgoing/.1251461525.outgoing.swp
[Aug 28 07:14:17] WARNING[22452]: pbx_spool.c:260 apply_outgoing: At least
one of app or extension must be specified, along with tech and dest in file
/var/spool/asterisk/outgoing/.1251461525.outgoing.swp
[Aug 28 07:14:17] WARNING[22452]: pbx_spool.c:427 scan_service: Invalid file
contents in /var/spool/asterisk/outgoing/.1251461525.outgoing.swp, deleting
[Aug 28 07:14:17] WARNING[22452]: pbx_spool.c:482 scan_thread: Failed to
scan service '/var/spool/asterisk/outgoing/.1251461525.outgoing.swp'
Really destroying SIP dialog
'23c73cf32cf9626e1751218f7d2e8...@192.168.23.95' Method: NOTIFY
[Aug 28 07:14:45] NOTICE[22452]: pbx_spool.c:255 apply_outgoing: Syntax
error at line 1 of /var/spool/asterisk/outgoing/.1251461525.outgoing.swp
[Aug 28 07:14:45] WARNING[22452]: pbx_spool.c:260 apply_outgoing: At least
one of app or extension must be specified, along with tech and dest in file
/var/spool/asterisk/outgoing/.1251461525.outgoing.swp
[Aug 28 07:14:45] WARNING[22452]: pbx_spool.c:427 scan_service: Invalid file
contents in /var/spool/asterisk/outgoing/.1251461525.outgoing.swp, deleting
[Aug 28 07:14:45] WARNING[22452]: pbx_spool.c:482 scan_thread: Failed to
scan service '/var/spool/asterisk/outgoing/.1251461525.outgoing.swp'
Really destroying SIP dialog
'1acdd99941b909773bb53ce570223...@192.168.23.95' Method: OPTIONS
Really destroying SIP dialog
'615fe52153a8397c5b73394208d11...@192.168.23.95' Method: NOTIFY
-- Attempting call on DAHDI/1/ww5551212 for s...@mickey:1 (Retry 3)
Really destroying SIP dialog
'0a8b85bb66406b521920941648b52...@192.168.23.95' Method: OPTIONS
> Channel DAHDI/1-1 was answered.
-- Executing [...@mickey:1] Answer("DAHDI/1-1", "") in new stack
-- Executing [...@mickey:2] GotoIf("DAHDI/1-1", "1?start") in new stack
-- Goto (mickey,s,5)
-- Executing [...@mickey:5] BackGround("DAHDI/1-1",
"telbank/firstwelcome") in new stack
-- <DAHDI/1-1> Playing 'telbank/firstwelcome' (language 'en')
-- Executing [...@mickey:6] BackGround("DAHDI/1-1", "telbank/important")
in new stack
-- <DAHDI/1-1> Playing 'telbank/important' (language 'en')
Really destroying SIP dialog
'491fddfc375016185c7560f2256d3...@192.168.23.95' Method: NOTIFY
-- Executing [...@mickey:7] WaitExten("DAHDI/1-1", "5|m") in new stack
-- Started music on hold, class 'default', on channel 'DAHDI/1-1'
-- Timeout on DAHDI/1-1, continuing...
-- Stopped music on hold on DAHDI/1-1
-- Executing [...@mickey:8] AGI("DAHDI/1-1", "plusone.agi|IVRTRY|") in new
stack
-- Launched AGI Script /var/lib/asterisk/agi-bin/plusone.agi
-- AGI Script plusone.agi completed, returning 0
-- Executing [...@mickey:9] Verbose("DAHDI/1-1", "Try 1") in new stack
Try 1
-- Executing [...@mickey:10] GotoIf("DAHDI/1-1", "1?mickey|s|start") in
new stack
-- Goto (mickey,s,5)
-- Executing [...@mickey:5] BackGround("DAHDI/1-1",
"telbank/firstwelcome") in new stack
-- <DAHDI/1-1> Playing 'telbank/firstwelcome' (language 'en')
-- Hungup 'DAHDI/1-1'
[Aug 28 07:15:38] NOTICE[18287]: pbx_spool.c:366 attempt_thread: Call
completed to DAHDI/1/ww5551212
Any other ideas??
-----Original Message-----
From: asterisk-users-boun...@lists.digium.com
[mailto:asterisk-users-boun...@lists.digium.com] On Behalf Of Tzafrir Cohen
Sent: Thursday, August 27, 2009 12:13 PM
To: Asterisk Users Mailing List - Non-Commercial Discussion
Subject: Re: [asterisk-users] POTS supervision with DAHDI in 1.4 releases
For the benefit of our readers, I will convert this back to a more
readable in-line replies format:
On Thu, Aug 27, 2009 at 11:45:10AM -0500, Danny Nicholas wrote:
> On Thursday, August 27, 2009 11:36 AM, Tzafrir Cohen wrote:
> >
> > Has this actually ever worked?
>
> yes it did or I wouldn't be chasing this dog.
> >
> > Do you use the same zapata.conf / chan_dahdi.conf ?
>
> 2 - no, but I'm going to try and regress dahdi.conf to match Zapata.conf
>
> > Do you have 'answeronpolarityswitch = yes' ?
>
> 3 - yes.
One thing to test: do you still get a polarity event at answer time?
You should get a debug-level message from DAHDI for each event. And one
or two more debug messages for polarity reversal events.
--
Tzafrir Cohen
icq#16849755 jabber:tzafrir.co...@xorcom.com
+972-50-7952406 mailto:tzafrir.co...@xorcom.com
http://www.xorcom.com iax:gu...@local.xorcom.com/tzafrir
_______________________________________________
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
AstriCon 2009 - October 13 - 15 Phoenix, Arizona
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 --
AstriCon 2009 - October 13 - 15 Phoenix, Arizona
Register Now: http://www.astricon.net
asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users
