Hi,
bereits an Siemens gemeldet.
Viele Grüße,
Olli
bereits an Siemens gemeldet.
Viele Grüße,
Olli
Firmware version: 021230000000 / 043.00
I have a S685IP base station with 6 handsets (3 S67H/S68H, 1 SL56, 1 4000 Comfort, 1 3000) connected to an Asterisk PBX (1.6.0).
Each of the handsets has it's own VoIP account configured and assigned. Asterisk has a single voicemail account, which is configured for 4 of the 6 handsets (the S67H/S68H and the SL56) as the "network mailbox".
When all of those network mailboxes are set to "active", the S685IP will crash during boot and thus stay in a reboot loop. This seems to happen when Asterisk sends the initial NOTIFYs for the mailboxes.
In the asterisk log file, I can see this
[Oct 12 13:20:06] WARNING[3005] chan_sip.c: Remote host can't match request NOTIFY to call '[email protected]'. Giving up.
[Oct 12 13:20:06] WARNING[3005] chan_sip.c: Remote host can't match request NOTIFY to call '[email protected]'. Giving up.
[Oct 12 13:20:06] WARNING[3005] chan_sip.c: Remote host can't match request NOTIFY to call '[email protected]'. Giving up.
[Oct 12 13:20:06] WARNING[3005] chan_sip.c: Remote host can't match request NOTIFY to call '[email protected]'. Giving up.
The only way to exit the crash-o-loop is by shutting down asterisk, disabling the network mailboxes, restarting asterisk, let the S685IP register and *then* reenable the network mailboxes one by one. Irritatingly, this works.
It looks to me as if there is some race condition in the S685IP's startup process, causing it to nuke when receiving NOTIFYs while still be in startup.