SPA112 Voicemail indicator problem

[J.A. Vliet]

Hi,

I'm a newbee in voip so I hope my discription of this problem makes any sense.

When there is an voicemail my dect phone shows an icon. So far so good. But after I listen and remove the voicemail and than create another voicemail, the icon doesn't show anymore. So it is a one time only event. After I reboot the SPA112 it works again but only for one time again.

Everything else is working fine.

Because the SPA112 is behind a NAT. I've set the keep nat alive and nat mapping on Yes. The nat keep alive message and destination is default $notify and $proxy.

In the SIP settings I set the nat keep alive to 15.

Firmware: 1.3.3 (015)

Are there any other settings to set?

Regards,

Jos

[Dan Lukes]

Well. It's because the SPA112 doesn't know there is message stored on mailbox, or SPA112 is not delivering the state to your's DECT phone properly.

According "divide et impera" principle we need to decide.

Visit the WWW interface of the SPA112. Check the status page. What's value of "Message Waiting" state is show here for the extension in question ?

[J.A. Vliet]

Hello Dan,

Thanx for your reply. The "message Waiting state" after I create a voicmail is "No". So indead the SPA doesn't know there is a message.

Also the "last caller number" is not the number I used to create the voicemail.

But why does the SPA do it only once after a reboot?

[Dan Lukes]

The SPA device will subscribe to state server on reboot. The server should send initial state of service immediatelly after subscription. But then, the notifications will be sent by server when necesarry.

Let's continue with dividing. Now we need to decide:

1. notification is NOT sent by server

or

2. notification IS sent by server, but the packet is not delivered to phone (because of NAT, firewall or so)

or

3. notification IS sent by server, IS delivered to phone, but not recognized by them as valid message

You need to catch SIP messages between your device and the switch (PBX). Use tcpdump or wireshark or other packet catcher. You need to see NOTIFY messages arriving from server. If you will see no one, it is either server or network issue. If you will see those messages, check the phone's response. Also turn on syslog&debug messages and catch them. They may help you with the analysis.

Installing and Using Wireshark for Capturing Network Traffic

Debug and syslog Messages from SPA1x2 and SPA232D ATA (Analog Telephone Adapters)

[J.A. Vliet]

I've installed Wireshark and captured while creating a voicemail. But I don't see any traffic from or to the ipadress of the SPA. And I don't see any UDP traffic. Do I have to set setain things?

My SPA is in the same vlan as my PC.

The syslog is in the attachment.

[Dan Lukes]

If there is switch between the PC running packet catcher and the SPA the packets will not be sent to you. Smart switches may be configured to forward other's traffic to you, but it's not possible on most common cheap switches.

It may not be problem as long as you configured "SIP Debug Option" to "full" and "Syslog Server" and "Debug Server" has been directed to IP of computer running the packet catcher (or syslog server).

I see no debug messages in your's attachments. Note that local log (e.g. logs are stored on SPA itself) is know to be unreliable. Log and debug messages needs to be catched outside of SPA.

With SIP Debug Option full we should see SIP packets in debug log so it's not necesarry to catch them directly.

[J.A. Vliet]

Dan,

The problem is solved! I've connected the SPA to the router directly instead of connecting it to a switch. Your line about the switch gave me the idea.

So every time there is a voicemail I see the vocemail icon apear om the DECT. And in the setting on the SPA interface the  value of "Message Waiting" state is now "On".

So, thanks for all you input and efford.

[Dan Lukes · Accepted solution]

Glad to hear, despite I have no idea how the switch caused the original problem.

Mark thread as answered, please. It will help others to found solutions.

Regards

Dan