locked
Calls from PBX to Mediation server failing RRS feed

  • Question

  • I have a mediation server and Audio Codes MP-114 connected to a PBX.  Calls from Communicator can call out through the PBX with no problems.

     

    I am trying to get calls from the PBX to connect to the Communicator.  They are failing.  They show all of the correct SIP Invites, and the call gets to the Proceeding state, but disconnects with an MP114 error showing     #0:RELEASE  GWAPP_UNASSIGNED_NUMBER :

     

    In the Enterprise Voip documentation is says:

     

    Once a primary number is chosen, it must be:

    §  Normalized to E.164 format

    §  Copied to the Active Directory msRTCSIP-line attribute.

    I think the problem may be that I don't have the msRTCSIP-line set, but I don't seem to be able to fine where this is.  I have the tel:+15305552131 primary number in the Telephone field on the General tab, but I still get the failure.  In the User and Computer snap in with Advanced options set I do not see any place for the msRTCSIP-line attribute to be set.

     

    How to I set the msRTCSIP-line to the primary number?

     

     

    Thanks

    Doug

    Sunday, April 1, 2007 3:43 AM

Answers

  • Info about the low-level inspection of msRTCSIP-* values ...

    "... A good way to test this is to run an Active Directory browsing tool
    (ldp.exe or adsiedit.msc, for example) ... Use the tool to browse to the user/contact object DN in question.
    You should be able to see all msRTCSIP-* attributes if they are set...."

    http://blogs.technet.com/toml/articles/404684.aspx

     

    It's for LCS but it may be the same for OCS.

     

    Don't use adsiedit.msc for the editing of msRTCSIP-* attributes !

     

    I hope it'll help you.

     

    Daniel

    Sunday, April 1, 2007 8:11 AM
  • Daniel,

     

    I found the msRTCSIP-line attribute using adsiedit.msc.  I did edit the value, and the calls magically worked.

     

    Thank you.

     

    I guess I still don't know how this is to be set in a normal environment.

     

    Doug

    Sunday, April 1, 2007 3:12 PM

All replies

  • Info about the low-level inspection of msRTCSIP-* values ...

    "... A good way to test this is to run an Active Directory browsing tool
    (ldp.exe or adsiedit.msc, for example) ... Use the tool to browse to the user/contact object DN in question.
    You should be able to see all msRTCSIP-* attributes if they are set...."

    http://blogs.technet.com/toml/articles/404684.aspx

     

    It's for LCS but it may be the same for OCS.

     

    Don't use adsiedit.msc for the editing of msRTCSIP-* attributes !

     

    I hope it'll help you.

     

    Daniel

    Sunday, April 1, 2007 8:11 AM
  • Daniel,

     

    I found the msRTCSIP-line attribute using adsiedit.msc.  I did edit the value, and the calls magically worked.

     

    Thank you.

     

    I guess I still don't know how this is to be set in a normal environment.

     

    Doug

    Sunday, April 1, 2007 3:12 PM
  • Hi Doug,

     

    You can set this in the "OCS 2007" Management Console.

    In the user-options (properties-additional options...), you find there "Line URI"-input field. That's the msRTCSIP-Line attribute.

     

    You can also set this field in the "Active Directory Users and Computers" Management Console. Go to the User/Properties/Communications tab/Additional options...), and you find there the same "Line URI"-input field.

     

    Regards,

    Dieter

     

    Friday, April 6, 2007 6:53 AM