Topic: 7200s spnet to 7100 - cant call remote site via vmail

[matherton]

Might be something for tech level, but thought I'd start here.

2 sites spnet networked.  s/w 4.70 on both.  Users at both sites can call each other no problem phone to phone.
The voicemail has been set to auto-download all spnet extensions and trunks, and it has done so.
Calls coming into the 7200s are answered by AA.  When a caller dials an extension on the remote end, the AA says the normal transfer response "transfering to...".  Voicemail completes the transfer, but the call bounces immediately back into voicemail "i'm sorry that party is not available".  The phone system just kicks the call back into voicemail instead of attempting LCR-spnet the call. 

Has anyone else seen this kind of discontinuity?

I've managed a work around by putting in Day Main, the extension number as a dialable entity - goto a virtual SLT extension which is forwarded to the spnet trunk group: site code and extension number - which works - through the voicemail.

I've got a ticket open with STA, and have sent them databases and telnet voicemail traces, but nothing back yet.

[Marc Haycook]

Ugh... it's been a long time, but yes... I have seen this problem. If I remember it had to do with the extensions not being listed properly. I cannot remember what table, but you will need to add the extension group.

If the far end extensions are 23xx, you will need to add 23?? to the search table.

Does that make sense? If not call me later. I'll send you a PM with my new cell number.

[bmreen]

I think all that is required is to have the extensions of the remote node listed in the extension block

[matherton]

I think all that is required is to have the extensions of the remote node listed in the extension block

Yeah, the extensions are there, otherwise the voicemail would say "i'm sorry, that is not a valid entry".  the voicemail actually does transfer the call, saying "transferring to... one moment please" then the call terminates on that vm port, but bounces back in on the next available port in voicemail saying "i'm sorry, that party is not available" without actually sending the call to LCR and off to SPNET to the other side. 

[virob]

Hi Marty,

I'm not sure if this may be the issue as I haven't setup SPNet with centralized voicemail on V4.70 yet but I did notice the default outdial permissions on the Standard EClass changed to No for all.  You may need the off-premise to be yes as the system treats SPNet as a trunk call.

[matherton]

Hi Marty,

I'm not sure if this may be the issue as I haven't setup SPNet with centralized voicemail on V4.70 yet but I did notice the default outdial permissions on the Standard EClass changed to No for all.  You may need the off-premise to be yes as the system treats SPNet as a trunk call.

I saw that as well in EClass but thought since the voicemail is actually allowing the transfer to happen and sending the call out - that part didn't apply. 

I did get a message back late Friday from STA tech support that they believe my toll restrictions were denying the call.  I hadn't thought of that - thinking incorrectly that an SPnet extension call would be exempt of toll control.  I had assigned the voicemail ports a toll class and then denied any 0x call (doh!) to that class.  I haven't confirmed this yet but will be doing so Monday morning.  To be honest, I'm a little embarrassed that one got past me, having toll fraud restrictions didn't connect in my brain to SPnet extension calling...  Its a new day, more to learn!