DX650 Directory prefers to call SIP URI

Hello,
I have some DX650's deployed, and at least one of them, when using the corporate directory to look up a user, attempts to dial that user at his SIP URI address rather than dialing the DN.  I confirmed that the telephone number in active directory is populated and it imports into the CUCM properly.
Has anyone run across this issue before?
Thanks,
Brian

Hello,
Do you know how to get the DX-650 corporate directory to show the DN/Extension of the user in search results instead of the Directory URI, or show both in the search results?

Similar Messages

  • SPA2102 with Yahoo! Voice, can't call SIP URI

    For some years I have been using Speed Dial slots to hold full SIP URI numbers such as [email protected] This was working fine until I configured Yahoo! Voice on Line_1 of my SPA2102. Line_2 can still dial these SIP URIs as it's set up with Gizmo5.
    How do I report this bug to Linksys?

    Thanks, the log shows there are some dsp errors on the lines though I'm not sure exactly what the error means - is it a hardware problem on the router or an issue with the pots lines?
    *May 9 19:51:28.247: %C5510-1-C5510_CHPI_ERROR: cHPI error for pa_bay 0 pump 0 dsp 1.
    *May 9 19:51:28.571: %FLEX_DNLD-3-ERROR_FIRMWARE_DNLD: DSP firmware download fails for slot 0 dsp_id 0
    *May 9 19:51:39.435: %C5510-1-C5510_CHPI_ERROR: cHPI error for pa_bay 0 pump 0 dsp 1.
    *May 9 19:51:39.763: %FLEX_DNLD-3-ERROR_FIRMWARE_DNLD: DSP firmware download fails for slot 0 dsp_id 0
    *May 9 19:51:50.639: %C5510-1-C5510_CHPI_ERROR: cHPI error for pa_bay 0 pump 0 dsp 1.
    *May 9 19:51:50.963: %FLEX_DNLD-3-ERROR_FIRMWARE_DNLD: DSP firmware download fails for slot 0 dsp_id 0
    *May 9 19:52:01.831: %C5510-1-C5510_CHPI_ERROR: cHPI error for pa_bay 0 pump 0 dsp 1.
    *May 9 19:52:02.155: %FLEX_DNLD-3-ERROR_FIRMWARE_DNLD: DSP firmware download fails for slot 0 dsp_id 0
    I found the following info on the errors:
    Explanation An error has occurred during initialization of the DSP in the specified slot with the application firmware.
    Recommended Action Power down, reinsert the port module, and reboot. If this message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.

  • Virtual Extension calls an external SIP URI, possible?

    Is it possible to setup a virtual extension (or dial plan normalization entry) to call an external SIP URI? For example, let's say we want Lync callers who dial '411' to reach a public SIP URI of [email protected] ? Thank in advance for your time to reply!

    It's possible by creating static route
    To configure static route, you refer below link
    http://blog.schertz.name/2013/09/selecting-matchuri-lync/
    Please remember, if you see a post that helped you please click "Vote As Helpful" and if it answered your question, please click "Mark As Answer"
    Mai Ali | My blog: Technical

  • Video conferencing and SIP URI setup

    I am new to Cisco's video products and am trying to configure them for some simple video conferencing. I currently have the following in our environment:
    CUCM v7.1.5
    VCS X7.2.1
    TMS v14.1.0
    MCU 5320 v4.3(2.17)
    EX90 vTC5.1.2
    I am also new to SIP URI dialing. I have done some base configuration on my VCS, TMS, and MCU, following the installation and configuration guide. What I am struggling with is what I need in order to set up the SIP URI info for the EX90. Does there need to be an AD account configured that has a sip directory value? Or can I just use whatever SIP address I want as long as the domain matches what I put in the VCS for the domain and allow list?
    I followed the following guides:
    TMS
    http://www.cisco.com/en/US/docs/telepresence/infrastructure/tms/install_guide/Cisco_TMS_install_guide_14-1.pdf
    VCS
    http://www.cisco.com/en/US/docs/telepresence/infrastructure/vcs/install_guide/Cisco_VCS_Getting_Started_X7-2.pdf
    http://www.cisco.com/en/US/docs/telepresence/infrastructure/vcs/config_guide/Cisco_VCS_Basic_Configuration_Single_VCS_Control_Deployment_Guide_X7-2.pdf
    MCU
    http://www.cisco.com/en/US/docs/telepresence/infrastructure/mcu/install_guide/Cisco_TelePresence_MCU_5300_Series_Getting_started.pdf
    VCS & CUCM Call routing
    http://www.cisco.com/en/US/docs/telepresence/infrastructure/vcs/config_guide/Cisco_VCS_Cisco_Unified_Communications_Manager_Deployment_Guide_CUCM_6-1_7_8_and_X7-0.pdf
    Any assistance and understanding that can be shared would be greatly appreciated!
    Thanks in advance,
    Mr. A little confused - Arras V. Martin

    Hi Arras.  Good morning.  I'm going to hopefully answer some of your questions you have here.  You also may find that the Telepresense Community on the Support Forums is a great place to post this as well. 
    First, I would recomment to you to update from TMS 14.1 to TMS 14.1.1.  There was a major scheduling bug in this release, and had to be removed and updated with TMS 14.1.1.  I would start by updating TMS to that version. 
    CUCM 7.1.5 is a bit older release.  There are some nuasances with this version that have been fixed in 8.6.2 CUCM.  Also, if running 8.5 CUCM or higher, you can add this to TMS and manage TP endpoints on CUCM via this version.  So if you have CTS endpoints or EX, MX and C-series registered to CUCM, you can manage and schedule those units in TMS. 
    Q -Does there need to be an AD account configured that has a sip directory value?
    A - If you add the device in TMS and have it registered to VCS as SIP, you can configure the SIP URI field to whatever SIP URI you wish to assign to the system.  As long as the domain you specify is part of VCS domain and your allow list pattern or rule is ok, the system should register just fine. 
    If you running SIP only environment, you can always restrict bookings in TMS to allow SIP only if this is what your gearing towards. 
    Hope this helps you out a bit.  Feel free to post any more questions here you may have and will do my best to get those answered for ya.
    VR
    Patrick

  • How does a 4G VoLTE UE know the destination SIP URI format to create the SIP INVITE

    This trace is the output from an ASR500 for a VoLTE call,
    For VoLTE the UE and IMS core network must support Public User Identities as defined in section 13.4 of 3GPP TS 23.003, which includes all of the following types of addresses:
    •Alphanumeric SIP-URIs
      sip:[email protected]
    •MSISDN represented as a SIP URI:
      sip:[email protected];user=phone
    •MSISDN represented as a Tel URI:
      tel:+447700900123
    sip:[email protected]
    In the SIP SDP you will see: sip:[email protected]
      Mobile Originating  UE:        sip:[email protected]
      Mobile Terminating UE:        tel:+14047808898
    Notice the two different formats.....
    Below in the initial SIP INVITE you will see that the MO (Mobile Originating) sends the SIP URI in  the proper format (1 of 3) to the MT (Mobile Terminating 4G  handset).
    My questions is: does the MO know the SIP URI format of the MT  (User Endpoint / 4G smartphone) because it has some sort of Address Book, or is that the designated format for a SIP INVITE   (to: tel+###########) because he MO knows the MSIDSN (tel number) dialed  .
    I do not understand how the MO knows how to format the SIP URI format of the MT (Mobile Terminating) and would appreciate any insight into this.
    PROTOCOL PAYLOAD FOLLOWS:
    2600:100c:8221:6dc9:f77a:8b7:5e38:a5d5.60717 > 2001:4888:3:fe0f:c0:105:0:17.5060: . [tcp sum ok] 1:1357(1356) ack 1 win 214 <nop,nop,timestamp 64706 423317258> (len 1388, hlim 64)
    PROTOCOL PAYLOAD ENDS.
    PDU HEX DUMP FOLLOWS:
    0x0000 30ff 0594 c20d 0073 6000 0000 056c 0640 0            ......s`....l.@
    0x0010 2600 100c 8221 6dc9 f77a 08b7 5e38 a5d5 &          ....!m..z..^8..
    0x0020 2001 4888 0003 fe0f 00c0 0105 0000 0017                ..H.............
    0x0030 ed2d 13c4 e245 e405 fcb6 417e 8010 00d6                .-...E....A~....
    0x0040 f720 0000 0101 080a 0000 fcc2 193b 4f0a                 .............;O.
    0x0050 494e 5649 5445 2074 656c 3a2b 3134 3034               INVITE.tel:+1404
    0x0060 3738 3038 3839 3820 5349 502f 322e 300d                7808898.SIP/2.0.
    0x0070 0a4d 6178 2d46 6f72 7761 7264 733a 2037                .Max-Forwards:.7
    0x0080 300d 0a52 6f75 7465 3a20 3c73 6970 3a5b                0..Route:.<sip:[
    0x0090 3230 3031 3a34 3838 383a 333a 6665 3066                2001:4888:3:fe0f
    0x00a0 3a63 303a 3130 353a 3a31 375d 3a35 3036                :c0:105::17]:506
    0x00b0 303b 6c72 3e0d 0a56 6961 3a20 5349 502f 0               ;lr>..Via:.SIP/
    0x00c0 322e 302f 5443 5020 5b32 3630 303a 3130 2.               0/TCP.[2600:10
    0x00d0 3063 3a38 3232 313a 3664 6339 3a66 3737                0c:8221:6dc9:f77
    0x00e0 613a 3862 373a 3565 3338 3a61 3564 355d                a:8b7:5e38:a5d5]
    0x00f0 3a35 3036 303b 6272 616e 6368 3d7a 3968                     :5060;branch=z9h
    0x0100 4734 624b 3030 3033 3335 3933 2d31 6361                G4bK00033593-1ca
    0x0110 6630 3633 340d 0a43 5365 713a 2031 2049                f0634..CSeq:.1.I
    0x0120 4e56 4954 450d 0a46 726f 6d3a 203c 7369                NVITE..From:.<si
    0x0130 703a 2b31 3931 3236 3735 3738 3639 4076                p:+19126757869@v
    0x0140 7a69 6d73 2e63 6f6d 3e3b 7461 673d 3534                  zims.com>;tag=54
    0x0150 3436 375f 3030 3033 3339 6130 2d33 6665                467_000339a0-3fe
    0x0160 3439 3434 380d 0a54 6f3a 203c 7465 6c3a                49448..To:.<tel:
    0x0170 2b31 3430 3437 3830 3838 3938 3e0d 0a41                +14047808898>..A

    Hi Tod,
    The "session target registrar "  point to the SIP-TRUNK to the PSTN, as detailed exaplaination:
    session target (VoIP dial peer)
    To designate a network-specific address to receive calls from a VoIP or VoIPv6 dial peer, use the session target command in dial peer configuration mode. To reset to the default, use the no form of this command.
    A ideal situation would be to use session target ipv4: of the ITSP:
    dial-peer voice 105 voip
    description **Outgoing Call to SIP Trunk**
    translation-profile outgoing PSTN_Outgoing
    destination-pattern 91%...........
    session protocol sipv2
    session target ipv4:11.11.11.11:6034 <<(1st SIP-TRUNK)
    voice-class codec 2 
    dtmf-relay rtp-nte
    no vad
    dial-peer voice 106 voip
    description **Outgoing  2ND Call to SIP Trunk**
    translation-profile outgoing PSTN_Outgoing
    destination-pattern 91%...........
    session protocol sipv2
    session target ipv4:22.22.22.22:6035 <<(2ND SIP-TRUNK)
    voice-class codec 2 
    dtmf-relay rtp-nte
    no vad
    Rate the post accordingly.
    Regards,
    Kevin

  • TCS SIP URIs drop registration

    Good Morning all,
    Have an odd issue. I have a new TCS implementation that we had installed just about 2 weeks ago. The TCS will register H.323 and SIP URIs to my VCS without issue. However, I see that the SIP URIs disappear from the VCS after a while. I haven't been able to narrow down a time-frame or activity that causes it, but as soon as I reset the TCS services, it will re-register. The H.323 registration stays without problems. Any ideas why it does that??
    VCS: X7.1
    TCS: Cisco TelePresence Content Server v5.3 Build 3316

    Hi Jaime,
    Thanks for the reply..
    Funnily enough I was thinking of something similar to your reply.. and it did occur to me how it would differentiate what resides in VC land and what is in CUCM land..
    Having a different domain name for our CUCM registered DX80 endpoints is not particularly desirable, therefore does that mean we would need to define entry for each endpoint to tell it to route towards CUCM..
    Ive made a bit of progress today but it's still messy to get it to work.. but think it touches on what your are saying..
    So...
    Dialling [email protected], hits the search rule on VCS which redirects it to the DX80 ( in CUCM land ) and our end point rings.
    Dialling [email protected], does not seem to hit the search rule on VCS ( get the error, 404 Not found ) and therefore does not get routed to CUCM.. This is strange as it is basically the same as the rule Ive created for 1001.
    ** If it did manage to hit CUCM, I would expect it to resolve to the end point 1001, as Ive created a Directory URI associating the extension and SIP name..
    As dialling [email protected] seemed to work, Ive created a new translation search rule on VCS.. So..
    Dialling [email protected] now hits a search rule,which translates the entry to…. [email protected]
    This then matches the other rule and correctly routes over to CUCM and our DX80 endpoint rings. !.
    Again, this is odd as it does prove that a variation of the [email protected] search rule does work , so I don’t understand why a simple reroute statement doesn’t work and we're having to do a translation instead !!..
    So kinda working but a very messy way of doing it…. And also we'd have to assign a static routing entry for each DX80 endpoint..
    Any thoughts please ?

  • Certain SIP URIs failing at the VCS- E

    Certain SIP URIs  are failing at the VCS-E.  The external SIP client is an Onsight application from Librestream. Onsight provides live video from a laptop or a iPhone.   The call from the OnSight application is calling a codec.  The codec is registered on TMS   VCS-E is running version 8.5.1.  Jabber SIP URIs from external users are connecting without a problem.
    Any thoughts on what is going on?  I noticed that on the Call Attempted log, that "Auth=NO".  What is this telling me?
    The incoming SIP URI is [email protected].   The destination SIP URI is jackson_ts&[email protected].  This is the alias for the codec.
    Error logs:
    2015-03-27T09:29:09-05:00 tvcs: Event="Call Rejected" Service="SIP" Src-ip="54.213.166.17" Src-port="5061" Src-alias-type="SIP" Src-alias="sip:[email protected]" Dst-alias-type="SIP" Dst-alias="sip:jackson_ts&[email protected];transport\=tls" Call-serial-number="1fa8bdc4-0c39-4273-aaab-f79a998e1b7a" Tag="40ed40f2-fd4b-4f36-a71d-99a2f127ace2" Detail="Not Found" Protocol="TLS" Response-code="404" Level="1" UTCTime="2015-03-27 14:29:09,784"
    2015-03-27T09:29:09-05:00  tvcs: Event="Search Completed" Reason="Not Found" Service="SIP" Src-alias-type="SIP" Src-alias="[email protected]" Dst-alias-type="SIP" Dst-alias="sip:jackson_ts&[email protected];transport\=tls" Call-serial-number="1fa8bdc4-0c39-4273-aaab-f79a998e1b7a" Tag="40ed40f2-fd4b-4f36-a71d-99a2f127ace2" Detail="found:false, searchtype:INVITE, Info:Policy Response" Level="1" UTCTime="2015-03-27 14:29:09,784"
    2015-03-27T09:29:09-05:00 licensemanager: Level="INFO" Detail="License granted" call_id="a6f0cd3b-6bc9-4cb3-8235-e6cb959748d4" lic_type="traversal tokens=2" UTCTime="2015-03-27 14:29:09,724"
    2015-03-27T09:29:09-05:00 tvcs: Event="Call Attempted" Service="SIP" Src-ip="54.213.166.17" Src-port="5061" Src-alias-type="SIP" Src-alias="sip:[email protected]" Dst-alias-type="SIP" Dst-alias="sip:jackson_ts&[email protected];transport\=tls" Call-serial-number="1fa8bdc4-0c39-4273-aaab-f79a998e1b7a" Tag="40ed40f2-fd4b-4f36-a71d-99a2f127ace2" Protocol="TLS" Auth="NO" Level="1" UTCTime="2015-03-27 14:29:09,713"
    2015-03-27T09:29:09-05:00 tvcs: Event="Search Attempted" Service="SIP" Src-alias-type="SIP" Src-alias="[email protected]" Dst-alias-type="SIP" Dst-alias="sip:jackson_ts&[email protected];transport\=tls" Call-serial-number="1fa8bdc4-0c39-4273-aaab-f79a998e1b7a" Tag="40ed40f2-fd4b-4f36-a71d-99a2f127ace2" Detail="searchtype:INVITE" Level="1" UTCTime="2015-03-27 14:29:09,713"
    The Search history for the call is:
    Search (393)
    State: Completed
    Found: False
    Reason: Not Found
    Info: Policy Response
    Type: SIP (INVITE)
    CallSerial Number: 1fa8bdc4-0c39-4273-aaab-f79a998e1b7a
    Tag: 40ed40f2-fd4b-4f36-a71d-99a2f127ace2
    Source (1)
    Authenticated: False
    Aliases (1)
    Alias (1)
    Type: Url
    Origin: Unknown
    Value: [email protected]
    Zone (1)
    Name: DefaultZone
    Type: Default
    Path (1)
    Hop (1)
    Address: 54.213.166.17:5061
    Hop (2)
    Address: 100.78.104.176:49482
    Destination (1)
    Alias (1)
    Type: Url
    Origin: Unknown
    Value: sip:jackson_ts&[email protected];transport=tls
    StartTime: 2015-03-27 09:29:09
    Duration: 0.07
    SubSearch (1)
    Type: Transforms
    Action: Not Transformed
    ResultAlias (1)
    Type: Url
    Origin: Unknown
    Value: jackson_ts&[email protected];transport=tls
    SubSearch (1)
    Type: Admin Policy
    Action: Proxy
    ResultAlias (1)
    Type: Url
    Origin: Unknown
    Value: jackson_ts&[email protected];transport=tls
    SubSearch (1)
    Type: FindMe
    Action: Proxy
    ResultAlias (1)
    Type: Url
    Origin: Unknown
    Value: jackson_ts&[email protected];transport=tls
    SubSearch (1)
    Type: Search Rules
    SearchRule (1)
    Name: Search VCS-C for SIP URI
    Zone (1)
    Name: Traversal Zone
    Type: TraversalServer
    Protocol: SIP
    Found: False
    Reason: Not Found
    StartTime: 2015-03-27 09:29:09
    Duration: 0.06
    Gatekeeper (1)
    Address: 10.3.70.123:25072
    Alias (1)
    Type: Url
    Origin: Unknown
    Value: jackson_ts&[email protected];transport=tls
    Jackson Prod Support Conf A
    System Type:TANDBERG Codec C40 System status:Idle Network Address:10.8.40.11Connectivity:Reachable on LAN
    Summary Settings Call Status Phone Book ConnectionPermissionsLogs
    View SettingsEdit SettingsExtended SettingsCompare SettingsPersistent SettingsTicket Filters
    Persistent Settings
    Persistent Template:
     Discovered Systems Template GSI SX-20 Template GSI SX-80 Template New Configuration Template QoS and other Basic Settings No Template 
    System Name:
    Current System Name:
    Jackson Prod Support Conf A
    E.164 Alias:
    Current E.164 Alias:
    1704826
    H.323 ID:
    Current H.323 ID:
    [email protected]
    SIP URI:
    Current SIP URI:
    Jackson_TS&S_Room [email protected]

    Because this is the VCS-E search history, we can't see what is happening on the VCS-C, can you please upload the rest of the search history for this call from the VCS-C as well?
    I looks like the Onsight application is appending ;transport=tls to the dialed SIP URI, and the VCS is reading that as a part of the SIP URI and it might not be able to locate the registration with it added.  If you can't get the Onsight application to drop ;transport=tls part, you might be able to create a transform that will remove it for you - see below.
    Pattern type:  Suffix
    Pattern string:  agcocorp.com;transport=tls
    Pattern behavior:  Replace
    Replace string:  agcocorp.com

  • Using SIP URI address as phone number (possible?)

    Hi
    It appears the SPA525G2 supports direct SIP URI, however as this phone is part of the UC320w system, is there a way of storing and dialing the SIP URI "number" for someone?
    Second to this is the UC320w able to receive a call like this from another phone server using the SIP URI as a call method (I know SNOM does it, also sure 3CX does as the SPA9xx series think will also do as well as the SPA525G2 phones)?
    I would like to give this out as well as a "BELL" traditional phone number, i assume i wont need a VoIP provider for this as it would be direct method of contact.

    Hi Ashley,
    UC320W doesn't support SIP URI dialing and receiving.
    Regards,
    Wendy Yang

  • How to create a SIP URI speed dial

    Hi - I would like to set up speed dials to SIP URI's (as opposed to a phone number).
    Does anyone have an example of how the URI is specified in the web config screen and whether I need to then include a dial plan to handle the [email protected] URI. Thanks

    IP dialling is enabled.
    This is an example SIP URI (the Lenny URI :D)
    sip:[email protected]
    So what would the syntax for a speed dial be ?
    Extended Functions:  fnc=sd;sub=sip:[email protected];ext=sip:[email protected]

  • Is Preferred vendor approved automatically. Is preferred vendor called VL

    Hi friends
    Is Preferred vendor approved automatically. Is preferred vendor called Vendor List.
    Regards
    Surya
    Edited by: surya K on Dec 29, 2008 4:03 PM

    Hi Surya,
    Whenevr you do "SHOP", under source of supply system will propose preferred vendor based on the list which we maintained on product level or product category level....if we not maintained these lists then system will propose you the last vendor of shopping cart.....
    Thanks
    Ravi

  • Mapping application instance to SIP URI in OCCAS 4.1

    Hi all,
    I need to map application instance to SIP URI on Presence SIP plugin. I input application instance as 'domain_user' but I'm not sure what to put for the SIP URI.
    My guess for SIP URI is 'sip:127.0.0.1:5060', is this correct ?
    Any help would be greatly appreciated.
    Regards,
    Setya

    Hi all,
    I need to map application instance to SIP URI on Presence SIP plugin. I input application instance as 'domain_user' but I'm not sure what to put for the SIP URI.
    My guess for SIP URI is 'sip:127.0.0.1:5060', is this correct ?
    Any help would be greatly appreciated.
    Regards,
    Setya

  • SIP: Choosing sip account from SIP URI

    It is possible to store arbitrary strings in vcards, for example sip:[email protected], but unfortunately the inbuilt SIP client seems not to parse the URI and tries to reach myfriend at someregistrar.com, but uses the default account for all calls.
    Is it possible to select the SIP account for outgoing calls on a call by call basis? Using IP adresses for calling should be possible as well, e.g. sip:192.168.1.1.
    Is it possible to reach the phone via SIP even when it is not registered - most SIP clients are reachable via their FQDN/IP address
    Thanks!
    Nokia E51

    Flodis79,
    No need to delete/add anything repeatedly. You can do that but as you mentioned it's not easy.
    I'm not doing this under "Settings". I only use settings to define the two SIP accounts (VoipBuster and TruPhone). For example Menu->Tools->Settings->Connection takes me to where my "SIP Settings" and "Internet tel. settings" can be changed. Not talking about modifying these at all. However, your SIP Settings for both providers needs to be set to Registration == "always on" if you really want this to work as I stated in my original post.
    Where I'm switching is:
    Menu->Connect->Internet tel
    When you do this it may say "Discovering services" and takes a few seconds. When that's done you will see a message pop up if you are already connected. In my case I see "Already connected to TruPhone and VoipBuster". The message will go away and there is an "opions" button in the lower left corner.
    Select it and you should get a menu that says:
    Connect to service or Disconnect from serv
    Change service
    Refresh
    Settings
    Help
    Exit
    The "Change service" is what I use to do what you are asking about. The "Connect to service" or "Disconnect from serv" option just depends on you current state.
    So in my case I just click change service and a list will pop up with the Net call service to use:
    TruPhone
    VoipBuster
    Just pick the one you want and that's it. Go to your phone book and make your call. Switch between the two providers between calls.
    You don't need to "Disconnect from serv" to change it. Just another option if you already have an active profile want to stop using a profile. Also, if you select Connect to service and your SIP profile Registration is set to "Always on" it will get changed to "When Needed" for some reason? Took me a while to figure that out.
    Does that help?
    Also, you don't need to store two versions of the same phone number for each SIP account. Just put the phone number in your address book and the client will add the @sipProvder.com to the phone number when you make an Internet call.

  • External Calls , SIP Setup.

    So far I have a 2811 setup with a few CIPC softphones. This is working fine.
    What i'd like to do now is set up calling to external phones. We have set up a voip account with a company and have the following details. SIP username, SIP Password and SIP Proxy.
    How can i go about using this to connect to an external number? The reason i'm asking for online documentation and help is that the company said they'd assist in setting it up , but they've been a little slow so far.
    Many Thanks.

    Sorry I should have been more thourough.
    Software Version 12.3(11)T10 / CME 3.2

  • Active Directory integration with call manager

    Hi,
    I am facing issues while Integrating the CCM to my Active Directory using AD Plug-in.
    SITE SETUP:
    1. Windows 2003 Parent Domain Controller located remotely with GC.
    2. Windows 2003 Child Domain for the Parent DC located Locally with GC.
    3. Cisco CallManager 4.1.3 sr3b
    My Requirement is to integrate CCM with my Windows 2003 AD.
    My Questions are:
    1. Do I need to Provide the Parent Domain name or the Child Domain name while performing the AD Plug-in Setup?
    2. Does my Call Manager need to have the Forest access of the Active Directory (i.e., Does it perform some modifications in the Parent Domain)?
    3. Does the user account (which is used for Directory Integration) need to have direct members of Schema Admins or thru some other domain admin groups (i.e., Admin user -> Child Domain Admins Groups -> Parent Domain and Schema Admin Groups)?
    Can anyone can help me on this?
    Thanks,
    V.Kumar

    1. Do I need to Provide the Parent Domain name or the Child Domain name while performing the AD Plug-in Setup?
    Use the root domain, in this case the Parent domain.
    Cisco does not recommend having a Cisco Unified CallManager cluster service users in different domains because response times while user data is being retrieved might be less than optimal if domain controllers for all included domains are not local.
    2. Does my Call Manager need to have the Forest access of the Active Directory (i.e., Does it perform some modifications in the Parent Domain)?
    Yes, actually all domains in the forest share the same Schema, which will be modified after running the AD plugin.
    3. Does the user account (which is used for Directory Integration) need to have direct members of Schema Admins or thru some other domain admin groups (i.e., Admin user -> Child Domain Admins Groups -> Parent Domain and Schema Admin Groups)?
    Account should be a member of the Schema Admins group in Active Directory, try the one in parent domain.
    Correct permissions for CCMAdministration and similar example for your setup:
    http://www.cisco.com/en/US/products/sw/voicesw/ps556/products_implementation_design_guide_chapter09186a00806e8c04.html#wp1043057
    HTH

  • Does anyone know Directory Utility is called on a Dutch system?

    I'm trying to install a MAMP on my system and I've found a tutorial on Internet that says that I have to open the Directory Utility in System > Library > Core Services (in Dutch: Systeem > Bibliotheek > CoreServices) but I can't find the Directory Utility. I assume that this is translated to Dutch since I'm using a Dutch system.
    Does anyone know what is called?

    Thanks, for looking. But I've found it: "Adreslijsthulpprogramma".
    (It's a bit off a stupid translation if you ask me)

Maybe you are looking for