FNE Service fail and mobile twinning 1

[martinnystrom]

Hi, we recently upgraded our pbx to 9.1.300 and after that upgrade SOME users are experiencing issues with the FNE Service.

When a user call the FNE they just recieve Busy tone. Also, when some extensions try to activate twinning they recieve "Twinning function blocked" in their 9608 display.
This is a monitor trace for the FNE FAIL

What struck me was this line
10:29:48 50468562mS PRN: CMGhostHandler : No mobility licence for Anna B-S

I have no idea what it means. Twinning is ACTIVATED with the correct number!

10:29:48 50468556mS CMLineRx: v=0
CMSetup
Line: type=SIPLine 17 Call: lid=17 id=7231 in=1
Called[0101025008] Type=Default (100) Reason=CMDRdirect SndComp Calling[xxxx@xxxx] Type=Unknown Plan=Default
BC: CMTC=Speech CMTM=Circuit CMTR=64 CMST=Default CMU1=ALaw
IE CMIEFastStartInfoData (6) 4 item(s)
IE CMIERespondingPartyNumber (230)(P:100 S:100 T:0 N:100 R:4) number=xxxx@xxxx
IE CMIEDeviceDetail (231) 0afe021500001c3f LOCALE=sve HW=15 VER=9 class=CMDeviceSIPTrunk type=0 number=17 channel=6 features=0x0 rx_gain=32 tx_gain=32 ep_callid=7231 ipaddr=xxxx apps=0 loc=999 em_loc=999 features2=0x0 is_spcall=1
10:29:48 50468557mS CD: CALL: 17.7231.1 BState=Idle Cut=1 Music=0.0 Aend="Line 17" (0.0) Bend="" [] (0.0) CalledNum=xxxx() CallingNum=xxxx@xxxx () Internal=0 Time=4 AState=Idle
10:29:48 50468557mS CMCallEvt: 0afe021500001c3f 17.7231.1 1065 SIPTrunk Endpoint: StateChange: END=A CMCSIdle->CMCSDialInitiated
10:29:48 50468557mS CMTARGET: 0afe021500001c3f 17.7231.1 1065 SIPTrunk Endpoint: LOOKUP CALL ROUTE: GID=0 type=100 called_party=xxxx sub= calling=xxxx@xxxxdir=in complete=1 ses=0
10:29:48 50468559mS CMTARGET: 0afe021500001c3f 17.7231.1 1065 SIPTrunk Endpoint: SET BESTMATCH: length 0 vs -1 match= dest=
10:29:48 50468559mS CMTARGET: 0afe021500001c3f 17.7231.1 1065 SIPTrunk Endpoint: SET BESTMATCH: length 9 vs 0 match=xxxx dest=77701
10:29:48 50468560mS CMCallEvt: Priority hike: call 1065 priority 0->1
10:29:48 50468560mS CMTARGET: 0afe021500001c3f 17.7231.1 1065 SIPTrunk Endpoint: LOOKUP ICR: DDI=xxxx CGPN=xxxx@xxxx (Destination 77701 ) => CDPN=77701
10:29:48 50468560mS CMTARGET: 0afe021500001c3f 17.7231.1 1065 SIPTrunk Endpoint: ADD TARGET (N): number=77701 type=100 depth=1 nobar=1 setorig=1 ses=0
10:29:48 50468561mS CMTARGET: 0afe021500001c3f 17.7231.1 1065 SIPTrunk Endpoint: SYS SC: 77701 5 01 sc=type=FeatureNameExtensions code=777XX, num=N callinfop->sending_complete=1 secondary_dialtone=
10:29:48 50468562mS PRN: CMGhostHandler : No mobility licence for Anna B-S
10:29:48 50468562mS CMTARGET: 0afe021500001c3f 17.7231.1 1065 SIPTrunk Endpoint: NO INITIAL TARGETS: ??
10:29:48 50468563mS CMTARGET: 0afe021500001c3f 17.7231.1 1065 SIPTrunk Endpoint: Fallback() targeting failed
10:29:48 50468564mS PRN: CDR - TCPSend maxqueuesize=500 framecount=0 operational=1
10:29:48 50468566mS CMLOGGING: CALL:2015/07/1010:29,00:00:00,000,xxxx@xxxx,I,77701,xxxx,,,,0,,"",0,n/a
10:29:48 50468566mS CD: CALL: 17.7231.1 BState=Idle Cut=0 Music=0.0 Aend="Line 17" (0.0) Bend="" [] (0.0) CalledNum=77701 () CallingNum=xxxx@xxxx () Internal=0 Time=13 AState=Dialling
10:29:48 50468566mS CD: CALL: 17.7231.1 Deleted
10:29:48 50468567mS CMLineTx: v=0
CMReleaseComp
Line: type=SIPLine 17 Call: lid=17 id=7231 in=1
Cause=17, User busy

 

[intrigrant]

If twinning is active you should see a call setup (NOT a SIP trace!) from a PARTNER:extension_number extension.
So disable SIP trace as it is not of any use here and enable the default Call trace inclusive shortcodes.

 

[martinnystrom]

The above is the trace of the use of FNE. Sorry if I was not clear.

 

[martinnystrom]

I am finding this as well MOBILE TWINNING IGNORED (NO LICENCE):

 

[intrigrant]

That is odd, mobile twinning is not licensed in 9.1. Mobile Call Control is licensed though but this is not used.
What FNE code do you use?
Did you enable Mobile Twinning when logged off?
Are you sure that the incoming CLI equals the mobile twinning number?
You are right about the trace, I did not read well, I should have taken better notice, sorry.

 

[martinnystrom]

I think these issues are close related. FNE code is 77701.

We can enable twinning without any warnings, we have tripple checked all numbers. There are no issue there and it was working flawlessly before the upgrade.

 

[janni78]

Mobile Call Control is not licensed, One-X mobile is licensed but that has to do with One-X portal.
I think you'll need Mobile Call Control active to be able to use FNE01.

"Trying is the first step to failure..." - Homer

 

[martinnystrom]

It is activated, it does not still explain why we get this error in monitor MOBILE TWINNING IGNORED (NO LICENCE): in a 9.1 installation.

 

[intrigrant]

Maybe a new "hidden feature" aka bug : only a limited number of mobile twinning users license free....
It wouldn't surprise me.
If you have IPOSS get Avaya involved.

 

[janni78]

well, there was a bug in earlier 9.1 that you couldn't add them in manager since you got a license warning so they might broken the firmware as well, wouldn't be first time.

I assume that the user in the trace has Username Anna B-S?
A longshot but try removing - , don't think it's allowed in the Username, otherwise you'll need to place a ticket with Avaya.
I haven't upgraded any live systems to 9.1 yet.

"Trying is the first step to failure..." - Homer

 

[Westi]

We are running 9.1 in our office and I use FNE all the time, but we are 9.1.0.4 so may older than your release

Joe W.

FHandw, ACSS (SME)


"This is the end of the world, make sure to buy your T-shirt before it is too late"
Original expression of my daughter

 

[Albus2]

What exactly did you enable?
You say, mobile call control is activated, but the FNE used is 01. Correct FNE for mobile call control is 31.

01 like all FNE's form 00 up to 27 are used for 'one-X Mobile client' while FNE 31-33 are used for 'mobile call control'. 01 and 31 is not the same function.
Usually we activate 'one-X Mobile client' and 'mobile call control' as well as 'twinning when logged out'. This way, you should have no problems.

...And now, while reading the fine manual - FNE 00 is 'dialtone', FNE 01 is 'steal call'. So, I assume this is your problem. I think you expect some dial tone, right?
Why did those !di*75 need to move this part out of the manager-help and only leave it in a separate PDF..?

 

[intrigrant]

For the same reason as they took out the shortcodes, the help files grew too big and they had to make a selection on what to remove.

 

[janni78]

Good thing someone is thinking =)
As Albus2 said it looks like your FNE shortcode is incorrect.

SYS SC: 77701 5 01 sc=type=FeatureNameExtensions code=777XX, num=N

That would make num=N 01 and it should be 31 to get dialtone.

You should change you shortcode to 77701/FNE/31 or point the ICR to 77731 using the current shortcode.

"Trying is the first step to failure..." - Homer

 

[EmilP]

Good imput. We didn´t notice that.
But I don´t think this is the complete solution. We had the same issue with incoming call twinning out to mobile. It wouldn´t twin out.
We ended up downgrading again to latest 9.0 and it works. Really frustrating though. I checked a server edition on 9.1.1.0 build 10 and we have the same issue there.

 

[janni78]

There is an issue with the 9.1 manager that you can't enable mobile twinning from the Manager, you need to use the phone or the Web Administration.
Don't know if they fixed it yet, to many strange issues with 9.1 so staying away from it as long as I can =)



"Trying is the first step to failure..." - Homer

 

[intrigrant]

The FNE 01 should work if there is a physical system phone active for the twinned user but I would prefer to use FNE code 00 as it provides dial tone.
It is bull stating that all FNE's from 00 upto 27 are reserved for One-X Mobile.
Long before One-X mobile was introduced we used the FNE codes 00 to 27 for mobility users and it never failed, in fact I still do on the latest version on my mobile phone ( I hate the One-X client, it consumes too much data and drains the battery ).

 

[intrigrant]

I use this since a year or three and I am very happy with it, keep it simple for a strong solution...

 

[derfloh]

I use that open on iPhone

https://itunes.apple.com/us/app/ec500/id421187871?mt=8

It's nice that you can provision the app with a XML file.

 

[Albus2]

There are two different feature sets.
FNE 00 - 27 where there first, when Symbian was a common mobile OS. FNE 00 is 'dial tone', FNE 01 is 'activ call' etc. It all works by dialing individual DID numbers for every feature. In-Call features are used by a second call, not in-band. This is also the way ACM works. The feature in 'User|Mobility|Mobility Features' is "One-X Mobile Client"
Later, FNE 31-33 where introduced with the option to control the call in-band, which is great for non-Smartphones. FNE 31, again, gives dial tone. But here it is supported to use star-star for transfer and more. The feature in 'User|Mobility|Mobility Features' is "Mobile Call Control"

I just tried this with 9.1. There is the 'problem' because not only FNE 00 and FNE 31 seem to work in the same way. Also, the check-box for "One-X Mobile Client" and "Mobile Call Control" do not work different, at least not regarding the feature to get dial tone and to use star-star to transfer the call.
Avaya may or may not 'fix' this in the future. Anyway, it's better to use the correct codes.