Can you dial into the IP Office PBX and then make an outgoing call?

[jhtnadave]

I am trying to enable the system to allow users to call into our 800 number and then once inside the system, place an outgoing call. Is this possible? I am running 3.2.57.

Thanks.

 

[BoyRacer1001]

Yes if you have VM Pro. send it to menu with $ as only key option + timeout, then send to a transfer with $KEY as destination.

You will want to add pin coding etc for security

 

[puregold]

Do this at your own peril.

This is how fraud is commited.

First thing you will know is you will get a $20,00000 telephone bill.

ACE - Avaya Certified Expert
ACI - Avaya Certified Instructor

 

[ipofficeman]

So thats how you suplement your income Pure gold!!

 

[Bas1234]

Or wait for version 4.2

It works like the Avaya communication manager.

see link below

http://support.avaya.com/elmodocs2/mobile/Avaya_Nokia_Aruba_App_Note_05_14_07.pdf

greetzz...Bas

________________________________________
It works! Now if only I could remember what I did...
________________________________________

 

[jhtnadave]

BoyRacer,

Thanks for the tip. I set this up as you suggested. I know I am getting to the module, but nothing happens when I get there other than the system asks me to enter my access code. I do that and then enter a number and nothing happens?? What am I missing?

Thanks.

Dave

 

[BoyRacer1001]

You need to press # after entering your number, and/or include a "Wait for key press for" time say 3.
Also best to include some sort of greeting (entry prompt) in the menu, even just for testing.

 

[ZebrAYA]

Quoting puregold
“Do this at your own peril.
This is how fraud is commited.”

Certainly it’s a possibility, but one of our clients needs to re-route mobile (cellphone) calls to international trunks (analog or SIP trunks), and we’ve not implemented it because he hasn’t purchased the cellular base, but also because in another tests we couldn’t get it.
So I ask.

Can I program the IPO / VMpro to allow taking line only to registered users, I mean members of X “user rights” profile?

Can I program the IPO / VMpro to add security to the operation asking for pins an passwords to check identity?

Is this controlled by VMpro features or by IPO account codes?
Jhtnadave have you actually got your setup working right?

 

[ProviderReborn]

In 4.1 you could use telecommuter mode which would then follow user rights ie if they have international barring or the likes.
This then has the added security of:

A: Your users logging into the PC Laptop in a secured fashion,
B: Any security your VPN offers,
C: The user name and password which would be assigned to the PhoneManager.

From Knowledge Base

#

Telecommuter Mode (Phone Manager 4.1+)
In this mode, a user running Phone Manager Pro on a PC with a data connection to the IP Office (for example via VPN), is able to have their calls routed to a telephone number they specify when starting Phone Manager. When the user makes a call using Phone Manager, the IP Office will call the user's specified telephone number and when answered, then make the outgoing call for the user. Similarly incoming calls to the user's extension on the IP Office are routed to the remote number. By having the speech part of all calls initiated from the IP Office, the cost for those calls is assigned to the IP Office.

If your routing a ICR into a VM module to dial out, it will not be a user on the system making the calls, it will be the VM ports.
So you would need to assign a Pin check on a menu or some thing like a check digits option in VM Pro.

I like the telecommuter mode, it would of course mean an upgrade plus more.


ACA - IP Office Implement
ACA - IP Telephony
ACS - IP Office Implement
CCNA - Working towards.

 

[jhtnadave]

ZebrAYA,

I do have this working. In VMPro you can set up a PIN code in the menu and the system hangs up after 3 incorrect tries. I have my system setup so this can be accessed using a short code.

Let me know if you have any other questions.

Dave

 

[puregold]

Im not saying dont do it.

Im saying if you ae going to do it then you need to be careful that you do it 100% right and get your customer to sign a disclaimer.

Otherwise, six months later when you realise you put a number in somewhere that enabled hackers to dial international, whos gonna pay the bill?

Things could get messy.

Cover your arse and make sure you do it 100% right.

ACE - Avaya Certified Expert
ACI - Avaya Certified Instructor

 

[aarenot]

In this situation advising the customer of the risks of unintended usage, and letting them know that you are assuming, and informing them that this WILL happen in order to cover your own persoanl liability is my usual procedure. Letting the customer know that since unintended usage is anticipated with this set up, the customer must take proactive steps to monitor the toll billing in real time, change security codes often enough to eliminate any toll fraud, as well as take responsibility for any unintended usage as well as the toll charges incurred by such set up.

Finally, set it up in programming, everything except pressing save in the IPO manager, and saveandmake live in VMPRO. Then have the customer press the save in manager, and saveandmakelibe in VMPRO, so that it is not actually you who implemented the changes. There is a difference legaly I am told by my attorney to shwoing how to, and actually doing it yourself. Just like you are not responsible for what CD is put in the player for MOH even though you may connect the player, unless you are the one who presses play.

 

[ZebrAYA]

I am making some preliminary tests, letting external user to dial an option in the Main menu, dial the PIN code, dial the desired number and #.
It’s working fine for local numbers, any time I tried to dial a mobile number, the call hangs out immediately.

The mobile number dialing never goes out via main trunk (a PRI trunk) but via cellular bases, for that to be done I use a two digit numeric prefix. (registered as a shortcode)
What’s the relationship between this VMPRO dialing and system / user call barring settings?

Since I can’t choose outgoing trunk in VMPRO, I thought using the same shortcodes the VMPRO would told the IP Office which trunk to use.


[Always Close your threads for avoiding other people to entangle]

 

[aarenot]

I would also add that putting the access to outside lines on the main AA is not the best practice. I would use a DID which is not the main one, have the AA provide no instructions, and not even have a prompt, just silence so most will hang up.

 

[tlpeter]

Or use a WAV with a text that this number is not in use
Only the people who knows will put ina pincode and the rest will hang up or get disconnected

ACA - Implement IP Office
ACA - Voice Services Management
______________
Women and cats can do as they please and men and dogs should relax and get used to the idea!

 

[ZebrAYA]

Taking the idea of aarenot and tlpeter

I’ve already implement the different AA, accessible only for two analog trunks, and one DID number, I have a prompt that the public cannot hear, and I gave the caller the option to call 0 to be transferred to the main AA

But I have still the question…
It’s working fine for local numbers, any time I tried to dial a mobile number, the call hangs out immediately.

See this
My local PSTN numbers are of 7 digits
My local Mobile numbers are of 10 digits
the internal user dials 7 + number for local numbers (trough main PRI trunk)
the internal user dials 80 + number for mobile numbers (trough ARS and tecom mobile trunks)

its working just OK.

the external user dial the “secret” DID number, and gets into the VMPRO
later dial 7 + local number and # (or wait) and outgoing call is made. (using transfer to $KEY)
Or
Later dial 80 + mobile number and # (or wait) and call is hanged up before ending dialing.






[Always Close your threads for avoiding other people to entangle]

 

[aarenot]

try skipping the 80, see what happens.

 

[ZebrAYA]

Retaking this thread I would like to comment my progress with this process

I had to disable account codes since they were UNCOMPATIBLE with $KEY and trunk to trunk connections, if I used the 80 ARS, call would not be done.
Only alternative I had to overcome the “80” line problem was cloning this line, but deactivate all (yes – all) the “force account code” checkboxes.
A group of users (remote location) are able to call dialling “82” (80’s clone) and they are the only people supposed to be aware of that, but of course, if any other user inside or outside the company uses the “82” will able to establish un-restricted codes.

We have an ISDN, 4 mobile gateways, 4 Voip Direct numbers, and 4 data channels with a remote location via Cisco Routers.
Virtually all the combinations of trunk to trunk calls are enabled.

My customer is aware of consequences of the –almost unrestricted- trunk to trunk connections, he wants to cut costs of telephony biding every user to use the collective phone resource.

Even more, because the only alternative

One of you said that its not the “best practice” and that’s right, as far as these secrets can’t be keep as that for a long time.
The trunk to trunk international, mobile or any kind of calls can’t be tracked

There’s a system for accounting and billing running on a PC taking CDRs from the IP 500, via 8090 port. The system detects account codes (on purpose authorization codes show as passwords ******, so could not be used for auditing user calls), any call made trunk to trunk is not tracked, not registered, not billed.

FINDING A DEFINITIVE SOLUTION

I told the customer that we could use some methods to prevent illegal access.

1) personal shortcodes, the user will have a *something* shortcode that will lead him to a individual module on the VMpro (paper says it has unlimited modules) this module will be PIN protected, and only the user will know the PIN, later, when call is established the accounting software will see “calling from jon_jones_attendant”
2) a way that user validates himself when making a call from outside. Curiously the customer is familiar with Altigen and Nortel and said it was possible to do on those old machines
You have mentioned that 4.2 release will do more on that, can I keep the hope?.
3) Trying other features of Voicemail (we have the 4.0.20 release) that help to make a more secure trunk to trunk transfer.






[Always Close your threads for avoiding other people to entangle]