FNE Service 1

[4vayaMan]

I have a 500v2 on 6.0.(14) and I was trying to play around with the FNE Service but am not having much luck. My extension has a Power User profile so licensing should not be an issue here. According to the knowledgebase I can create a short code like this:

Code: 777XX
Feature: FNE Service
Telephone Number: N
Line Group ID: 0

I read that FNE31 is the star star support code so I pointed an unused DID to 77731 but when I call in one my cell phone I get a busy. Im calling from the number that is set in the twinning profile for my extension. Anyone else had luck with this?

Thanks in advance

 

[intrigrant]

use the FNE for dial tone or appearance.

 

[thrtnastrx]

Make sure you have your twinning set to the same phone number as the phone you are testing from.

 

[Westi]

make sure you read the help in the Manager (hate to tell you) it is quite good and will point you to where you need to be.
Also I think the number needs to be a FNE service number so the telephone number can not be N it needs to point to it as far as I remember but don't quote me as a reliable source I am overtired and need to sleep before my brain starts working again.

Joe W.

FHandw., ACSS

 

[4vayaMan]

Westi the Help had the same documentation as the knowledgebase. Ive read the darn thing so many times and have tried so many things but to no avail. Should I be able to dial that shortcode internally and get the FNE service? Because I get a busy there too. Im thinking about hard rebooting the PBX and seeing what happens. It just doesn't make sense that it wont work.

Also thrtnastrx I am using the mobile number that is in my twinning field.

 

[tlpeter]

Did you enable "mobile call control" for the user?
Then you make a shortcode like you already mentioned.
Then you make an incoming call route with the CLI of the mobile phone and give it destination shortcode with the right number for XX

00 is dialtone
33 is call back (must be activated on the user too.

So in your case you need shortcode: 77700 for dialtone.
Security is done by looking for the mobile number on the mobile twinning field.
When there is no match then no dialtone.


When you pay peanuts, you get monkeys!

honey, i fried the IP Office !!!

Sarcasm, it's only one of the services I offer.

 

[Westi]

internal doesn't work for sure because you won't get the caller ID info to the system to verify that you actually are allowed to use it.
try it simple first and not as involved as you try to make it.
incoming call route with your caller ID to a shortcode *22

make a shortcode
*22
FNE
31
Line ID doesn't matter

make your caller ID a twinning number for a mobility user (or higher)
enable mobile call control

almost the same that tlpeter suggested but without the ability to pick and chose which FNE feature you want to use so it is easier to troubleshoot

Joe W.

FHandw., ACSS

 

[Escorthosis]

Be sure that your mobile sends out a caller id!. My mobile was set to send only caller id to 'known contacts'.

Another possibility could be that you haven't setup the lines correctly to add te outgoing line prefix.

Make a call from you mobile directly to your extension. Don't answer it. Try to call back your cell phonefrom the missed call logs. If this works your lines are correctly configured and all should work.

Just start Monitor and trace your incoming call to FNE it should also show a value for 'calling=xxxxx' the value xxxxx should exactly match the number entered on your user\mobile profile.

 

[4vayaMan]

There is no 9 in the Prefix for the PRI. So I would have to press 9 before I hit call off the phone logs. I will try to add that and see if it works.

 

[tlpeter]

Can you anser these questions?

Is mobile call control enabled for the user?
What is the destination in your incoming call route?


When you pay peanuts, you get monkeys!

honey, i fried the IP Office !!!

Sarcasm, it's only one of the services I offer.

 

[4vayaMan]

Sorry guys. Yes I have mobile call control checked as well as Mobile Callback.

The destination in ICR is *99

the short code in the sysem is:

*99
FNE Service
00
0

In place Ive tried 31 and 33 but no luck.

 

[tlpeter]

Try your original shortcode:

777XX
FNE
N
0


Destination 77700


What trunks do you use?


When you pay peanuts, you get monkeys!

honey, i fried the IP Office !!!

Sarcasm, it's only one of the services I offer.

 

[Chedzz]

I set this up only yesterday and it's working fine.

Short Code as TLPeter says except I've used 666XX, FNE, N, 0 (or whatever your PRI line group is)

ICR for a spare DDI with destination of 66631 (I think it needs to be 31 if you are only using Mobile Call Control)

User set to correct profile and license available for the set profile.

Mobility tab: Mobility Features ticked. Twinned mobile number set (without access code in my case and also yours from what you have said) and only Mobile Call Control ticked.

You aren't using a legacy card carrier for your PRI are you?

 

[Chedzz]

Memory may be fading but wasn't it 6.0.14 that was so full of bugs that Avaya dropped it completely without a word as to why?

I think I'd probably upgrade to 6.0.18 and try it again

 

[4vayaMan]

Amazingly it turned out to be the prefix on the PRI that fixed it. Thanks for all the tips everyone!