Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Rhinorhino on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Mobile Call Control FNE

Status
Not open for further replies.

4vayaMan

Programmer
Joined
Dec 21, 2010
Messages
232
Location
US
I had a thread about this earlier, but I have a different question regarding this. If I dial in to try and get the FNE service it will work if my mobile twinning is my cell phone...that is without a 9. If I dont have a 9 in that field then twinning doesn't work. I have the 9 prefix in my PRI line. I cant have that 9 in the field or FNE wont work, is there a way to setup my twinning to put a 9 without me actually putting a 9 in the field?
 
Tried removing the 9 on the mobile?
What typ of phone do you have? (my guess Iphone junk?)

Avaya_Red.gif

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

Dain Bramaged
___________________________________________
 
I had to read it three times and still i wonder...

Mark the right answer
You have mobile twinning on your phone? yes/no
Your mobile number for twinning has a leading "9"? yes/no
Your trunk has a "9" as prefix? yes/no
Your trunk has a "90" as a national prefix? yes/no

if you dial in to your digital extension from your cell phone the display shows "9xxxxxxxxxx" were xxxxxxxxxx is your mobile number? yes/no

If you have a NO somewere then correct that until you have all "yes
 
Yes to all of your questions. In the mobile twinning field I have 9xxxxxxxxxx - mobile twinning works fine, FNE doesn't work anymore.

If I take the 9 out of the mobile twinning field, mobile twinning doesn't work anymore, but FNE does.

I Have a DID I call into that points to *99 which goes to the FNE service. Its like my mobile number has to match what's in the twinning field. If I put my number into the "incoming caller ID" field then FNE doesn't work - if it did work, then I could just put 9xxxxxxxxxx in the incom. CID field and things might be okay. How do other people set this up?
 
try 299 instead of *99 the * could be your problem. The outside line needs to be blank or if you can't make it the first digit from you DDI/DID number. Say you DDI/DID number is 088-12345678

The 0 from 088 is removed so in the "outside line" enter the 8 and your call app number will be 8-12345678 instead of the
88-12345678

Avaya_Red.gif

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

Dain Bramaged
___________________________________________
 
I am pretty sure that Mobile Twin makes a match with at least 10 digits and the match is made from the right to the left.
It can also be that the IPO makes the match with the digits entered - if you enter 10 digits, it will match 10 and if you enter 12 digits it will match 12 digits.

But anyway - to overcome the issue that you described you should be able to use this solution:

type on the NoUser Source Number the following: -oneXdigits2match=9
This should allow the One X to make the match to the last 9 digits of the CLI received, matching to the User mobility number entered.
Do not use Merge, do a reboot.

And this should mean that it should not differ if you have your cli prefix entered or not.

maybe in your case you will need it set to 8 instead of 9, but that depends on the incoming CLI. But you can not set it too low.

Regards Lodde
 
I think I lied. I ended up sticking 9xxxxxxxxxx in the Incoming Caller ID field and it worked - thought I had tried that already but I played around with it and it worked.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top