BFCP & cisco Callmanager

Similar Questions

• Cisco CallManager and DHCP beyond vswitch

  I have a test lab setup for our managers to call cicso 8.6 running in vmware.  Everythings upward and the work.  However, I can not all phones to pick up my 172.16.1.1 editor/dhcp server IP addresses.  DHCP works very well in the vswitch in vmware, but nothing beyond.  Maybe it's a problem with the configuration on my cisco switch, but I would check here thought incase there is something else I need to do on the vswitch.

  I can ping everything in all directions without problem.  I've got the physical hosts on the cisco switch that can ping the managers of the call and vice versa.  I guess it's a vlan tagging problem, but don't know how to solve this problem.  I do not have a router in the laboratory, only the switch that is configured as the gateway for the managers of the call.

  Call managers - 172.16.1.1 (editor) default gateway is 172.16.1.254
  ... DHCP subnet is 172.16.1.0/24
  .
  VMware vSwitch - no vlan tagging, the vswtich is set to zero (0)
  .
  Cisco 3524 - IP Vlan1 172.16.1.254
  ... The port that connects the switch to host vmware...
  switchport trunk encapsulation dot1q
  switchport access vlan 172
  switchport mode trunk
  switchport voice vlan 172
  spanning tree portfast
  ... The I have a phone plugged into the port...
  switchport trunk encapsulation dot1q
  switchport mode trunk
  switchport voice vlan 172
  .
  .

  Again, I can ping everything in and out of the switch just fine.  I can't get anything on the physical switch to pick up an address 172.16.1.1 dhcp.

  Promisc mode & forging of mac address enabled on your vswitch and portgroup - with out that DHCP does not.

• Ports of unit - is not registered & unknown status in CallManager

  The unit 4.1 (1) unified with Exchange 2003 out of area

  Sr2c CallManager 4.0 (2A)

  I've had a few calls from users today who said that their MWI has not worked. I looked in the event of the unit logs and found the event ID 126 (CiscoUnity_TSP). Then, I went to CallManager Admin and found that the port described where the newspaper was to State "unknown".

  I tried to reset the port of CCM, but nothing helped. I also have another port which is hardly used and has the value "unregistered". In addition to presenting evidence running the unit in the middle of the morning? Thanks in advance.

  Cisco Unity device - CM TSP 75 (port of Cisco Unity 71): an attempt to market the indicator message waiting (MWI) to extension 7891 failed because Cisco Unity lost connection with Cisco CallManager 10.40.0.10.

  This condition can occur occasionally in normal operation, and the MWI request will be retried once Cisco Unity reconnects with Cisco CallManager. If the MWI status remains unchanged for a long period of time or if there are a lot of these warnings from Cisco Unity in a short period of time, there may be a configuration of MWI problem or another problem.

  For more information, see the "On-hold Message indicators" chapter in the Cisco Unity Troubleshooting Guide.

  For more information, click: http://www.CiscoUnitySupport.com/find.php

  Make sure that you run the plu software recent and TSP. If you can download this at

  http://Cisco.com/Kobayashi/SW-Center/SW-voice.shtml

  Former TSP software have a history of becoming not recorded by the CTM. If you reboot the CCM server, it seems to bring back... But if update software TSP, he'll settle all this.

  Good luck

• difference between gateways, voice and Porter

  Hello

  Someone might well want explain (or provide a url link) the main difference between the voice gateways and a guard?

  Concerning

  Hello

  Your best source of information is the book of Cisco Press 'Cisco Voice Gateways and guardians (GWGK)' which explains these 2 more in detail. I have included information to help...

  The role of voice gateways:

  In a VoIP environment, voice gateways are the interface between a VoIP network and the public switched telephone network (PSTN), a private branch exchange (PBX) or analog devices such as fax machines. In its form the simplest, a voice gateway has an IP interface and a legacy phone interface, and it manages the many tasks involved in translation between protocols and transmission formats.

  At least one gateway is an essential element of any IP telephony system that interacts with the PSTN or analogue devices. In addition, when the front doors are configured correctly, many can resume when it is inaccessible to a Cisco CallManager.

  The gateway that enables communication between the two networks by performing tasks such as these:

  Interfacing with the PBX and the PSTN or IP network.

  Support IP call control protocols, more than time-division multiplexing (TDM) call control protocols.

  For calls between VoIP and PSTN closing networks and REPETITION of the call media and noting the call setup and teardown artist.

  Providing additional services, like call hold and transfer.

  Relay of DTMF multi-frequency (DTMF) tones.

  Supporting modems and analog fax via the IP network.

  In a Cisco CallManager network, a gateway must also do the following:

  -Support the CallManager redundancy in replacement of spare CallManager.

  -Support survival call when no CallManager is available.

  Gateways communicate with other gateways, guards, their end points or their control agents, such as Cisco CallManager call or a PBX.

  Protocols that use Cisco gateways for voice signaling and media are:

  Media Gateway Control Protocol (MGCP)

  H.323

  Session Initiation Protocol (SIP)

  Skinny Client Control Protocol (SCCP)

  Real-time Transport Protocol (RTP)

  The role of guardians of the voice:

  Access controllers help scale of large VoIP networks. Businesses that are geographically dispersed, networks of voice, or that have become so important that they are difficult to handle, could opt to segment their network. In a network of CallManager, you can create multiple clusters. In this case, you need to configure a full mesh of connections via the WAN IP to connect all segments or clusters. You need to configure the dialing information for each remote location on each bridge and CallManager cluster.

  It is preferable to use the guards. In a network that has doormen, trunks are necessary only for the keeper and the goalkeeper keeps information of remote endpoint.

  When you use access controllers, gateways and CallManager to register with their goalie. Doormen divide the network into 'zones', or groups of devices that fit to a particular access controller.

  When an H.323 gateway receives a call that is intended for a remote phone, he asks the guard for the location of the endpoint.

  If the call is for a different area, you can configure the guardian to allow it only if sufficient bandwidth is available. In more complex networks, you can use a directory gatekeeper to maintain information on all areas.

  You can configure routers Cisco with the Cisco IOS appropriate as guardians H.323.

  Please note the useful messages...

• 'Fail forward' for Ports on the virtual machine

  We have a customer who will be centralizing the unit with about 250 users at remote sites (4 Sites, 1000 Subscribers, they have currently a unit break at each site and want to centralize). Each site will have its own cluster of CM. I'm thinking about what I could do failure network SCOPE. Of course, each site will be fine IPT wise because they have their own cluster of CM, but VM will be declining. I think I watered but if there was a way to "transmit failure" or something on the VM ports on the PSTN to maintain the work of the virtual machine. (Of course carrier must support ISDB).

  Someone at - it works in this or thought about it?

  Andrew Dignan... If the carrier supports RDINS of course

  The connectivity of voice mail for Cisco CallManager chapter of the Cisco CallManager System Guide:

  "Inter-classes Interfaces A Cisco CallManager in a cluster can provide access to a voice mail system in another cluster, if the administrator provides the voicemail number on the trunk driver inter-classes. Voicemail systems can leave messages and sets the flags of message waiting for devices other clusters if clusters are connected by trunks QSIG. »

  This applies to any system of virtual machine. With the unit, you have of additional capacity to save ports across multiple clusters so to provide MWI without ICTS as QSIG.

  Hope this helps,

  Eric

• Unexpected phone reboot - CUCM 8.5

  I received a complaint from a user who has a few phones to one of my sites SRST restarted unexpected.  This one particularly restarted during an ongoing call.  Here's what I could find in the newspapers of Call Manager via RTMT: (the phone is - SEPD0C789D7E6D6)

  16:30:31.174 | RouteListControl::idle_CcSetupReq - RouteList(LYN-PSTN-RL), numberSetup = 0 numberMember = 1 vmEnabled = 0 | 2, 100, 13, 10100482.7625 ^ 10.93.79.6 ^ SEPD0C789D7E6D6

  16:30:31.354 | Support TEST DEBUG: Number of entries in the CallTable is = 1

  | 2 100, 13, 9987045.90003 ^ 10.93.81.4 ^ SEP1CAA0710C02F

  16:30:31.355! | ERROR! -MediaManager-(71915): wait_AuDisconnectRequest, mCleanupPreallocatedMTP = 0 | 2, 100, 13, 9987045.90003 ^ 10.93.81.4 ^ SEP1CAA0710C02F

  16:30:31.360 | MatrixControl:updatePartyMediaCoordinatorNodeId: party1 = 0, videocapable part 2 = 0 videoCapable | 2, 100, 21, 21867.9 ^ 10.93.81.250 ^ port 56110

  16:30:31.360 | ViprUtils: Count is not +, not an E164 valid [7300] | 2, 100, 21, 21867.9 ^ 10.93.81.250 ^ port 56110

  16:30:31.361 | ForwardManager - wait_SsDataInd mInterceptTable - ERROR - No entry found for ForwardKey = 0 x 25, call key = 0x73F2 | 2, 100, 21, 21867.9 ^ 10.93.81.250 ^ port 56110

  16:30:31.371 | H225D: Call forwarding and the PID of connection does not match any active process of the H225Cdpc | 2, 100, 13, 10110455.6 ^ 10.93.81.253 ^ *.

  16:30:59.852 | Support TEST DEBUG: Number of entries in the CallTable is = 1

  | 2 100, 13, 10100482.7634 ^ 10.93.79.6 ^ SEPD0C789D7E6D6

  16:30:59.852 | SdiStats: #Lines: 14 free HWM: 4 free HWM (total): 76 | * ^ * ^ *

  16:30:59.853! | ERROR! -MediaManager-(71926): wait_AuDisconnectRequest, mCleanupPreallocatedMTP = 0 | 2, 100, 13, 10100482.7634 ^ 10.93.79.6 ^ SEPD0C789D7E6D6

  16:30:59.853 | MediaTerminationPointControl (49): star_MediaExchangeAgenaCloseLogicalChannel - could not delete. PortReq not found in the list. 2, 100, 13, 10100482.7634 ^ 10.93.79.6 ^ SEPD0C789D7E6D6

  16:30:59.853 | MediaTerminationPointControl (49): star_MediaExchangeAgenaCloseLogicalChannel - could not delete. PortReq not found in the list. 2, 100, 13, 10100482.7634 ^ 10.93.79.6 ^ SEPD0C789D7E6D6

  16:30:59.920 | MatrixControl:updatePartyMediaCoordinatorNodeId: party1 = 0, videocapable part 2 = 0 videoCapable | 2, 100, 21, 21871.7 ^ 10.93.81.250 ^ 43977 by Port

  16:30:59.920 | ViprUtils: Count is not +, not an E164 valid [90689092816] | 2, 100, 21, 21871.7 ^ 10.93.81.250 ^ 43977 by Port

  16:30:59.976 | H225D: Call forwarding and the PID of connection does not match any active process of the H225Cdpc | 2, 100, 13, 10110469.18 ^ 10.93.80.249 ^ *.

  16:31:09.795 | DbMobility: could not find remdest 90677037881 in map | * ^ * ^ *

  16:31:09.795 | SdiStats: #Lines: 8 free HWM: 3 free HWM (total): 76 | * ^ * ^ *

  16:31:09.796 | RouteListControl::idle_CcSetupReq - RouteList(LYN-PSTN-RL), numberSetup = 0 numberMember = 1 vmEnabled = 0 | 2, 100, 13, 10100482.7640 ^ 10.93.79.6 ^ SEPD0C789D7E6D6

  16:31:12.381 | DeviceTransientConnection - a device has attempted to register but do not complete the registration connection Port: 2000 Device Name: AN416AFCE970002 device IP address: 10.93.81.253 type: 30027 reason Code: 3 Protocol: SCCP IPAddressAttributes:2 UNKNOWN_PARAMNAME:LastSignalReceived:StationRegister UNKNOWN_PARAMNAME:StationState:wait_register App ID:Cisco CallManager ID:StandAloneCluster Cluster ID:mrn node - cucm01 | AlarmAN416AFCE970002 ^ * ^ AN416AFCE970002

  16:31:12.380 | CcmCcmdbStationRegistrationProfile - for device AN416AFCE970002: No. Device/EmccDynamic Record for deviceName = AN416AFCE970002. Self-registration is not enabled for the type of the device. | *^*^*

  16:31:12.380 | CcmdbStationRegistrationProfileBuilder::getBasicRegistrationProfile::init() - rc (2) failure. * ^ * ^ *

  16:31:12.380 | StationD: error (10065306), ccmdbGetStationRegistrationProfile (not configured). 0, 0, 0, 0.0 ^ 10.93.81.253 ^ AN416AFCE970002

  16:31:12.383 | StationInit: TCPPid = [2.100.13.10110472] Socket broken. DeviceName = AN416AFCE970002, 10.93.81.253 = IPAddr, Port = 0xa1e7, controller of device = [2,57,10065306] | 0, 0, 0, 0.0 ^ 10.93.81.253 ^ AN416AFCE970002

  16:31:13.871 | Forwarding - getMaskedDn - maskedDn = [7000] mask [302] = dn = [7000] | * ^ * ^ *

  16:31:13.875 | RouteListControl::idle_CcSetupReq - RouteList (voicemail in France), numberSetup = 0 numberMember = 18 vmEnabled = 1 | 2, 100, 13, 10089065.18486 ^ 10.93.78.17 ^ SEPD0C789D775F3

  16:31:13.878 | CcmCcmdbHelper::buildLineStructGivenLiteDnData - getCallForwardDynamicRecordGivenNumPlanPkid() FAILED for device name(MRN-Unity1-VI1), pkid (86d8cd0f-286b-f689-4a3c-fea64a7d2c03)--> IGNORING numplan | * ^ * ^ *

  16:31:13.880! | ERROR! -ConnectionManager-wait_AuDisconnectRequest: CI NOT FOUND in the TABLE, ABOVE (44856055,0), children = 1, IFCreated (0,0), PID (0, 0-0-0), IFHandling (0,0), MCNode (0,0). 2, 100, 13, 10089065.18486 ^ 10.93.78.17 ^ SEPD0C789D775F3

  16:31:13.880 | MatrixControl:updatePartyMediaCoordinatorNodeId: party1 = 0, videocapable part 2 = 0 videoCapable | 2, 100, 13, 10089065.18486 ^ 10.93.78.17 ^ SEPD0C789D775F3

  16:31:13.881 | Support TEST DEBUG: Number of entries in the CallTable is = 1

  | 2 100, 13, 10089065.18486 ^ 10.93.78.17 ^ SEPD0C789D775F3

  16:31:13.902 | MmmanService - ERROR too large number of calls to decrementTotalNumberOfRegisteredCallingEntities, already at zero. | *^*^*

  16:31:16.883 | Support TEST DEBUG: Number of entries in the CallTable is = 1

  | 2 100, 13, 10089065.18495 ^ 10.93.78.17 ^ SEPD0C789D775F3

  16:31:16.883 | SdiStats: #Lines: 14 free HWM: 3 free HWM (total): 76 | * ^ * ^ *

  16:31:16.885 | ForwardManager - wait_SsDataInd mInterceptTable - ERROR - No entry found for ForwardKey = 0 x 25, call key = 0x73F7 | 2, 100, 13, 10089065.18495 ^ 10.93.78.17 ^ SEPD0C789D775F3

  16:31:16.885! | ERROR! -MediaManager-(71927): wait_AuDisconnectRequest, mCleanupPreallocatedMTP = 0 | 2, 100, 13, 10089065.18495 ^ 10.93.78.17 ^ SEPD0C789D775F3

  16:31:16.887 | MatrixControl:updatePartyMediaCoordinatorNodeId: party1 = 0, videocapable part 2 = 0 videoCapable | 2, 100, 13, 10089065.18495 ^ 10.93.78.17 ^ SEPD0C789D775F3

  16:31:16.888 | Support TEST DEBUG: Number of entries in the CallTable is = 1

  | 2 100, 13, 10089065.18495 ^ 10.93.78.17 ^ SEPD0C789D775F3

  16:31:39.421 | Support TEST DEBUG: Number of entries in the CallTable is = 1

  | 2 100, 13, 10100482.7653 ^ 10.93.79.6 ^ SEPD0C789D7E6D6

  16:31:39.421 | SdiStats: #Lines: 6 free HWM: 4 free HWM (total): 76 | * ^ * ^ *

  16:31:39.423! | ERROR! -MediaManager-(71928): wait_AuDisconnectRequest, mCleanupPreallocatedMTP = 0 | 2, 100, 13, 10100482.7653 ^ 10.93.79.6 ^ SEPD0C789D7E6D6

  16:31:39.423 | MediaTerminationPointControl (49): star_MediaExchangeAgenaCloseLogicalChannel - could not delete. PortReq not found in the list. 2, 100, 13, 10100482.7653 ^ 10.93.79.6 ^ SEPD0C789D7E6D6

  16:31:39.423 | MediaTerminationPointControl (49): star_MediaExchangeAgenaCloseLogicalChannel - could not delete. PortReq not found in the list. 2, 100, 13, 10100482.7653 ^ 10.93.79.6 ^ SEPD0C789D7E6D6

  Hi Jacob,

  I think that the phone has no failover to the secondary or the SRST because this failover process takes time. The phone will try to reach the primary call three times Manager before declaring the link as dead, and then try saving with its secondary server. My guess is that it reset during this time and when he returned, realized that the connectivity to the main call agent is there. He then joined the main call agent.

  This doc speaks to the behavior of IP phone. You can consult the section "failover delayed for SCCP phones."

  https://supportforums.Cisco.com/docs/doc-19066

  Thank you

  Sree

• Here Mr Lindborg? MWI question...

  Hi Jeff... hopefully :-)

  Or someone else who can help...

  I have set up a lab environment, a CM3.3, a CME3.1 and a 4.0 Server (4) of the unit.

  As I use the license of the demonstration with only two ports unit, I set up one for CME and the other for the CM, each takes and receives calls... I know this isn't 'book', but surely it should work fine for a volume of calls to one or two per hour?

  While everything seems to work fine on the surface, I noticed that any MWI/disable notification comes out two ports - I guess this is normal because the two systems will need to know, and the theory would be that one that had the DN being notified would act on the call...

  However once the notification goes to CM3.3 (the extension be informed either cm or on the CME system), but the unit will retry peristently send to the CME system up to six or so times.

  No idea why this is happening / if it is normal if it can be fixed?

  The application log records this message:

  Cisco Unity device - CM TSP 6 (port of Cisco Unity 2): an attempt to disable the indicator message waiting (MWI) to extension 1203 received no response from Cisco CallManager. The MWI OFF Extension parameter is 5081.

  Often, this condition may occur when attempting MWI is facing an incoming call on the same port, we recommend that ports setting MWIs be isolated ports handling incoming calls. However, this condition may occur occasionally in normal operation, and the MWI request will be retried. If the MWI status remains unchanged for a long period of time or if there are a lot of these warnings from Cisco Unity in a short period of time, there may be a configuration of MWI problem or any other problem.

  Thank you

  Aaron

  I am not Ms. Lindborg, but I share an office with her wall...

  I think it's because of the way in which GCE responds (or lack of response, if any) when the unit tries an MWI for an extension of the CCM. The fix for CSCed86359 should bring some relief. In the meantime, try to change the following registry key on the server unit, reboot and see if that helps to reduce the delay...

  HKLM\Software\Active Voice\Notifier\RetriesOnFailure = 1

  Finally, you are right that it is normal that the unit send MWI requests to each "cluster" defined in UTIM. Search this forum for something like 'Unit MWI Cluster' other related discussions.

  -Eric

• Install the 4.0 unit

  Someone at - it a good document for the installation of the unit with CCM 4.0? I installed MAC several times but never the unit and I am looking for some general guidelines to follow when installing the unit with CCM.

  Thank you

  Shane

  Start with the unit installation guide http://www.cisco.com/en/US/products/sw/voicesw/ps2237/products_installation_guide_book09186a00802254a5.html

  Cisco CallManager 4.0 integration for Cisco Unity 4.0 Guide

  http://www.Cisco.com/en/us/products/SW/voicesw/ps2237/prod_configuration_guide09186a00801e9e37.html

• IPCC 4.0.4 1-server for the installation procedure 2-Server w/HA

  Does anyone have the correct procedure for a Server 4.0.4sr1 monkey (still running MSDE) to a fully redundant dual server, configuration of availability very?

  Will this work?

  1. remove existing SR1 4.0.4/MSDE server (I have to?).

  2. install the SQL/Execute SQL utility on primary

  3. install CRS on the standby server

  4 install the utility SQL SQL/Run

  5 Install SR1 on both boxes

  6. active components on the standby server

  7 active Editor.

  Am I missing something? Measures of out-of-order?

  Thanks in advance

  This URL should help you:

  Release notes for Cisco Customer Response Solutions 4.0 (4):

  http://www.Cisco.com/univercd/CC/TD/doc/product/voice/sw_ap_to/apps_4_0/English/Relnotes/crs404rn.PDF

  The IPCC with CallManager compatibility in the following document.

  http://www.Cisco.com/univercd/CC/TD/doc/product/voice/sw_ap_to/crscomtx.PDF

  Release notes for Cisco CallManager 4.0 (2) on the Cisco ICS 7750:

  http://www.Cisco.com/en/us/products/HW/voiceapp/ps967/prod_release_note09186a008031486e.html

• CCM4.1 (2) sr1 with IPCC 3.5 Expr.Co-Res and IPCC Express 3.5

  Hallo,

  I installed sr1 CCM 4.1 (2) IPCC expr. 3.5 Res Co.

  Now I will connect Express.com (MCS7825) of the IPCC.

  Is it possible to run

  IPCC Express 3.5 Res Co and

  IPCC Express 3.5 (MCS7825)

  at the same time?

  Thanks in advance

  Concerning

  Hello

  You want to point living CRS and Standalone CRS on the same Cisco CallManager? If so, yes you certainly can point several CRS to CCM. But, you need a different configuration for each CRS Server profile. Profile repository can be shared between the two CRS servers.

  Concerning

  Yogi

• IPCC with other managers to call seller

  Can anyone provide information on the covering of the IPCC with the other providers (legacy) CallManager? Is there a list of suppliers that the IPCC is compatible with? What components are required for the integration/interfaces?

  IPCC is also purely based IP... IPCC can run on phones without IP (RJ45 ports)? How? -purely novice I know...

  The suite is called the IPCC when it integrates with Cisco CallManager, otherwise it is ICM. ICM's former product Geotel, which was acquired by Cisco in the end of the 1990s, it has been around for awhile and it integrates with many such as Nortel Symposium, Nortel Meridian, Concerto CLSA formerly spectrum Rockwell, Aspect, Avaya Defnity, Alcatel, Ericson, Siemens etc.

  In order to integrate these sellers next to the CIM server you PG (periphial offer) for this provider.

  Order this doc:

  http://www.Cisco.com/application/PDF/en/us/guest/products/ps1001/c1225/ccmigration_09186a008041ef29.PDF

  and this link for the integration docs:

  http://www.Cisco.com/en/us/products/SW/custcosw/ps1001/prod_technical_reference_list.html

  Chris

• JTAPI and SCI

  Hi list;

  Can one tell me why the communication between MCI and IVR via SCI and not JTAPI while communication between the Manager IVR and call is JTAPI? Also, what type of communication between MCI and call manager?

  Bilal,.

  "Note the positions" which means that if you think that the answers to your questions are right you may scores the answer. In the lower right corner, you will find a link 'Rate the post' or a drop-down list.

  About your questions, you can imagine a GP as a container of PIMs. A PIM support a connection of device to an ACD or IVR.

  For traditional CLSA or are a available in Cisco CallManager PGs specific price lists and they do not use GED125. These pages use connections of CTI to the CLSA and the CTI connection depends on the CTI link provided by CDA (Avaya-> MAPD, Nortel-> Sympoium CallManager-> JTAPI).

  Hope this helps,

  Juan Luis

• External caller ID wrong

  CUCM 10.5.2.11900 - 3, recently updated since 6. XX

  Call to a number outside a remote building, display shows the building badly on some phone operators, but it is correct on AT & T that provides our PRI lines.

  Example: Call my cell AT & T, ILA shows correct number.  Call a Verizon phone and a few other companies similarly phone and line, caller ID shows the number of the main line for high school, where all calls out the taken. Remote school calls another remote school of composition on the outside, display appears the number of high school.

  As far as I know, we did not have this problem before the upgrade.

  I checked in the models of road and the "component party transform mask" is set correctly for each building.

  Call for presentation of the line - default ID
  Call, presentation of the name - by default
  Call of Party - Cisco Callmanager Number Type
  The Party - Cisco Callmanager Dial Plan component

  Config of gateway on remote bad schools:

  Called party IE number type unknown *-Cisco CallManager
  The calling party IE number type unknown *-Cisco CallManager
  Called Numbering Plan *-Cisco CallManager
  Call for outline numbering - Cisco CallManager

  On the PRI config is:

  National
  National
  ISDN
  ISDN

  respectively for each of them.

  Am I missing other places that would cause the identification of the appellant to be bad, but only on certain carriers?  I'll put in a ticket with AT & T, but we all know how this goes without doubt.

  Hello

  ISDN IDP can be tricky at times, could you please send outputs debug debug ISDN q931 to both types of calls?

  Also, could you please change the Plan and Type as unknown and see if it makes any difference based?

  Concerning

• MWI on duplicate extensions

  I have a client with a centralized call processing model, without the site to another component. As a result, they have extensions twice in the entire company. How can I set the unit to turn on the correct MWI when there is more than one instance of a particular phone? Thank you

  Make sure that you have enabled the setting of service tenant multiple MWI on Call Manager. Here is an excerpt from the the unit-CallManager integration Guide is: "When this parameter is set to True, Cisco CallManager uses any translation scheme set up to convert extensions voicemail numbers directory during activation or deactivation of an MWI."

  -Eric

• Messaging with Nortel PBX unit

  I am currently under a double integration in my transition to IP telephony. In my current sitiation, we run a Nortel Meridian 1 Option 81C PBX as well as Cisco CallManager 4.0. They are both integrated with Cisco Unity 4.0. Our problem is that our IP phones are able to dial * then the extension and leave a message without ringing the phone. PBX users, however, are not able to do. This becomes a growing problem that we're driving on the conversion of the voicemail. A local Cisco engineer hold me it is possible to install it for the for the PBX numbering plan, but opposed our PBX technician. Can anyone send me an example of how to get this feature for all phones. Thanks in addvance.

  Nortel phones have a similar feature with the old voicemail system? Or users see this as a new feature that comes with the migration? On the side of CCM unit, it's really a feature of the telephone system. Unit is not something special for her. From the point of view of unity, calls by * [ext] exactly the same as a call that has been transferred [ext].

  If you can't similar functionality of a Nortel PBX, then here is the closest thing I can think of... define a driver that allows users of PBX to call in the greeting of the opening of the unit (instead of the sign - in conversation). From there they compose [ext] #2. This will take them directly to the greeting [Ext.] without ringing the phone.

  -Eric