Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations TouchToneTommy on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

voicemail to email not working

Status
Not open for further replies.

dimm0k

IS-IT--Management
Dec 6, 2019
18
US
not sure what happened over the past couple of weeks, but the voicemail to email option is no longer working! we have the Nortel BCM50 and a Nortel Contivity 1010 device and while the phones and vmail work, the option where you get an email notification after receiving a vmail no longer works. I've confirmed nothing is wrong with the software side in CallPilot Manager in terms of the settings so that leads me to suspect the hardware. I don't really have much information on this as this system was put into place before me and my knowledge of the system is basic at best. can anyone help me troubleshoot what might be wrong or what to do?

EDIT: logging into CallPilot Manager I just noticed that the setting that used to be available for each mailbox to forward to emails via a check box is no longer available! hopefully this is a clue for someone out there to help
 
Welcome to the forums dimm0k

What page and what is the name of setting are you referring to in Callpilot Manager?
We cannot see what you can so please be very specific when posting.

If your missing a box then will assume it's more likely a software or user/admin input issue.

Follow my steps in order until you might see where something is not inputted correctly...

To enable voice mail to email on Callpilot 100/150/BCM:

-Go to Configuration/SystemProperties and fill out all the SMPT message forwarding details at the bottom
-Go to the Class Of Service, choose your C.O.S. number that the mailbox is in and "Enable Message Forwarding"
-Go to the users Mailbox Manager/MessageForwarding and "Enable Message Forwarding"
---Fill in the email address
---And the rest of the options

Test and please always update your posts/threads no matter what, with resolution (when possible) so those whom help and others with same issue are not left hanging.
Thanks
cc









________________________________________
small-logo-sig.png


=----(((((((((()----=
Toronto, Canada

Add me to LinkedIN
 
@curlycord thank you for your reply. I was able to confirm your first step and its settings are input correctly. I'm stuck on the second step as I cannot find anything with regard to Class Of Service while in Callpilot Manager. The version number described in "System Properties" is Voice Mail Version: 43.03.24.22 and I know for a fact that my own mailbox should be forwarding my voicemail messages to me as an email. I've attached a screenshot of what I see
2019-12-09_13_03_50-Callpilot_Manager__Mailbox_Properties_aulebi.png
. It may have been a while since I've actually given anyone access to this feature of "vmail to email" that I am recalling incorrectly of what the option should say, but I would guess at this point with relation to the info you've provided that the "Class of Service" of 2 does in fact mean "vmail to email"? You'll also note that in the screenshot that there is no mention of an email to use for the forwarding.

while digging around I was able to pull up the Event Log and below is a snippet of what may be the cause or possible multiple cause of what has gone wrong
Code:
ALARM REPORT                                        Date: 2019/12/10

Date       Time     Error Message
----       ----     -------------
...
2019-12-10T00:07:54.348 [INFO ] {STLog} (0) - Daily statistics ..
2019-12-10T00:07:54.349 [INFO ] {STLog} (0) - One call FOD 0 Two Call FOD 0 FOV 0 FAX Print 0
2019-12-10T00:07:54.349 [INFO ] {STLog} (0) - Incoming AMIS 0 Outgoing AMIS 0 VPorts Busy 0  FPorts Busy 0
2019-12-10T00:07:54.349 [INFO ] {STLog} (0) - F980 Sess 0 F981 Sess 5 F982 Sess 0 F983 Sess 0 F985 Sess 0
2019-12-10T00:07:54.349 [INFO ] {STLog} (0) - F986 Sess 0 F987 Sess 0 F988 Sess 0 F989 Sess 0 F930 Sess 0
2019-12-10T00:07:54.349 [INFO ] {STLog} (0) - Call Ans 17 AA/CCR 14 OPN 0
2019-12-10T00:07:54.349 [INFO ] {STLog} (0) - Ext Trans 0 Ctx Trans 0 Broadcast Msgs 0 Group List Msgs 0
2019-12-10T00:07:54.349 [INFO ] {STLog} (0) - SMTP Receive 0 SMTP Send 0 NVM Manager 0 Call Screening 0
2019-12-10T00:07:54.349 [INFO ] {STLog} (0) - Dsktp Logins 0 Dsktp Open Msgs 0 Text Bodies 0
2019-12-10T00:28:38.519 [INFO ] {STLog} (0) - SMTP: osConnectToSecureServer() failed rc=7(0x7)
2019-12-10T00:28:38.519 [INFO ] {STLog} (0) - SMTP: osReadFromSecureSocket failed rc=14478(0x388e)
2019-12-10T00:31:47.518 [INFO ] {STLog} (0) - SMTP: osTCPConnect() failed rc=7(0x7)
2019-12-10T00:31:47.518 [INFO ] {STLog} (0) - SMTP: SmtpSendMail SMTPConnectToServer failed rc=7(0x7)
 
Perhaps you can edit that log, way too long and repetitive...edit button is to the right but for a limited time only.

When in the Manager did you go through the list to look for it?
Click on Mailbox Administration and it's the last link.

In the case of your screen shot above that mailbox is in Class Of Service 2.
However the screenshot is showing your mailbox under Mailbox Administration/Change, I did not direct you to go there as there is nothing there to see that is related to the issue.

FYI..even C.O.S. numbers are for the Alternate Language such as Spanish in the states or French in Canada.

________________________________________
small-logo-sig.png


=----(((((((((()----=
Toronto, Canada

Add me to LinkedIN
 
@curlycord sorry, I've edited the log to contain a small snippet of the log. As for C.O.S. that you were referring to, I found it after you mentioned it's in Mailbox Administration. I expanded all of the sections EXCEPT that for some reason. I've attached a screenshot of this section to show that it is in fact enabled so things should be working for phones with C.O.S. set to 2.

2019-12-10_11_08_16-CallPilot_Manager__Class_of_Service_bw7a4y.png


please disregard the previous comment's screenshot of the Mailbox. I included it since it was to show that that Mailbox was set differently in terms of the COS for ones that should have message forwarding set. now this leads me back to my log file of it not being able to connect to the SMTP server... I know there's nothing wrong with the SMTP server as I am able to connect it to my mail client on the desktop.
 
2019-12-10T00:28:38.519 [INFO ] {STLog} (0) - SMTP: osConnectToSecureServer() failed rc=7(0x7)

Well this leads me to a simple question, does your SMTP server see the BCM on your network? Can you ping the BCM from the server?

Marv ccna

 
Thanks for editing.

Still need to find where youy saying the Box is missing so my last questions still unanswered would be:
-Go to the users Mailbox Manager/MessageForwarding and[highlight #FCE94F] "Enable Message Forwarding"[/highlight]
---Fill in the email address
---And the rest of the options

I was not paying attention to the alarms because you said the "Enable Message Forwarding" box is missing.
If you can confirm the box is in the Mailbox manager then I would look into what Marv is showing, even check the BCM's alarm list too.

________________________________________
small-logo-sig.png


=----(((((((((()----=
Toronto, Canada

Add me to LinkedIN
 
@allworxguy the SMTP server is actually an outside third party server. this has not changed since this was first installed (prior to me working here) and I do have the credentials so I am able to confirm it has not been changed. because the BCM is on our LAN it is not directly ping'able from the outside without making any changes on the firewall to do NAT. this part has also not been changed.

@curlycord sorry for not being clear. the missing box I was referring to was in the Mailbox screenshot that I first posted, which is what I see when I go to the users Mailbox Manager. here I do not see the "Enable Message Forwarding" option at all. can you confirm this is where I should see this option?
 
No it is not, what you are seeing is a particular mailbox's properties under Mailbox Administration.

You need to go to Mailbox Manager and not Callpilot Manager
So after the IP address enter /mailboxmanager instead of /callpilotmanager (mailboxmanager)
Then enter the users mailbox number and it's password.

Then you should see the box to enable "Message Forwarding" link.
Once you click that you will see "Enable Message Forwarding" box and the rest of the entries.

________________________________________
small-logo-sig.png


=----(((((((((()----=
Toronto, Canada

Add me to LinkedIN
 
@curlycord omg, there we go!! sorry, I was stuck in Callpilot Manager and thought the "Message Forwarding" link was there and not in the Mailbox Manager. anyway, to confirm the setting is there and is correctly set for my own mailbox. now that that's confirmed to be correct, what is next?
 
I would say go into ElementManager/Administration/Utilities/and use the Ping fetaure and ping 8.8.8.8 and your SMTP server....this will help see if the BCM can get in touch with the internet.
Maybe it's not on the network any longer? and network changes lately?

Also per Allworxguy about the alarms also check the BCM alarms too - ElementManager/Administration/General/Alarms and look for any alarms related the issue.


If you are convinced that the Callpilot settings are all correct and that you tried a reboot of the BCM then I would say you have a network issue and/or beyond.


________________________________________
small-logo-sig.png


=----(((((((((()----=
Toronto, Canada

Add me to LinkedIN
 
@curlycord looks like the BCM is not capable of contacting the Internet as it is not able to ping even 8.8.8.8. Do you happen to have a layout of what should be connected to for the BCM to get out onto the Internet? there were some tinkering around when the Verizon technician came by to replace the router and do some testing for a network related issue. unfortunately I was not around when this was happening so I'm not sure what they did!
 
Make sure cable is in the 2nd from the left on the BCM going into the Switch on the other end.

On a PC on the same network open/run Command Prompt (cmd)
Do: ipconfig and note the IP address, Subnet & Gateway

Check ElementManage/Configuration/IPSubsystem/LANintrefaces and check the IP address under Customer Lan
If you need to change it then change it, then reboot via Admin/Utilities/Reboot

Or you can do it via telset using F9*8 and the credentials.
IP Address, change as need then press BACK to see the Reboot option and do it.




________________________________________
small-logo-sig.png


=----(((((((((()----=
Toronto, Canada

Add me to LinkedIN
 
so the 2nd port from the left on the BCM has a cable attached with lights on connected to our switch. our PCs are on the same network with 192.168.200.xxx IP addresses. The closest I can get to what you described in Element Manager is pictured below

The IP address
2019-12-11_14_50_10-BCM_Element_Manager_-_192.168.20.50_bghbgv.png


Checking the IP address of my own phone, I can confirm that it is 192.168.200.52 and am able to ping the phone from the computer. This would mean they are both on the same network correct? I'm have no trouble getting to the Internet from the computer
 
Internal Lan would be same as Customer Lan, yours must be an older release....rls 3 maybe.
So it looks like the Internal LAN IP address on the BCM went back to default.
So change the IP address and also change the .252 at the end of the subnet to most likely .0, then go to General tab beside it and change the gateway too then reboot.





________________________________________
small-logo-sig.png


=----(((((((((()----=
Toronto, Canada

Add me to LinkedIN
 
so it looks like I've hit a snag... after making the changes and doing a reboot I'm getting the attached error message when trying to connect to Element Manager.
2019-12-11_17_12_28-Nortel_Business_Element_Manager_-_Network_Elements___192.168.20.50_tflfvw.png

The phones themselves are saying server unavailable.
 
The phones themselves are saying server unavailable."

I gather IP phones then....
If the phones were working on 10.10.99.1 then they are now trying to connect to 10.10.99.1.
This would mean something was changed on the network after all.

Put it back to 10.10.99.1 then and reboot.

You error is caused by you did not wait 15 minutes or so to boot up or you forgot to change the IP address on your laptop to something like 192.168.20.60

And contact your network crew to check into it.




________________________________________
small-logo-sig.png


=----(((((((((()----=
Toronto, Canada

Add me to LinkedIN
 
ahh, I was not aware that it would take 15 minutes or so to boot up! to confirm, I was supposed to change the IP to 192.168.200.1 and the .252 to .0 section correct? all the computers on the network get DHCP to an IP address in the 192.168.200.100-192.168.200.240 range while all the IP phones and the BCM are between .50 and .99. the weird thing is after I rebooted the device the IP address went back to 10.10.99.1 and also back to .252! after making these two changes I'm disconnected from ElementManager and logging back in still shows the old values! any ideas?
 
-Every device must have it's own IP and be in the same range (parts 1-3), only the last part (4) should be different from the rest.
-Most networks have a subnets of 255.255.255.0
-The Gateway is usually the lowest number such as .1

To sort out IP address's in regards to subnet being .0 or .252 I cannot tell you what really is correct,you need to this to answer that question:
"On a PC on the same network open/run Command Prompt (cmd)
Do: ipconfig and note the IP address, Subnet & Gateway"

ipconfig results:

Ethernet adapter Ethernet 4:

Connection-specific DNS Suffix . :
IPv6 Address. . . . . . . . . . . : 2607:fea8:2040:4ae:3cb1:fe14:4669:c22a
Temporary IPv6 Address. . . . . . : 2607:fea8:2040:4ae:cc91:22c1:59bf:8dd1
Link-local IPv6 Address . . . . . : fe80::3cb1:fe14:4669:c22a%14
IPv4 Address. . . . . . . . . . . : 192.168.1.247
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : fe80::76da:daff:febc:c06d%14
192.168.1.1

To make sure what the BCM IP was go to an IP set and press "Services" twice quickly, then press "Enter" to go to "IP Set Info", scroll down to bottom to see "EEPROM S1 IP: and see whats here.

If changing the IP address of BCM did not work then try via the phone as I stated above:
"Or you can do it via telset using F9*8 and the credentials used to normally program through the set.
Navigate to IP Address, change the three sections as need then press BACK to see the Reboot option."





________________________________________
small-logo-sig.png


=----(((((((((()----=
Toronto, Canada

Add me to LinkedIN
 
I can confirm that the subnet should be 255.255.255.0 and the static portions of the IP address are 192.168.200.xxx where the last xxx varies across the phones, printers, and computers on the network. on the phones themselves the S1 IP address matches the address of the BCM, 192.168.200.50.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top