<![CDATA[Don't show status on DAHDI Extensions]]>I have trouble with status of extensions on DAHDI.
I set up much extensions in elastix as DAHDI devices, such as "DAHDI/i9/19", but corresponding buttons don't show status, when I make call to or from extensions.
However status of DAHDI trunks work well, that is, I see on trunks channels and phone numbers.

]]>http://localhost:4567/topic/981/don-t-show-status-on-dahdi-extensionsRSS for NodeTue, 27 Oct 2026 05:47:06 GMTWed, 14 Dec 2011 06:16:36 GMT60<![CDATA[Reply to Don't show status on DAHDI Extensions on Wed, 18 Jan 2012 02:36:41 GMT]]>well, a working but maybe ugly solution. I will work on a fix for the next fop2 release so you can avoid using that proxy.

]]>http://localhost:4567/post/4292http://localhost:4567/post/4292Wed, 18 Jan 2012 02:36:41 GMT<![CDATA[Reply to Don't show status on DAHDI Extensions on Tue, 17 Jan 2012 07:38:10 GMT]]>The problem was solved by changing "DAHDI/i9" on "SIP" via proxy between FOP2 server and asterisk :shock:

]]>http://localhost:4567/post/4291http://localhost:4567/post/4291Tue, 17 Jan 2012 07:38:10 GMT<![CDATA[Reply to Don't show status on DAHDI Extensions on Mon, 26 Dec 2011 04:52:47 GMT]]>I found, why status doesn't showed:

when I call from SIP phone, registered in FOP2 as SIP/155 in log this string appears:

GET CHANNEL input (SIP/155-00006e9a) - output (SIP/155)

and status of button SIP/155 is shown

but when I call from phone, registered in FOP2 as DAHDI/i9/55 in log this:

GET CHANNEL input (DAHDI/i9/55-71ca) - output (DAHDI/I9)

although must be some, like this

GET CHANNEL input (DAHDI/i9/55-71ca) - output (DAHDI/i9/55)
]]>http://localhost:4567/post/4290http://localhost:4567/post/4290Mon, 26 Dec 2011 04:52:47 GMT<![CDATA[Reply to Don't show status on DAHDI Extensions on Fri, 23 Dec 2011 11:42:41 GMT]]>Yes, I did. I have to check/test still.

]]>http://localhost:4567/post/4289http://localhost:4567/post/4289Fri, 23 Dec 2011 11:42:41 GMT<![CDATA[Reply to Don't show status on DAHDI Extensions on Fri, 23 Dec 2011 05:22:28 GMT]]>I sent log to you, are you received it?

]]>http://localhost:4567/post/4288http://localhost:4567/post/4288Fri, 23 Dec 2011 05:22:28 GMT<![CDATA[Reply to Don't show status on DAHDI Extensions on Fri, 16 Dec 2011 11:06:29 GMT]]>The session id is normal and it is removed by fop2, so the device names are the same. If they are advertised as such in AMI, then it must work... (edited) but perhaps the double slash is troublesome. Try to capture events from AMI using fop2_server in debug level 1 when you make a call with that extension and send the capture to me so I can replay it locally

service fop2 stop
cd /usr/local/fop2
script capture.log
./fop2_server -X 1

(do your call)

ctrl-C
exit

(send me the capture.log file via private email/post)

]]>http://localhost:4567/post/4287http://localhost:4567/post/4287Fri, 16 Dec 2011 11:06:29 GMT<![CDATA[Reply to Don't show status on DAHDI Extensions on Fri, 16 Dec 2011 03:07:26 GMT]]>autoconfiguration sets such device names:

[DAHDI/i9/55]
type=extension
extension=55
...
bun, when I call from 55 to 591600, the command asterisk -rx "core show channels" shows
...
DAHDI/i9/55-40a3 s@macro-dialout-trun Ring Dial(DAHDI/g2/591600,300,T)
...
and number -40a3 changes from call to call

]]>http://localhost:4567/post/4286http://localhost:4567/post/4286Fri, 16 Dec 2011 03:07:26 GMT<![CDATA[Reply to Don't show status on DAHDI Extensions on Thu, 15 Dec 2011 18:15:44 GMT]]>Look at how the autoconfiguration is setting the device names ( run /usr/local/fop2/autoconfig-buttons-freepbx.sh ), and compare those names with active channel names when you are on a call ( asterisk -rx "core show channels" ). If the device names are different, you won' t see status, you have to use in fop2 the same device name as an active channel. If the autoconfiguration fails to guess the number, you will have to create some manual configuration fro your dahdi extensions.

]]>http://localhost:4567/post/4285http://localhost:4567/post/4285Thu, 15 Dec 2011 18:15:44 GMT