Sign in
Microsoft.com
 
Microsoft
 
 
 

locked
Communicator Call from MOC Mobile R2 don't work RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi All,

    I have deployed OCS 2007 R2 FE and OCS 2007 R2 Edge Server. All services from Inside and Outside work fine.
    There isn't Mediation Server deployed, but I created a Location Profile, Normalization Rules, Phones Usages and Policies.

    Also I enabled Enterprise Voice feature to all users with their respective Line URI.

    Example:

    User1 --> +511441
    User2 --> +511442
    User3 --> +511443

    From my Communicator R2 Client I call to +511442 and user2 answer me.

    User3 is logged only on his Windows Mobile (MOC Mobile R2). Then From my communicator When I call to +511443 or User3 I hear 4 rings and then call stop, communicator show me this "+511443 cannot be reached" and "User3  annot be reached".

    Also when User3 on his windows mobile (MOC Mobile R2) can't call me (user1), His MOC Mogile R2 show this "call was unsucccessfull"

    There is an Call Option on MOC Mobile R2 where you can enter a Mobile Phone Number. What Number should I put there ?  the number of User3 (+511443).

    I put that number, but it didn't work.

    Any Ideas, please?

    Thanks.



    Monday, July 20, 2009 9:14 PM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote
    Yes, that is the Single Number Reach functionailty where the Mediation server places an outbound call to your mobile phone as well as a second outbound call to the number you've chosen, and then connects the two calls.  The ringed party sees the call coming from your work number, not your mobile number, hence the name.  At no time does the voice navigate the data network of the mobile carrier, the data network simply sets up the voice calls on the Mediation server.  The call to the cell phone still uses the carrier's cellular network.
    Jeff Schertz, PointBridge | MVP | MCITP: Enterprise Messaging | MCTS: OCS
    Wednesday, July 22, 2009 1:38 AM
    Moderator

All replies

  • Question
    Sign in to vote
    1
    Sign in to vote
    Calling from Communicator Mobile (CoMo) is not VoIP and still uses the phone's cellular carrier network to make calls. If your numbers are not normalized by the Address Book Service into a string that is understood by foreign systems (like +E.164) then calls to numbers like +511443 will fail.  You'll need to dial the full, valid DID from mobile devices (e.g. 13125511443)
    Jeff Schertz, PointBridge | MVP | MCITP: Enterprise Messaging | MCTS: OCS
    Monday, July 20, 2009 10:21 PM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi Jeff,

    Thanks for Reply. I forgot mention User3 (MOC Mobile R2) is connected to our wireless Lan and the numbers are normalized correctly.

    I'm confused, when a Internal OCS user or External OCS User calls to cell or local number, the call is routing through mediation server to PBX, and then PBX to PSTN, right?. I thought this concept applies to COMO R2.

    And why when i call to user3 (Logged on COMO R2) it fails. He must receive the call, but he don't see any information on his COMO R2.

    Thanks.

    Monday, July 20, 2009 11:41 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Jose,

    As Jeff stated above when you are transferring to a users cell phone, even when the cell phone is using MOC Mobile, you still have to actually dial there cell number. 

    To test that the cell phone portion of the call works, please dial the person's cell phone number directly.  Once that is verified, go into Communicator

    Under Tools>Options>Phones
    Configure the actual cellular number there.

    Then click on the green phone button in Communicator and chooes Simultaneously ring> and pick your mobile number.  Now dial the user's URI (or click to call them) and the cell should ring within 1-2 rings.

    Keep in mind CoMo is meant only for IM and remote call control (setting forwarding and sim ring) and not actual VoIP. 

    Hope this helps!

    -kp
    Kevin Peters MCSE/MCSA/MCTS/CCNA/Security+ blog: www.ocsguy.com
    Tuesday, July 21, 2009 2:00 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    This is actually a fairly strange way of working, in my opinion. When I am on my full Communicator R2 client, I see users that are Available - Mobile. When I click them to do a Communicator Call, I indeed cannot reach them. I have to rightclick them and say 'call on mobile' to reach them.

    Wouldn't it be more easy for users if the MOC would see that the person you are trying to reach is Mobile, and so it would forward you to his mobile automatically? Maybe this would be a nice feature for 2010?
    Ruud van Strijp - Student, doing Network Infrastructure Design in the Netherlands. MCSE: 70-270, 70-284, 70-290, 70-291, 70-294, 70-297. Cisco: CCNA, CCDA, CCNP, CCDP.
    Tuesday, July 21, 2009 1:37 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Hi Ruud,

    I don't understand something You Said "When I am on my full Communicator R2 client, I see users that are Available - Mobile. When I click them to do a Communicator Call, I indeed cannot reach them. I have to rightclick them and say 'call on mobile' to reach them."

    I had to rightclick on User that are Available - Mobile, but I didn't find "call on mobile" options.

    Regards.
    Tuesday, July 21, 2009 10:27 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Ahh, I see what you mean.  You are placing calls from a standard EV-enabled OC client, not CoMo.  The 'Phone' icon will default to the last number used to call that contact, so if you want to call a different number you'll need to use the drop-down menu to the right to select a different number (as in Mobile instead of Work), as you are doing.

    Although it might make sense to have a contact in the status of "-Mobile" default to dialing a Mobile telephone number, some deployments (and more as time goes on) are utilizing Single-Number reach and may want calls to still go to their work number as they've configured forwarding rules anyways.
    Jeff Schertz, PointBridge | MVP | MCITP: Enterprise Messaging | MCTS: OCS
    Tuesday, July 21, 2009 11:36 PM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote
    Hi Jeff,

    Here http://communicatorteam.com/archive/2008/11/26/349.aspx say that COMO R2 can receive and make call from COMO R2.

    Regards.
    Wednesday, July 22, 2009 12:47 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Yes, that is the Single Number Reach functionailty where the Mediation server places an outbound call to your mobile phone as well as a second outbound call to the number you've chosen, and then connects the two calls.  The ringed party sees the call coming from your work number, not your mobile number, hence the name.  At no time does the voice navigate the data network of the mobile carrier, the data network simply sets up the voice calls on the Mediation server.  The call to the cell phone still uses the carrier's cellular network.
    Jeff Schertz, PointBridge | MVP | MCITP: Enterprise Messaging | MCTS: OCS
    Wednesday, July 22, 2009 1:38 AM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote

    To get that 'call on mobile' option, you need 2 things:
    - Add the user's mobile number to Active Directory or the personal OCS client's field (Tools -> Options -> Phones);
    - Use Enterprise Voice combined with a Mediation server.

    To reach a non-OCS phone, you'll need a Mediation server. As a mobile phone counts as non-OCS (because CoMo doesn't really VoIP, it only does call control), you'll need to use a Mediation server to reach it's mobile cellular number.

    Ruud van Strijp - Student, doing Network Infrastructure Design in the Netherlands. MCSE: 70-270, 70-284, 70-290, 70-291, 70-294, 70-297. Cisco: CCNA, CCDA, CCNP, CCDP.
    Wednesday, July 22, 2009 7:13 AM