VoIP Mailing List Archives
Mailing list archives for the VoIP community |
|
| View previous topic :: View next topic |
| Author |
Message |
greg at gregandeva.net
Guest
|
 Posted: Sat Dec 05, 2015 2:18 pm Post subject: [asterisk-users] after upgrade buttons on Dahdi phones don't |
 |
|
On Fri, Dec 4, 2015 at 12:50 PM, Greg Woods <greg@gregandeva.net (greg@gregandeva.net)> wrote:
| Quote: | the first numeric button press generates a fast busy. Inbound calls to the Dahdi phones work just fine.
|
I did some poking around and figured out that I could run something like "asterisk -r -d -d -d" and get more detailed debugging info. That produced this:
[Dec 5 08:16:50] DEBUG[28802][C-0000000b] sig_analog.c: waitfordigit returned '
8' (56), timeout = 0
[Dec 5 08:16:50] DEBUG[28802][C-0000000b] sig_analog.c: Can't match 8 from '400
2' in context from-internal
OK, so the fast busy comes as soon as asterisk can see that there is no extension that starts with '8'. The dahdi-channels.conf file does declare from-internal as the context for the channels those phones are connected to. And there is no from-internal context declared anywhere. So this makes sense.
What DOESN'T make sense is that this configuration *ever* worked. But it did, until the recent upgrade. The fix was to change "from-internal" to "internal" in dahdi-channels.conf . So that just leaves the question of how this configuration ever worked at all.
--Greg |
|
| Back to top |
|
 |
mjordan at digium.com
Guest
|
| Posted: Sun Dec 06, 2015 9:51 pm Post subject: [asterisk-users] after upgrade buttons on Dahdi phones don't |
|
|
On Sat, Dec 5, 2015 at 1:17 PM, Greg Woods <greg@gregandeva.net (greg@gregandeva.net)> wrote:
| Quote: |
On Fri, Dec 4, 2015 at 12:50 PM, Greg Woods <greg@gregandeva.net (greg@gregandeva.net)> wrote:
| Quote: | the first numeric button press generates a fast busy. Inbound calls to the Dahdi phones work just fine.
|
I did some poking around and figured out that I could run something like "asterisk -r -d -d -d" and get more detailed debugging info. That produced this:
[Dec 5 08:16:50] DEBUG[28802][C-0000000b] sig_analog.c: waitfordigit returned '
8' (56), timeout = 0
[Dec 5 08:16:50] DEBUG[28802][C-0000000b] sig_analog.c: Can't match 8 from '400
2' in context from-internal
OK, so the fast busy comes as soon as asterisk can see that there is no extension that starts with '8'. The dahdi-channels.conf file does declare from-internal as the context for the channels those phones are connected to. And there is no from-internal context declared anywhere. So this makes sense.
What DOESN'T make sense is that this configuration *ever* worked. But it did, until the recent upgrade. The fix was to change "from-internal" to "internal" in dahdi-channels.conf . So that just leaves the question of how this configuration ever worked at all.
|
Sounds like you may have hit step 6...
http://plasmasturm.org/log/6debug/
--
Matthew Jordan
Digium, Inc. | Director of Technology
445 Jan Davis Drive NW - Huntsville, AL 35806 - USA
Check us out at: http://digium.com & http://asterisk.org |
|
| Back to top |
|
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
Powered by phpBB © 2001, 2005 phpBB Group
|
Search
