Outcalling - Server Edition vs VM Pro on Windows 1

[Mullet_Rocker]

I have a 500v2 with VM Pro on a Windows 2012 Server. I have outcalling set up using the callback token in VM Pro under the user mailbox and the P Source number string in Manager. The P string contains commas for pauses and it works just fine. I have a customer with server edition and have the same exact setup, but the server edition appears to ignore the commas for pauses and using a digismart, I can see that it's just dialing the numbers in the P string consecutively twice and not paying any attention to the commas for pauses. Thoughts? Why is it different on Server Edition?

 

[IPGuru]

1st question what is the reason for the pauses?
this suggests you are trying to do something with out-calling that was not intended.
(does not man there may bot be a work around)


Do things on the cheap & it will cost you dear

 

[Mullet_Rocker]

The intention is to have it call a number that is answered by a paging system, pause, enter pager number, pause enter 4 digit code. This works on my system with Windows based VM Pro. However, the P Dial string in the Server Edition seems to ignore the commas as pauses.

 

[Mullet_Rocker]

Forgive me, I guess this is referred to as Callback, not Outcalling. Per the VM Pro Admin Guide, it states the following:
8.7.1 Callback
Voicemail callback is a service whereby the Voicemail Pro calls a specified number whenever the user receives a new
voicemail message. When the callback is answered, the system announces the outbound alert and waits for a key press
for confirmation before continuing with the associated call flow.
This service requires configuration of a callback start point in Voicemail Pro and entry of a callback number through IP
Office Manager. See
Using a Personal Options Menu Action
.
The call flow created below is a very simple example. In practice you could include a menu that provides the user access
to other features. For example using access to a Personal Options Menu action, the user can remotely change various
mailbox settings including the callback number.
To set the user's callback number:
1. In IP Office Manager, open the system's configuration.
2. Click
User
to display a list of existing users.
3. Double-click the user for whom callback is being set up.
4. Select the
Voicemail
tab.
· In
Voicemail Code
, enter a pin code and confirm this in
Confirm Voicemail Code
.
5. Select the
Source Numbers
tab. Right-click and select add to add a new number.
·
Callback Number
Enter
P
followed by the destination telephone number. If you system requires an external dialing then that prefix
must be included, for example
P901923555456
. If connecting to a cell phone or pager system that expects digits
in separate sets, use , (comma) characters to add pauses to the telephone number dialing.

 

[IPGuru]

for this solution I would suggest creating a short code to call the pager use the 'D' &/or 'Y' characters to wait for the answer as well as any ',' for delays & set the users call back option to the short code.

as you have VM Pro you would still probably be better off looking at out-calling to a mobile (out-calling requires the connection to be acknowledged & can escalate to other users if needed) or VM to email, especially of the pager service offers an email gateway.



Do things on the cheap & it will cost you dear

 

[Mullet_Rocker]

IPGuru, thanks. I tried setting up the CALLBACK as well as OUTCALLING. CALLBACK was set up using the P and the dial string in the Source Number field under the user (P followed by the outbound access code, then the phone number, then pauses, then pager number, then 4 digit code). OUTCALLING was attempted as well using * for pauses. Again, attempting from my demo unit to the pager system, it works both ways (outcalling and callback). However, when setting this up on the customer's server edition, it ignores the pauses whether I am using CALLBACK with commas, or OUTCALLING with *. It just dials the number strings in rapid succession and repeats 2 or 3 times. I may have to open a ticket with Avaya.

 

[IPGuru]

whay about my other sugestion
instead of including the commas in the call back number
set the call back number to a short code that has the delays in it

example if your callback is currently 01234567890,,,1234

create a new short code

SC: 666
TN: 01234567890Y,,,1234 (the commas may be unnecessary after the 'y' which says wait for call progress message)

and set the call back number to 666


Do things on the cheap & it will cost you dear

 

[Mullet_Rocker]

I built a shortcode for Dial, <access code><10 digit number to pager system>D****<Pager Number>*****<4-digit Code to send to pager># and set the callback to the new shortcode and it's working. However, it still doesn't explain my original problem where the server edition appears to be ignoring my commas for pauses in dial strings. I can monitor the connection to the pager system and hear the stars being passed as DTMF in addition to the numbers I want to send. Fortunately, the pager system must ignore the stars when they're dialed.

 

[qtelcom]

Give the man a star for your work around! You'll probably have to show Avaya your bug issue with SE ignoring your comma's and then it'll be fixed in some future service pack a couple months later...

 

[joe2938]

who cares at this point it's working, i think you owe IPGuru some pink

 

[Mullet_Rocker]

All apologies.....IPGuru has been given a star!!! Thanks again.