locked
Error while transfering a call RRS feed

  • Question

  • Hello guys,

    I'm working currently on an lync infrastructure which has a VX1200 Net gateways to connect to an old PABX.
    Everything is working fine exept the call forward from UC to internal PABX number (call forward to PSTN which is behind the PABX and the gateway is working fine).

    I made some trace with the ResKit and I found this error :

    14010;reason="Unable to find an exact match in the rules set";source="SRV-LYNC01.CCI-57.fr";CalledNumber="9404";ProfileName="DefaultProfile";appName="TranslationService"</diagHeader>

    Here is my tests :
    - I'm calling a public number from a UC Phone.
    - I'm transfering this call to an other UC Phone : OK
    - I'm transfering this call to an public number : OK
    - I'm transfering this call to a number manage by the old PABX (9404) : NOK : not working

    It's really strange because I can call this number. When I dial 9404 from the UC phone, it works fine. It's like the account was not using the same rules for transfering and for calling.

    Do somebody has already seen this ?

    Best regards
    François Tetard


    Francois Tetard | Network and Telecommunications Engineer | Axians France
    Thursday, February 10, 2011 12:31 PM

Answers

  • Problem solved. Upgrading the VX gateway solved it.
    Francois Tetard | Network and Telecommunications Engineer | Axians France
    Wednesday, February 23, 2011 6:26 PM

All replies

  • Francois,

    You should better look at the logs of the VX1200 in order to determine the root cause of the failed call. The old PBX will probably provide an error message to the VX1200.

     

    Sunday, February 13, 2011 10:18 PM
  • In fact I did a Wireshark trace on the Lync server. There is no SIP INVITE sent the VX after the PRACK... but you're right I'll do some debug at the VX level.

    Thx for your answer.


    Francois Tetard | Network and Telecommunications Engineer | Axians France
    Monday, February 14, 2011 9:45 PM
  • Problem solved. Upgrading the VX gateway solved it.
    Francois Tetard | Network and Telecommunications Engineer | Axians France
    Wednesday, February 23, 2011 6:26 PM