none
cannot transfer a conference call to another pool RRS feed

  • Question

  • I have 2 lync pools, one in the USA, and one in China, and we are testing out dial in conferencing, which works if we use a conference ID from a user in the China pool, but if we use a conference ID from the USA pool, and the user dials in via the number for China, the conference attendant answers then says "We cannot connect you to your conference, bye". Here is the sip error I see, and its the only error that i see (nothing in event log on either pool)

    TL_INFO(TF_PROTOCOL) [1]0924.09C8::09/15/2011-14:11:17.498.00004b05 ((Shared),SipMessage.DataLoggingHelper:sipmessage.cs(613))[1831229087]
    >>>>>>>>>>>>Outgoing SipMessage c=[<SipTlsConnection_2699D09>], 10.x.x.x:54783->10.x.x.x:5061
    BYE sip:chinapool.internal.domain.com@domain.com;gruu;opaque=srvr:MediationServer:_cRGGrNiDlClcFpBc0SURAAA;grid=11053a7999ad4251a36a81cdc1a1e69c SIP/2.0
    FROM: <sip:conferencenumberchina;phone-context=DefaultProfile@domain.com;user=phone>;epid=A2E32B3D02;tag=69fa8967b
    TO: <sip:mycellphone;phone-context=DefaultProfile@domain.com;user=phone>;epid=5355FB0112;tag=1195996536
    CSEQ: 2 BYE
    CALL-ID: c0fef834-9a9e-42aa-b2a5-5a1c94dee4f8
    MAX-FORWARDS: 70
    VIA: SIP/2.0/TLS 10.x.x.x:54783;branch=z9hG4bK83884fbd
    ROUTE: <sip:chinapool.internal.domain.com:5061;transport=tls;opaque=state:F;lr>
    CONTACT: <sip:chinapool.internal.domain.com@domain.com;gruu;opaque=srvr:Microsoft.Rtc.Applications.Caa:MkUqwj7HWlK-Z-mxC4fWYQAA>;automata;actor="attendant";text;audio;video;image
    CONTENT-LENGTH: 0
    PRIORITY: Normal
    SUPPORTED: ms-dialog-route-set-update
    SUPPORTED: gruu-10
    USER-AGENT: RTCC/4.0.0.0 Conferencing_Attendant_1.0
    P-ASSERTED-IDENTITY: "Company Dial-in Conference Beijing"<sip:conferencenumberchina@domain.com>,<tel:+conferencenumberchina>
    ms-diagnostics: 33038;source="chinapool.internal.domain.com";reason="Cannot transfer the call to another pool.";component="urn:application:Caa";ConfID="52350";ConfURI="sip:me@domain.com;gruu;opaque=app:conf:focus:id:NOBF785M";CompatMode="14";AttemptedConfID="52350";IsAuthenticated="False";AcceptCall="1401ms";ResolveConference="2446ms";GetConferenceInfo="303ms";InterpoolTransfer="368ms";DestinationUri="sip:usapool.internal.Company.com@domain.com;gruu;opaque=srvr:Microsoft.Rtc.Applications.Caa:qhDp-4PBHl2cr4wZ38KHCwAA"
    Ms-Conversation-ID: 6c329e9671184df59fbf1634264bc8fc
    ------------EndOfOutgoing SipMessage

    Thursday, September 15, 2011 2:56 PM

Answers

  • yes we fixed the issue. It turns out in china the call manager was version 7.1 and the admin there had enabled refer support, while in the USA we were at 6.1 and had to disable refer support.  Once we disabled refer support on the trunk in china, everything started working again.
    • Marked as answer by Pantherfan Tuesday, September 27, 2011 1:16 PM
    Tuesday, September 27, 2011 1:16 PM

All replies

  • Hi,Pantherfan,

    It seems you have assigned different conferencing policy for the two pools,would you please compare the two pool conferencing configuration?

    And the information you provided is limited to troubleshoot this problem,please elaborate more on your Lync topology and backround environment for more information to troublshoot. Thanks in advance.

    Regards,

    Sharon

     

    Monday, September 19, 2011 10:14 AM
    Moderator
  • Hi,Pantherfan,

    Have you fixed the issue?

    Any updates please do let me know.Thanks!

    Regards,

    Sharon

    Thursday, September 22, 2011 9:25 AM
    Moderator
  • yes we fixed the issue. It turns out in china the call manager was version 7.1 and the admin there had enabled refer support, while in the USA we were at 6.1 and had to disable refer support.  Once we disabled refer support on the trunk in china, everything started working again.
    • Marked as answer by Pantherfan Tuesday, September 27, 2011 1:16 PM
    Tuesday, September 27, 2011 1:16 PM