Hi  have you applied any filter in the LDAP synchronization on the call manager site  ... View more

voice-card 0 dsp services dspfarm ! ! ! voice service voip allow-connections h323 to h323 allow-connections h323 to sip allow-connections sip to h323 allow-connections sip to sip fax protocol t38 version 0 ls-redundancy 0 hs-redundancy 0 fallback none ! ! ! ! ! ! license udi pid CISCO2901/K9 sn FCZ173292T6 hw-module ism 0 ! hw-module pvdm 0/0 ! ! ! username SSIHD_ADM privilege 15 password 0 IPMAN%2012$ ! redundancy ! ! ! ! ! ! interface Loopback0 no ip address ! interface Embedded-Service-Engine0/0 no ip address ! interface GigabitEthernet0/0 ip address 10.36.177.3 255.255.255.0 no ip route-cache duplex auto speed auto h323-gateway voip interface h323-gateway voip bind srcaddr 10.36.177.3 ! interface ISM0/0 ip unnumbered GigabitEthernet0/0 service-module ip address 10.36.177.4 255.255.255.0 !Application: CUE Running on ISM service-module ip default-gateway 10.36.177.3 no keepalive ! interface GigabitEthernet0/1 no ip address shutdown duplex auto speed auto ! interface ISM0/1 description Internal switch interface connected to Internal Service Module no ip address ! interface BRI0/1/0 no ip address isdn switch-type basic-net3 isdn point-to-point-setup isdn incoming-voice voice ! interface BRI0/1/1 no ip address isdn switch-type basic-net3 isdn point-to-point-setup isdn incoming-voice voice ! interface BRI0/3/0 no ip address encapsulation hdlc shutdown isdn switch-type basic-net3 isdn point-to-point-setup ! interface Vlan1 no ip address ! ip default-gateway 10.36.177.250 ip forward-protocol nd ! ip http server ip http secure-server ! ip route 10.0.0.0 255.0.0.0 10.36.177.250 ip route 10.36.177.4 255.255.255.255 ISM0/0 ! ! ! ! control-plane ! ! voice-port 0/0/0 ! voice-port 0/0/1 ! voice-port 0/1/0 compand-type a-law connection plar 1700 ! voice-port 0/1/1 compand-type a-law connection plar 1700 ! voice-port 0/2/0 ! voice-port 0/2/1 ! voice-port 0/2/2 ! voice-port 0/2/3 ! ! ! ! ! ! mgcp behavior rsip-range tgcp-only mgcp behavior comedia-role none mgcp behavior comedia-check-media-src disable mgcp behavior comedia-sdp-force disable ! mgcp profile default ! ! dial-peer voice 50 voip tone ringback alert-no-PI destination-pattern 1...$ progress_ind setup enable 3 progress_ind alert enable 8 progress_ind connect enable 8 progress_ind disconnect enable 8 no modem passthrough session target ipv4:10.97.131.2 incoming called-number . dtmf-relay h245-alphanumeric codec g711ulaw ! dial-peer voice 100 pots incoming called-number . direct-inward-dial ! dial-peer voice 1 pots destination-pattern 9[2-9]......$ progress_ind alert enable 8 direct-inward-dial port 0/1/0 ! dial-peer voice 2 pots destination-pattern 905[0256].......$ progress_ind alert enable 8 direct-inward-dial port 0/1/0 prefix 05 ! dial-peer voice 3 pots destination-pattern 90[234679].......$ progress_ind alert enable 8 direct-inward-dial port 0/1/0 prefix 0 ! dial-peer voice 4 pots destination-pattern 900T progress_ind alert enable 8 direct-inward-dial port 0/1/0 prefix 00 ! dial-peer voice 5 pots destination-pattern 9[19]..$ progress_ind alert enable 8 direct-inward-dial port 0/1/0 ! dial-peer voice 6 pots destination-pattern 9[68]00T progress_ind alert enable 8 direct-inward-dial port 0/1/0 ! dial-peer voice 11 pots destination-pattern 9[2-9]......$ progress_ind alert enable 8 direct-inward-dial port 0/1/1 ! dial-peer voice 12 pots destination-pattern 905[0256].......$ progress_ind alert enable 8 direct-inward-dial port 0/1/1 prefix 05 ! dial-peer voice 13 pots destination-pattern 90[234679].......$ progress_ind alert enable 8 direct-inward-dial port 0/1/1 prefix 0 ! dial-peer voice 14 pots destination-pattern 900T progress_ind alert enable 8 direct-inward-dial port 0/1/1 prefix 00 ! dial-peer voice 15 pots destination-pattern 9[19]..$ progress_ind alert enable 8 direct-inward-dial port 0/1/1 ! dial-peer voice 16 pots destination-pattern 9[68]00T progress_ind alert enable 8 direct-inward-dial port 0/1/1 ! dial-peer voice 52 voip preference 5 destination-pattern 1741 session target ipv4:10.97.131.2 dtmf-relay h245-alphanumeric ! dial-peer voice 51 voip destination-pattern 1741 session target ipv4:10.36.177.4 dtmf-relay h245-alphanumeric ! ! ! ! gatekeeper shutdown ! ! call-manager-fallback secondary-dialtone 9 max-conferences 8 gain -6 ... View more

Cpu idle 97.03 system 00.99 Sent from Cisco Technical Support Android App ... View more

Hi im very sory for late reply . Shall i run checked via ssh to the call manager Sent from Cisco Technical Support Android App ... View more

Hi Joshua please not you need too check the following : Voice port CP tone signaling Dial plan where you want to call local, national, international ... View more

Hi Joshua Please coudl you send me waht you want to achive and this CME for which country ... View more

yes because BLF monitor is should be for DN , do you thing if i configured for hunt pilot it will work ? ... View more

Hi Roger Please did you get any news about the subject , Busy Lamp Field Call Pickup You can associate the busy lamp field (BLF) button on a              Cisco Unified IP Phone to a DN. This allows              Cisco Unified Communications Manager to notify a phone user when a call is             waiting to be picked up from the DN. The DN represents the BLF DN, and the             phone that picks up the call to the BLF DN represents the BLF call pickup             initiator. The following rules apply to the BLF DN and the BLF call             pickup initiator: The BLF call pickup initiator gets selected as the next available                     line or as a specified line. To use a specified line, the line must remain off                     hook before the BLF SD button is pressed. You can configure a hunt list member DN as the BLF DN to allow an                     incoming call to a hunt list member to be picked up by the BLF call pickup                     initiator. The incoming call on the hunt list member can come from the hunt                     list or be a directed call. The behavior in each case depends on how call                     pickup is configured for the hunt list member DN, the BLF DN, and the hunt                     pilot number. When a call pickup occurs with the service parameter Auto Call                     Pickup Enabled set to false, the phone must remain off hook or the user must                     press the answer key to pick up the call. The BLF SD button on the phone can exist in any of the             following states: Idle - Indicates that no call exists on the BLF DN. Busy - Indicates that at least one active call exists on the BLF                     DN, but no alerts exist. Alert - Indicates by flashing that at least one incoming call                     exists on the BLF DN i think for the BLF call pick goup the line should be busy then after that it will work i will tested next week , i will update , if you found something let me know please ... View more

Hi Roger Yes I agree, but if go to cisco doc for CUCM 9.1 feature call pick up, you will see they are describing this option, even they have the option call pick group inked to hunt group ... View more

Thank you for reply, I did it but the same problem ... View more

Oh Ok ok i miss that sorry , where can i find the passsword policy for the users ... View more