|
Joined: Apr 2007
Posts: 1,439
Member
|
Member
Joined: Apr 2007
Posts: 1,439 |
Cannot get the UM8000 inskin voicemail to do a dialout notification.
I have given this user permission to change notification settings, and I have setup "home" under notification with my cell number. When I leave the user a message, using 'port status' I can see the port go offhook and dial, but my cell never rings.
I have tried with a 9, without a 9, adding pauses....
Thought this would be easy, I'm lost.
D
|
|
|
Visit Atcom to get started with your new business VoIP phone system ASAP
Turn up is quick, painless, and can often be done same day.
Let us show you how to do VoIP right, resulting in crystal clear call quality and easy-to-use features that make everyone happy!
Proudly serving Canada from coast to coast.
|
|
|
Joined: Jul 2006
Posts: 731
Member
|
Member
Joined: Jul 2006
Posts: 731 |
There is a thread regarding this issue on the NTAC website.
"Load firmware 11.1.0.34 then load patch 11.1.0.39. Remove the 9 from dialout options & add it back in the dialout string in the mail box."
It sounds like a workaround to me. However, Active Voice claims the patchs will work, but the poster still had to "massage" it to make it work.
|
|
|
|
Joined: Apr 2007
Posts: 1,439
Member
|
Member
Joined: Apr 2007
Posts: 1,439 |
Thanks, I will be able to check into the patches this afternoon.
Will post back to let you you guys know how it went.
D
|
|
|
|
Joined: Apr 2007
Posts: 1,439
Member
|
Member
Joined: Apr 2007
Posts: 1,439 |
Current PBX version is 1.0.0.27
Current firmware of the voicemail card is 11.1.0.34.
Without doing any upgrades/patches I just removed the trunk access code from the system settings and put it in the dialstring in each mailbox and now it's working perfectly.
Thanks for the assistance!!
D
|
|
|
|
Joined: Jul 2005
Posts: 1,336
Member
|
Member
Joined: Jul 2005
Posts: 1,336 |
You may possibly blame me for this change.
A little history.
Way back in the day of rotary dial fones ours was one of the few countries in the world with a reverse dial. i.e. normally they go 0987654321 clock wise. Ours went 0123456789 clockwise meaning that the CO access code was always 1 rather than 9. With DTMF this all changed but most techs here today when they install a PBX system still use dial 1 as a CO access code. This is then complicated with the fact that with some systems on VPN the local station numbers start with the same number as the local area code. Here in Auckland ours is 9 so systems in Auckland will have their VPN station numbers starting with 9XXX. There is a problem with the UM8000 with software 11.0.2.6 in that when a call came into the AA and a station starting with 9xxx was dialed a CO trunk was picked regardless of what was programmed into the PBX or the mail. This appeared to be a bit of hard coding in the UM8000. UM8000 software version 11.1.0.39 fixes this problem and has most likely caused the OPs problem.. "Sorry about that chief."
Regards,
Paul W Now back to a 0 day week. Love these 7 day weekends.
|
|
|
|
Joined: Apr 2007
Posts: 1,439
Member
|
Member
Joined: Apr 2007
Posts: 1,439 |
Originally posted by paulw: You may possibly blame me for this change.
A little history.
Way back in the day of rotary dial fones ours was one of the few countries in the world with a reverse dial. i.e. normally they go 0987654321 clock wise. Ours went 0123456789 clockwise meaning that the CO access code was always 1 rather than 9. With DTMF this all changed but most techs here today when they install a PBX system still use dial 1 as a CO access code. This is then complicated with the fact that with some systems on VPN the local station numbers start with the same number as the local area code. Here in Auckland ours is 9 so systems in Auckland will have their VPN station numbers starting with 9XXX. There is a problem with the UM8000 with software 11.0.2.6 in that when a call came into the AA and a station starting with 9xxx was dialed a CO trunk was picked regardless of what was programmed into the PBX or the mail. This appeared to be a bit of hard coding in the UM8000. UM8000 software version 11.1.0.39 fixes this problem and has most likely caused the OPs problem.. "Sorry about that chief." you fellas down under just like to be different don't cha?? :rofl: D
|
|
|
|
Joined: Jul 2005
Posts: 1,336
Member
|
Member
Joined: Jul 2005
Posts: 1,336 |
Actually it was a US company that started the reverse dial thing from what I've been told. Way back early last century we bought our CO equipment from Western Electric which was a Bell Telephone Company equipment manufacturer at the time. They had some patent with their 7A rotary CO gear that required a reverse dial. Unfortunatly the powers to be in Telecom HQ back in the 1950s decided that their city was a WE equipt city and that the rest of the country would be the same. So those cites that were standard dial had to change them to reverse. So it was you guys up north that started it. :-)
Regards,
Paul W Now back to a 0 day week. Love these 7 day weekends.
|
|
|
|
Joined: Jul 2006
Posts: 731
Member
|
Member
Joined: Jul 2006
Posts: 731 |
Originally posted by doghart: Current PBX version is 1.0.0.27
Current firmware of the voicemail card is 11.1.0.34.
Without doing any upgrades/patches I just removed the trunk access code from the system settings and put it in the dialstring in each mailbox and now it's working perfectly.
Thanks for the assistance!!
:thumb:
D
|
|
|
|
Joined: Jul 2005
Posts: 1,336
Member
|
Member
Joined: Jul 2005
Posts: 1,336 |
I see that all remote access has been removed from the latest version of UM8000 software. Bummer. Site visits only now until it gets fixed..
Regards,
Paul W Now back to a 0 day week. Love these 7 day weekends.
|
|
|
sts pft
by davetel - 01/11/25 06:42 PM
|
|
|
|
|
Forums84
Topics94,459
Posts639,648
Members49,825
|
Most Online5,661 May 23rd, 2018
|
|
0 members (),
17
guests, and
38
robots. |
Key:
Admin,
Global Mod,
Mod
|
|
|
|