locked
SfB on prem: iOS and OS X client sometimes initiate federation call instead of PSTN RRS feed

  • Question

  • Hi,

    We did set some SfB-specialists onto this but finally they came to the conclusion that this is a client-bug.

    Description:

    SfB Clients on iOS and OS X only (windows is not affected at all) sometimes do display a message "this number is not available" - but in fact it is of course. One can call by another client without any problems and you even could have been calling this number with the same client a hundred times before. But since this message appears the client will never again be able to call this number until you completely remove the App (and on OS X all Caches) and reinstall.

    We can see in client and FE-Logfiles (SIP, S4 and UCWA) that the client is initiating a federated call instead of telling the FE the "user=phone" and to send this request as a telephone number via the direct attached SIP-Trunk. So the FE looks up for e.g. "+1234567@mycompany.com" in the GA, asks the EDGE, too and both they return of course "User unknown" - which is correct, there is no such user. The client displays immediately "This number is not assigned!" and you are stuck forever. The only way is to change the notation of this number le.g. w/ or w/o contry-code or, if the callee is inside the same city, without city prefix.) Sometimes this works for a while - until the client again tries to initiate a federation call.

    Until you reinstall the App you can switch to a windows client - there we never noticed such behavior.

    Any ideas on this? Otherwise I will have to pay 299 for opening an "incident" at MS :(

    Thanks - F.One

    PS:

    - SfB Business Server 2015 Standard edition, latest CU,

    - iOS 10 & 11 Client 6.17.3.22,

    - OS X 10.12 & 10.13, Client 16.13.168

    Thursday, November 23, 2017 3:13 PM

All replies

  • Hi F.One,

    If I understand correctly,when you make a call, the call sometimes become a  federation call instead of PSTN call,so the SFB client will promopt the error messge “this number is not available”,if get this error message and call this number again,the client will stuck in this until re-install the client on IOS and OS X or initiate a federation call again.

    If so ,I cannot find any relate know issue about this problem.


    Regards,

    Leon Lu


    Please remember to mark the replies as answers if they helped.
    If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.

    Friday, November 24, 2017 3:10 AM
  • Hi Leon-Lu,

    yes, you did understand correctly - so I will open up an incident right now.

    Thanks. 

    Friday, November 24, 2017 7:21 AM
  • Hi F.One,

    If you solve the problem,please update here,it will help others who has similar issue.


    Regards,

    Leon Lu


    Please remember to mark the replies as answers if they helped.
    If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.

    Friday, November 24, 2017 8:50 AM
  • Yes, I will do. But at the very moment it is still under investigation.
    Monday, November 27, 2017 11:06 AM
  • Ok,watting for your update。


    Regards,

    Leon Lu


    Please remember to mark the replies as answers if they helped.
    If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.

    Wednesday, November 29, 2017 1:16 AM