[AndrewTD]

Hi,

I have finally gotten around to setting up my first aa scripts on my SPA9000.
To date I (and my customers) have preferred to use the SPA9000 just with contact lists - no IVR.

But now I want to set up an after-hours aa script that invites callers to press 1 be transferred to an after hours on duty person (cell phone number programmed in the aa xml) or press 2 to go to voicemail.

I have got it working basically. The "press 1 to go to on duty person's cellphone" was fairly straightforward; but getting an option to xfer to voicemail was messy.

I couldn't get it to work using the vm<line id><vm id> construct.
I found by searching here a helpful post that suggested a workaround :
specify the xfer target as 0@<SPA400 IP address>:5092 ; or do the equivalent in the aa dp: <2:0@<SPA 400 IP address>:5090>S0.
This causes the aa script to drop back to the cfwd entry in the Line #1 contact list (which I have set to "cfwd=vm232")

Now this works, (and I am happy for that), but it does seem a somewhat inelegant solution.

Is their any tidy way of specifying an SPA400 voicemail account as a valid target of a xfer= entry in an aa xml script.?


Also, when testing this scenario, I found that quite often the SPA9000 would answer the call and supposedly direct it to the aa, but no audio would be played to the caller at all! I watched it with syslog, - debug level=3, but there wasn't any helpful info.
I would try again a few minutes later, (without changing anything in the interim) and it would work fine.
Do others have problems with the aa not always answering properly?

Today I discovered new f/w has been released for the SPA9000 - 5.1.9, and I have upgraded to it.

[Walford58]

Originally Posted by AndrewTD

..specify the xfer target as 0@<SPA400 IP address>:5092 ; or do the equivalent in the aa dp: <2:0@<SPA 400 IP address>:5090>S0.
This causes the aa script to drop back to the cfwd entry in the Line #1 contact list (which I have set to "cfwd=vm232")

Is their any tidy way of specifying an SPA400 voicemail account as a valid target of a xfer= entry in an aa xml script.?

I set up a hunt group to transfer to a particular voicemail box. Due to the limitations of the hunt, it does mean the quoted extension rings once, but transfers to vm without waiting for the phone forward timer to expire. It also means that extension 202 (in my example) will indicate message waiting on the handset:
5001:name="Voicemail2",202,hunt=ne;1;1,cfwd=vm2202

The aa script then has a target of 5001 when option 2 is selected.

Originally Posted by AndrewTD

Also, when testing this scenario, I found that quite often the SPA9000 would answer the call and supposedly direct it to the aa, but no audio would be played to the caller at all! I watched it with syslog, - debug level=3, but there wasn't any helpful info.

Originally Posted by AndrewTD

I would try again a few minutes later, (without changing anything in the interim) and it would work fine.
Do others have problems with the aa not always answering properly?

I have also had a problem with aa not always playing the audio. This was specifically with calls coming in over Sipgate. To resolve this I adjusted my NAT settings on the firewall and disabled the STUN on the SIP tab of the SPA400. The added benefit there was that my Plustalk account then allowed inbound calls - a problem which they had not resolved previously.

Pete

[AndrewTD]

Thanks Pete -Walford58, that's very helpful. I will use the Huntgroup as you described.

Recently I came across another post that mentioned the problem of SPA400 voicemail not giving audio. They suggested reducing the register time-out features to 30 seconds between the SPA400 and the SPA9000, and rebooting them in a particular order after changing the SAP9000 config. (I can't recall the order!) Basically they're suggesting that they loose the registration between themselves.

[AWIT]

I have the same problem. I have setup a hunt group as suggested and it works fine when I call the hunt group number from an internal handset but from the aa all I hear is silence when I should be hearing the VM greeting.

Any suggestions?

[humba3]

Are your bridge options set properly? I think you shouldn't even ask about cross device problems unless you mention how those settings are as they are crucial (the SPA400 really sucks in that department since it cannot even handle REFERs)

[AWIT]

VM bridge is enabled on the the SPA9000 line that is registered with the SPA400 but I'm sure I've got it wrong somewhere, the problem is I'm not sure how it should be configured...

[jamesnewbery]

For some reason AA seemes to take notice of codecs!!! don't understand why.

Make sure that everything is using matching Codecs, I have just set up using the hunt group to an internal extension and all working fine!

Thanks

James