Re: [asterisk-users] 2 Problems with 1.6.2
Have you solved this issue? When I restart the machines I can't make an outgoing DAHDI call until I get an incoming call on that same line. -Original Message- From: asterisk-users-boun...@lists.digium.com [mailto:asterisk-users-boun...@lists.digium.com] On Behalf Of Ira Sent: viernes, 17 de julio de 2009 07:47 p.m. To: Asterisk Users Mailing List - Non-Commercial Discussion Subject: Re: [asterisk-users] 2 Problems with 1.6.2 At 01:09 PM 7/17/2009, you wrote: Sorry, that's the most frequent problem that people have with MWI in 1.6, so it was worth mentioning. I would suggest that you file a bug report on https://issues.asterisk.org. It would be helpful if you would include SIP debug output for both a machine that is working, as well as a machine that is not working. So I'd be more than happy to file a bug report and include all the SIP debug anyone might need but it's been so many years since I did it that I've no idea how anymore. So I grabbed a cordless handset, sat down at the console, typed sip set debug ip 192.xxx.xxx.xx and called that voicemail box to leave a message. The instant I hung up a notify message was sent to my phone, but the red light did not come on. If you remind me the how, I'll grab that message and post it here. Thanks so much for the help. Ira ___ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users Checked by AVG - www.avg.com Version: 8.5.375 / Virus Database: 270.13.18/2243 - Release Date: 07/17/09 18:00:00 ___ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] 2 Problems with 1.6.2
Sebastian wrote: Have you solved this issue? When I restart the machines I can't make an outgoing DAHDI call until I get an incoming call on that same line. -Original Message- From: asterisk-users-boun...@lists.digium.com [mailto:asterisk-users-boun...@lists.digium.com] On Behalf Of Ira Sent: viernes, 17 de julio de 2009 07:47 p.m. To: Asterisk Users Mailing List - Non-Commercial Discussion Subject: Re: [asterisk-users] 2 Problems with 1.6.2 At 01:09 PM 7/17/2009, you wrote: Sorry, that's the most frequent problem that people have with MWI in 1.6, so it was worth mentioning. I would suggest that you file a bug report on https://issues.asterisk.org. It would be helpful if you would include SIP debug output for both a machine that is working, as well as a machine that is not working. So I'd be more than happy to file a bug report and include all the SIP debug anyone might need but it's been so many years since I did it that I've no idea how anymore. So I grabbed a cordless handset, sat down at the console, typed sip set debug ip 192.xxx.xxx.xx and called that voicemail box to leave a message. The instant I hung up a notify message was sent to my phone, but the red light did not come on. If you remind me the how, I'll grab that message and post it here. Thanks so much for the help. Ira ___ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users Checked by AVG - www.avg.com Version: 8.5.375 / Virus Database: 270.13.18/2243 - Release Date: 07/17/09 18:00:00 ___ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users I have the same issue == https://issues.asterisk.org/print_bug_page.php?bug_id=14577 ___ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] 2 Problems with 1.6.2
At 03:30 PM 7/20/2009, you wrote: Have you solved this issue? When I restart the machines I can't make an outgoing DAHDI call until I get an incoming call on that same line. I've not and from the responses it's sounds like a known problem Ira ___ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] 2 Problems with 1.6.2
At 07:53 PM 7/16/2009, you wrote: I've been using 1.6.2 for a few weeks and I've managed to get almost everything working perfectly. I can't get the MWI indicators on my Aastra phones to work properly, the did in all the versions of 1.2 I used up to the most recent one, but now they work correctly right after the phone is re-started and rarely thereafter. it's as if something changed in the way the MWI is handled and I can't figure out what the difference is or what I've done wrong. It would probably be best for you to read UPGRADE-1.4.txt, UPGRADE-1.6.txt, and UPGRADE.txt, as the issue with MWI is explained in there and what you can do to fix it. The second file contains the explanation, although you would be well advised to read all three. So, I read for the third time or so as asked and all I can see is that talks about MWI is I should add something to scan the VM folders if I'm messing with Voicemail outside the normal settings. I'm not, but I added it anyway just to see if it would help. It didn't. I've searched voip-info for MWI information, but either I'm just really being stupid or something changed. In 1.2 just adding the line mailbox=102,104 was all it took to make it work on the Aastra 480i-CTs we use. I really tried to figure this out without asking here, but it's been 2 weeks and I'm still failing. Ira ___ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] 2 Problems with 1.6.2
In some cases MWI is referred to (perhaps incorrectly) as BLF. Try searching on that. -Original Message- From: asterisk-users-boun...@lists.digium.com [mailto:asterisk-users-boun...@lists.digium.com] On Behalf Of Ira Sent: Friday, July 17, 2009 1:26 PM To: Asterisk Users Mailing List - Non-Commercial Discussion Subject: Re: [asterisk-users] 2 Problems with 1.6.2 At 07:53 PM 7/16/2009, you wrote: I've been using 1.6.2 for a few weeks and I've managed to get almost everything working perfectly. I can't get the MWI indicators on my Aastra phones to work properly, the did in all the versions of 1.2 I used up to the most recent one, but now they work correctly right after the phone is re-started and rarely thereafter. it's as if something changed in the way the MWI is handled and I can't figure out what the difference is or what I've done wrong. It would probably be best for you to read UPGRADE-1.4.txt, UPGRADE-1.6.txt, and UPGRADE.txt, as the issue with MWI is explained in there and what you can do to fix it. The second file contains the explanation, although you would be well advised to read all three. So, I read for the third time or so as asked and all I can see is that talks about MWI is I should add something to scan the VM folders if I'm messing with Voicemail outside the normal settings. I'm not, but I added it anyway just to see if it would help. It didn't. I've searched voip-info for MWI information, but either I'm just really being stupid or something changed. In 1.2 just adding the line mailbox=102,104 was all it took to make it work on the Aastra 480i-CTs we use. I really tried to figure this out without asking here, but it's been 2 weeks and I'm still failing. Ira ___ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- 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 -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] 2 Problems with 1.6.2
On Fri, 2009-07-17 at 13:30 -0500, Danny Nicholas wrote: In some cases MWI is referred to (perhaps incorrectly) as BLF. Try searching on that. MWI and BLF are two separate and distinct items. The only thing they have in common is that they both deal with lighting up little lights on a handset. MWI is Message Waiting Indication, where Asterisk sends a SIP NOTIFY message to a to a phone to let the phone know that there is new voicemail in the mailbox corresponding to that SIP device. (You set the corresponding mailbox by setting mailbox=1...@default in the peer or friend definition in sip.conf, where 1234 is the mailbox, and default is the voicemail context or section name in voicemail.conf.) BLF stands for Busy Lamp Field. BLFs are used for *all kinds* of different things, but most often they're used for monitoring extension state of another extension. To make this work, you create a dialplan hint for the device in question to map an extension state to a device state and then make sure that call limits are enforced in the SIP channel driver (so that it keeps track of device state. The phone with the BLF will then SUBSCRIBE to the status of the hint, and then when the extension state changes, Asterisk will send a SIP NOTIFY to the phone to let it know that the subscribed hint has changed states. I know you're only trying to help, but please don't muddy the water by telling people that MWI and BLFs are the same thing. -- Jared Smith Training Manager Digium, Inc. ___ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] 2 Problems with 1.6.2
At 11:30 AM 7/17/2009, you wrote: In some cases MWI is referred to (perhaps incorrectly) as BLF. Try searching on that. Thanks, I have BLF set up and working, it's MWI that's messed up. Ira ___ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] 2 Problems with 1.6.2
On Friday 17 July 2009 13:26:20 Ira wrote: At 07:53 PM 7/16/2009, you wrote: I've been using 1.6.2 for a few weeks and I've managed to get almost everything working perfectly. I can't get the MWI indicators on my Aastra phones to work properly, the did in all the versions of 1.2 I used up to the most recent one, but now they work correctly right after the phone is re-started and rarely thereafter. it's as if something changed in the way the MWI is handled and I can't figure out what the difference is or what I've done wrong. It would probably be best for you to read UPGRADE-1.4.txt, UPGRADE-1.6.txt, and UPGRADE.txt, as the issue with MWI is explained in there and what you can do to fix it. The second file contains the explanation, although you would be well advised to read all three. So, I read for the third time or so as asked and all I can see is that talks about MWI is I should add something to scan the VM folders if I'm messing with Voicemail outside the normal settings. I'm not, but I added it anyway just to see if it would help. It didn't. I've searched voip-info for MWI information, but either I'm just really being stupid or something changed. In 1.2 just adding the line mailbox=102,104 was all it took to make it work on the Aastra 480i-CTs we use. I really tried to figure this out without asking here, but it's been 2 weeks and I'm still failing. Sorry, that's the most frequent problem that people have with MWI in 1.6, so it was worth mentioning. I would suggest that you file a bug report on https://issues.asterisk.org. It would be helpful if you would include SIP debug output for both a machine that is working, as well as a machine that is not working. -- Tilghman Teryl with Peter, Cottontail, Midnight, Thumper, Johnny (bunnies) and Harry, BB, George (dogs) ___ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] 2 Problems with 1.6.2
Just a shot in the dark, but you say the MWI works right after an asterisk restart and not very well/long after? This could be a registration issue. If you do a sip reload, does MWI start working again for a while? -Original Message- From: asterisk-users-boun...@lists.digium.com [mailto:asterisk-users-boun...@lists.digium.com] On Behalf Of Tilghman Lesher Sent: Friday, July 17, 2009 3:09 PM To: Asterisk Users Mailing List - Non-Commercial Discussion Subject: Re: [asterisk-users] 2 Problems with 1.6.2 On Friday 17 July 2009 13:26:20 Ira wrote: At 07:53 PM 7/16/2009, you wrote: I've been using 1.6.2 for a few weeks and I've managed to get almost everything working perfectly. I can't get the MWI indicators on my Aastra phones to work properly, the did in all the versions of 1.2 I used up to the most recent one, but now they work correctly right after the phone is re-started and rarely thereafter. it's as if something changed in the way the MWI is handled and I can't figure out what the difference is or what I've done wrong. It would probably be best for you to read UPGRADE-1.4.txt, UPGRADE-1.6.txt, and UPGRADE.txt, as the issue with MWI is explained in there and what you can do to fix it. The second file contains the explanation, although you would be well advised to read all three. So, I read for the third time or so as asked and all I can see is that talks about MWI is I should add something to scan the VM folders if I'm messing with Voicemail outside the normal settings. I'm not, but I added it anyway just to see if it would help. It didn't. I've searched voip-info for MWI information, but either I'm just really being stupid or something changed. In 1.2 just adding the line mailbox=102,104 was all it took to make it work on the Aastra 480i-CTs we use. I really tried to figure this out without asking here, but it's been 2 weeks and I'm still failing. Sorry, that's the most frequent problem that people have with MWI in 1.6, so it was worth mentioning. I would suggest that you file a bug report on https://issues.asterisk.org. It would be helpful if you would include SIP debug output for both a machine that is working, as well as a machine that is not working. -- Tilghman Teryl with Peter, Cottontail, Midnight, Thumper, Johnny (bunnies) and Harry, BB, George (dogs) ___ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- 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 -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] 2 Problems with 1.6.2
On Fri, 2009-07-17 at 11:26 -0700, Ira wrote: I've searched voip-info for MWI information, but either I'm just really being stupid or something changed. In 1.2 just adding the line mailbox=102,104 was all it took to make it work on the Aastra 480i-CTs we use. I really tried to figure this out without asking here, but it's been 2 weeks and I'm still failing. Have you tried mailbox=...@default? It appears as though you need to specify a voicemail context. -- Jared Smith Training Manager Digium, Inc. ___ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] 2 Problems with 1.6.2
At 01:55 PM 7/17/2009, you wrote: 480i-CTs we use. I really tried to figure this out without asking here, but it's been 2 weeks and I'm still failing. Have you tried mailbox=...@default? It appears as though you need to specify a voicemail context. I did that but it didn't seem to make a difference. It indicates in places that it shouldn't be necessary if they are in the default context. Ira ___ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] 2 Problems with 1.6.2
At 01:15 PM 7/17/2009, you wrote: Just a shot in the dark, but you say the MWI works right after an asterisk restart and not very well/long after? This could be a registration issue. If you do a sip reload, does MWI start working again for a while? A slight correction, it works right after a phone restart, not after an Asterisk re-start. As if the phone can ask and get the correct information, but I've done something that's stopping Asterisk from pushing it to the phone. Ira ___ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] 2 Problems with 1.6.2
At 01:09 PM 7/17/2009, you wrote: Sorry, that's the most frequent problem that people have with MWI in 1.6, so it was worth mentioning. I would suggest that you file a bug report on https://issues.asterisk.org. It would be helpful if you would include SIP debug output for both a machine that is working, as well as a machine that is not working. No problem, I thought I'd read it or at least skimmed it, it's a small system, 3 POTS lines and 2 SIP numbers coming in, 3 SIP providers for outgoing calls, 3 Aastra 480i-CT handsets. We probably get 20 calls on a busy day and don't make many going out. Other than the POTs lines I spend under $10/month on phone calls and all outgoing calls use SIP. I'd compare with a working system, but being the brave foolish sort, once 1.6.2 seemed to be mostly working the machine with 1.2 minus it's memory and HD went off to be recycled. Ira ___ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] 2 Problems with 1.6.2
At 01:09 PM 7/17/2009, you wrote: Sorry, that's the most frequent problem that people have with MWI in 1.6, so it was worth mentioning. I would suggest that you file a bug report on https://issues.asterisk.org. It would be helpful if you would include SIP debug output for both a machine that is working, as well as a machine that is not working. So I'd be more than happy to file a bug report and include all the SIP debug anyone might need but it's been so many years since I did it that I've no idea how anymore. So I grabbed a cordless handset, sat down at the console, typed sip set debug ip 192.xxx.xxx.xx and called that voicemail box to leave a message. The instant I hung up a notify message was sent to my phone, but the red light did not come on. If you remind me the how, I'll grab that message and post it here. Thanks so much for the help. Ira ___ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] 2 Problems with 1.6.2
At 01:09 PM 7/17/2009, you wrote: Sorry, that's the most frequent problem that people have with MWI in 1.6, so it was worth mentioning. I would suggest that you file a bug report on https://issues.asterisk.org. It would be helpful if you would include SIP debug output for both a machine that is working, as well as a machine that is Not so embarrassing as I thought, I kept my notes and so here is the SIP output. I attached it in case the inserted section gets all messed up. Reliably Transmitting (no NAT) to 192.168.233.237:5060: NOTIFY sip:10277x...@192.168.233.237:5060;transport=udp SIP/2.0 Via: SIP/2.0/UDP 192.168.233.235:5060;branch=z9hG4bK3b6f21b4 Max-Forwards: 70 From: Robyns sip:1...@192.168.233.235:5060;tag=as405c743f To: Ira sip:10277x...@192.168.233.235:5060;tag=90f0be2565982a7 Contact: sip:1...@192.168.233.235 Call-ID: 5381b179eb2eec40ffa7dc855e671...@192.168.233.237 CSeq: 105 NOTIFY User-Agent: Asterisk PBX 1.6.2.0-beta3 Event: dialog Content-Type: application/dialog-info+xml Subscription-State: active Content-Length: 210 ?xml version=1.0? dialog-info xmlns=urn:ietf:params:xml:ns:dialog-info version=3 state=full entity=sip:1...@192.168.233.235:5060 dialog id=101 stateconfirmed/state /dialog /dialog-info --- --- SIP read from UDP:192.168.233.237:5060 --- SIP/2.0 200 OK Call-ID: 5381b179eb2eec40ffa7dc855e671...@192.168.233.237 CSeq: 105 NOTIFY From: Robyns sip:1...@192.168.233.235:5060;tag=as405c743f To: Ira sip:10277x...@192.168.233.235:5060;tag=90f0be2565982a7 Via: SIP/2.0/UDP 192.168.233.235:5060;branch=z9hG4bK3b6f21b4 Content-Length: 0 Contact: Ira sip:10277x...@192.168.233.237:5060;transport=udp Supported: replaces User-Agent: Aastra 480i Cordless/1.4.3.1001 Brcm Callctrl/1.5.1.0 MxSF/v3.2.8.45 - --- (10 headers 0 lines) --- SIP Response message for INCOMING dialog NOTIFY arrived Reliably Transmitting (no NAT) to 192.168.233.237:5060: NOTIFY sip:10277x...@192.168.233.237:5060;transport=udp SIP/2.0 Via: SIP/2.0/UDP 192.168.233.235:5060;branch=z9hG4bK5cb290bd Max-Forwards: 70 From: Robyns sip:1...@192.168.233.235:5060;tag=as405c743f To: Ira sip:10277x...@192.168.233.235:5060;tag=90f0be2565982a7 Contact: sip:1...@192.168.233.235 Call-ID: 5381b179eb2eec40ffa7dc855e671...@192.168.233.237 CSeq: 106 NOTIFY User-Agent: Asterisk PBX 1.6.2.0-beta3 Event: dialog Content-Type: application/dialog-info+xml Subscription-State: active Content-Length: 211 ?xml version=1.0? dialog-info xmlns=urn:ietf:params:xml:ns:dialog-info version=4 state=full entity=sip:1...@192.168.233.235:5060 dialog id=101 stateterminated/state /dialog /dialog-info --- --- SIP read from UDP:192.168.233.237:5060 --- SIP/2.0 200 OK Call-ID: 5381b179eb2eec40ffa7dc855e671...@192.168.233.237 CSeq: 106 NOTIFY From: Robyns sip:1...@192.168.233.235:5060;tag=as405c743f To: Ira sip:10277x...@192.168.233.235:5060;tag=90f0be2565982a7 Via: SIP/2.0/UDP 192.168.233.235:5060;branch=z9hG4bK5cb290bd Content-Length: 0 Contact: Ira sip:10277x...@192.168.233.237:5060;transport=udp Supported: replaces User-Agent: Aastra 480i Cordless/1.4.3.1001 Brcm Callctrl/1.5.1.0 MxSF/v3.2.8.45 - --- (10 headers 0 lines) --- Reliably Transmitting (no NAT) to 192.168.233.237:5060: NOTIFY sip:10277x...@192.168.233.237:5060;transport=udp SIP/2.0 Via: SIP/2.0/UDP 192.168.233.235:5060;branch=z9hG4bK3b6f21b4 Max-Forwards: 70 From: Robyns sip:1...@192.168.233.235:5060;tag=as405c743f To: Ira sip:10277x...@192.168.233.235:5060;tag=90f0be2565982a7 Contact: sip:1...@192.168.233.235 Call-ID: 5381b179eb2eec40ffa7dc855e671...@192.168.233.237 CSeq: 105 NOTIFY User-Agent: Asterisk PBX 1.6.2.0-beta3 Event: dialog Content-Type: application/dialog-info+xml Subscription-State: active Content-Length: 210 ?xml version=1.0? dialog-info xmlns=urn:ietf:params:xml:ns:dialog-info version=3 state=full entity=sip:1...@192.168.233.235:5060 dialog id=101 stateconfirmed/state /dialog /dialog-info --- --- SIP read from UDP:192.168.233.237:5060 --- SIP/2.0 200 OK Call-ID: 5381b179eb2eec40ffa7dc855e671...@192.168.233.237 CSeq: 105 NOTIFY From: Robyns sip:1...@192.168.233.235:5060;tag=as405c743f To: Ira sip:10277x...@192.168.233.235:5060;tag=90f0be2565982a7 Via: SIP/2.0/UDP 192.168.233.235:5060;branch=z9hG4bK3b6f21b4 Content-Length: 0 Contact: Ira sip:10277x...@192.168.233.237:5060;transport=udp Supported: replaces User-Agent: Aastra 480i Cordless/1.4.3.1001 Brcm Callctrl/1.5.1.0 MxSF/v3.2.8.45 - --- (10 headers 0 lines) --- SIP Response message for INCOMING dialog NOTIFY arrived Reliably Transmitting (no NAT) to 192.168.233.237:5060: NOTIFY sip:10277x...@192.168.233.237:5060;transport=udp SIP/2.0 Via: SIP/2.0/UDP 192.168.233.235:5060;branch=z9hG4bK5cb290bd Max-Forwards: 70 From: Robyns sip:1...@192.168.233.235:5060;tag=as405c743f To: Ira sip:10277x...@192.168.233.235:5060;tag=90f0be2565982a7 Contact: sip:1...@192.168.233.235 Call-ID: 5381b179eb2eec40ffa7dc855e671...@192.168.233.237 CSeq: 106 NOTIFY User-Agent: Asterisk PBX 1.6.2.0-beta3 Event: dialog
[asterisk-users] 2 Problems with 1.6.2
I've been using 1.6.2 for a few weeks and I've managed to get almost everything working perfectly. I can't get the MWI indicators on my Aastra phones to work properly, the did in all the versions of 1.2 I used up to the most recent one, but now they work correctly right after the phone is re-started and rarely thereafter. it's as if something changed in the way the MWI is handled and I can't figure out what the difference is or what I've done wrong. When I restart the machines I can't make an outgoing DAHDI call until I get an incoming call on that same line. Ira ___ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] 2 Problems with 1.6.2
On Thursday 16 July 2009 20:19:07 Ira wrote: I've been using 1.6.2 for a few weeks and I've managed to get almost everything working perfectly. I can't get the MWI indicators on my Aastra phones to work properly, the did in all the versions of 1.2 I used up to the most recent one, but now they work correctly right after the phone is re-started and rarely thereafter. it's as if something changed in the way the MWI is handled and I can't figure out what the difference is or what I've done wrong. When I restart the machines I can't make an outgoing DAHDI call until I get an incoming call on that same line. It would probably be best for you to read UPGRADE-1.4.txt, UPGRADE-1.6.txt, and UPGRADE.txt, as the issue with MWI is explained in there and what you can do to fix it. The second file contains the explanation, although you would be well advised to read all three. -- Tilghman Teryl with Peter, Cottontail, Midnight, Thumper, Johnny (bunnies) and Harry, BB, George (dogs) ___ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
