locked
[OCSR2] Cannot add second telephony participant RRS feed

  • Question

  • Hi,

    This is an OCSR2 deployment integrated with Cisco

    Scenario: User A calls number +123456, talks, and invites phone number +6544321

    The +6544321 person won't be invited with error:

    Cannot perform the selected action. This action may not be permitted by the conferencing service

    No errors are on tracing logs from client or server, and the +6544321 call is never placed to the Cisco PBX (never goes through it)

    If I first invite an internal OCS user, likes this

    User A calls User B, User A calls number +123456, talks, and invites phone number +6544321

    it works.

     

    I see that this is described here http://social.technet.microsoft.com/Forums/en-US/ocsconferencing/thread/508c7eb2-4f5c-4ed8-8b45-6c7dda87411d/ with no resolution.

     

    Can you guide me on what is causing this behaviour?

    Thanks

     

    Friday, October 28, 2011 6:48 PM

All replies

  • Hi,

    can you run Wireshark on Mediation Server and try the scenario once again? get an incoming call from PSTN, try to add another PSTN number to the call.

    Chek the Wireshark for any problems. i had the same problem and turns out my SIP connection to my IPPBX does not recognize my SIP "From" address which seems user@domain.com. so i had to add another SIP connection as the same setup but changing the address context to domain.com and it workd

    Thamara.

     

    Saturday, October 29, 2011 3:29 PM
  • Hi,

     

    wich integration with Cisco do you use? Direct sip ore RCC?


    regards Holger Technical Specialist UC
    Sunday, October 30, 2011 9:12 AM
  • Hi,

    First, you need to eliminate the if it is cisco pbx problem. Please invite two PSTN call to test it.

    If you install your OCS r2 in windows 2008 r2, it also cause this issue. Please read the following article, download and install the hotfix KB975858 to verify if the problem occurs again:

    http://support.microsoft.com/kb/975858#Manifests


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
    Monday, October 31, 2011 7:47 AM
  • Sean, It is not an R2.

    Holger, It is Direct SIP.

    Thamara, I'll run it and let you know I think that you had a similar scenario like the one I am experiencing. Could you explain a little more about address context change you did?

     

    Thanks!

    Monday, October 31, 2011 6:34 PM
  • Basically it's the SIP domain part. the usual address of the invite is sip:+1122334456@<IP>;ext=xxxx. but when you add add another party to the conference, Lync send the user name like, sip:firstname.lastname@domain.com;ext=phone in "from" part. the problem was that my gateway was not configured do handle the @domain.com context in the inbound invite. once i configure it, i was able to add PSTN numbers to the conference.

    Thamara.

    Tuesday, November 1, 2011 1:52 AM
  • I understand, I think that is exactly what is happening here.

    Can you guide me on how you configure the gateway to handle that phone context?

    I really appreciate your help,

    Tuesday, November 1, 2011 11:53 AM
  • In my gateway, when i create a SIP Route, i have 2 entries. 1 is Session Target it's like (172.20.10.61:5068;transport=tcp) and the other one is Remote address context that is actually the FQDN of the 172.20.10.61 (IP Of my Mediation Server) or can be @doamin.com where the "domain" is the domain that my Lync server users are enabled in.

    basically what you need to get the gateway configured to accept the incoming connections which have @domain as the remote address context other than it's IP address

    I'm not a Cisco Expert but it should be doable with Cisco as well.

    Thamara.

    • Proposed as answer by Sean_Xiao Thursday, November 3, 2011 1:24 AM
    Tuesday, November 1, 2011 5:03 PM
  • Let me check that, also I read that this could happen if media termination point is not configured.
    Thursday, November 3, 2011 5:17 PM
  • check and let us know :)

    Thamara.

    Thursday, November 3, 2011 5:19 PM