03-24-2011 06:10 AM - edited 03-21-2019 03:51 AM
We have a SPA8000 connected to a UC540. After about two days of working, it starts acting flakey. They have 2 phones and 1 fax machine. When the phones try to dial out, they get a busy signal. The fax can dial out no problem. When you call into the system, the phones ring and you can answer them and talk no problem. If you do not pick up, it should go to voicemail. It says 'there is no mailbox associated with this extension.' I changed the cfna from the voicemail pilot to the transfer to voicemail prefix + the extension and that get the external caller into the mailbox. It seems like the extension information is getting hosed somewhere along the line.
A debug showed this information:
708673: Mar 23 16:48:06.779: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:
Calling Number=anonymous, Called Number=, Voice-Interface=0x0,
Timeout=TRUE, Peer Encap Type=ENCAP_VOIP, Peer Search Type=PEER_TYPE_VOICE,
Peer Info Type=DIALPEER_INFO_SPEECH
708674: Mar 23 16:48:06.779: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:
Result=NO_MATCH(-1) After All Match Rules Attempt
708675: Mar 23 16:48:06.779: //-1/xxxxxxxxxxxx/DPM/dpMatchSafModulePlugin:
dialstring=NULL, saf_enabled=0, saf_dndb_lookup=0, dp_result=-1
708676: Mar 23 16:48:06.783: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:
Calling Number=anonymous, Called Number=, Voice-Interface=0x0,
Timeout=TRUE, Peer Encap Type=ENCAP_VOIP, Peer Search Type=PEER_TYPE_VOICE,
Peer Info Type=DIALPEER_INFO_SPEECH
708677: Mar 23 16:48:06.783: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:
Result=NO_MATCH(-1) After All Match Rules Attempt
Not sure if that information has anything to do with anything but maybe it does.
03-24-2011 06:48 AM
Hi Jason;
I suggest (if not done already) to upgrade the SPA8000 to latest firmware. Old firmware is known to have interop issues with UC500. Please let me know if you have done this already.
Regards;
Alberto
03-31-2011 06:05 AM
It turned out the 'block CID setting' was making this not work. It should be set to 'no'. The strange thing is that it started off at 'no' when we did the install. Somehow, it changed itself to yes after a couple of days. Also, L1 and L2 had it set to yes and L4 had it set to no. We never touched that setting at any point. After upgrading the firmware and changing this setting, it has been working fine for a week.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide