Inter cluster calling

Hi ,
We have 4 CUCM (7.x) cluster for four regions. Each cluster has 1 Pub. And 3 Subs. I want to enable inter cluster calling because all regions are at our MPLS Network.
Kindly suggest what to do to enable calling across 4 regions.
Regards,
Soni

Hi,
this is the "Contact Center" forum, your post would get better exposure in the "IP Telephony" section, but anyway. The easiest thing would be to set up intercluster trunks between clusters, and perhaps use Locations-based CAC to control the number of calls.
Or, a bit sophisticated approach: use a Gatekeeper (or a cluster of gatekeepers) to decide where to route the calls. You may also use Locations-based CAC or Gatekeeper CAC (or their combination).
G.

Similar Messages

Callmanager make the ONnet/Offnet between inter-cluster.

Hi,
I know that the onnet/offnet function can prevent the conference call between outside call to outside call. But i want to run the function between to inter-cluster. If the call from other clusters to call in which is on net phone. it can provide the function. but if the call call in from other cluster which is outside call in. I can separate this traffic by onnet/ off net ?
CCM versiion of Both clusters is 4.13sr3c

Try this link for more information
http://cisco.com/en/US/products/sw/voicesw/ps556/products_administration_guide_chapter09186a00803edae2.html

No Inter-Cluster RTP Stream with Gatekeepers

Hello,
Firstly I am no expert in Cisco telephony as we have just recently migrated to a full Cisco solution, so apologies if I ask a fundamental question.
Client A = Site A
Client B = Site B
Client C = Site C
Site A and Site B are in 1 cluster
Site C is in another cluster
Intra-Cluster Traffic Works
Client A -> Client B within the same cluster (across 2 sites with a low latency link) RTP stream comes up and the call functions as expected.
Inter-Cluster Traffic Fails (GK to GK)
Client C -> Client A this works, the RTP stream comes up and the call functions as expected.
Client A -> Client C this call connects but there is no RTP stream.
We are using G711 across the board and I have captured a wireshark capture from a Client A -> Client C failed call.
I have been going through this capture and noticed that when I search H225 (for the gatekeepers) I see the following –
CS: setup
RAS: admissionRequest
RAS: admissionConfirm
CS: callProeeding
CS: alerting
CS: notify
RAS: registrationRequest
RAS: registrationConfirm
CS: notify
CS: connect
CS: notify
CS: releaseComplete
RAS: disengageRequest (DISCONECT_REASON=2,TIME=1321266127,DURATION=24,DISCONNECT_STRING=no resource,ORIGIN=0,LINE_NUMBER=GK,OUTBUND_GW_IP=..
RAS: disengageConfirm
There are firewalls inbetween and these were the first thing I looked at, but I dont even see any RTP stream trying to be initiated from the far side. Would anyone have any ideas where I could start looking?
Thanks,
Peter

Pat,
I can not talk to the UC540, but I ran into a situation recently where the SIP gateway was sending out the private extension of the phone number instead of the full DID that was registered to the provider. The provider was then blocking call.
In our SIP debugs we saw the RDNIS information of the private extension I believe. The error code we were getting back from SP was code 404 or something along those lines.
I recommend you do some debugs and track where the calls fails, compare the SNR call versus a normal call in the debugs, and then if you still get stuck post running configs and debugs back here.

Callmanager Inter cluster trunk - 6608 MGCP problem

Hi
We have two callmanager clusters linked together with an Inter cluster link and then there is a 6608 GW registered with one cluster here below is a logical ASCII drawing of the setup.
6608--Cluster1--Cluster2
Calls that are made to and from the Cluster1 that the GW is registered to work fine.
But calls that are made to and from the Cluster2 that is on the other end of the Inter cluster trunk ring once and are then disconnected.
I have gone over all codec settings for all the regions and they are all set to G711.
I also tried the same thing with a H323 GW like this.
H323GW--Cluster1--Cluster2
And then all calls work fine.
If anyone has any clue on this I would really appreciate some input.
Kind regards
Gudmundur Thor Johannsson

Sounds like MGCP is not supported on callmanager for inter-cluster gateway . Or it could be a bug. Any thoughts?????

Inter cluster trunks

Is it possible to conect a intercluster trunk between the following 2 CUCM versions
version 5.1 and version 8.5?
All routing is correct and wokting fine however the inter cluster trunk will not allow calls to go through.
Dialed number analyzer confirms the path of teh call is reaching the inter cluster trunk
WHan adding a route pattern to the trunk the status and ip address changes to unknow within the version 5 cucm?

Yes, you can create ICTs from CUCM 5.1 and 8.5. When you create these trunks, it is as good as adding a H323 trunk. Therefore the trunk status would show unknown.
On calls not going through, you might want to consider the number of digits being dialed and what is being sent across the trunk. Also, what message do you get on the call when you dial through the trunk ?

Inter Cluster Trunk DisplayName and AlertingName issue

Hi All
I have an inter cluster trunk between two cluster , one is version 9 and other is 7.
When version 7 phone calls version 9 phone, the Alerting Name on version 7 Phone is not displayed.
When version 9 Phone calls version 7 Phone, the Display Name on version 7 Phone is not displayed.
Any idea?
Fei

Hi,
Can you please change the Service Parameter "Always Display Original Dialed Number" to "False" in the 7.x cluster and try again?
Regards,
Tere.
Please rate useful posts.

IPIPGW and Inter-Zone calls using NetMeeting

I'm using Netmeeting to test inter-zone calls through an IPIPGW. The IPIPGW registered in the zone0-gk zone should be used to establish the calls between zones.
I have two local zones, zone1 and zone2 and I'm using NetMeeting to test basic connectivity, with one endpoint (1000) registered in zone1 and another (2000) in zone2.
When a call is placed from 1000 to 2000 a call arrives at 2000 from the ipipgw. When this is accepted, another call arrived from the endpoint itself. (The same occurs in the opposite direction).
I'm not sure whether this is a configuration error with the IPIPGW/GK or a feature of NetMeeting.
voice service voip
allow-connections h323 to h323
h323
interface Loopback0
description IPIPGW/GK Source Interface
ip address 10.0.0.10 255.255.255.255
h323-gateway voip interface
h323-gateway voip id zone0-gk ipaddr 10.0.0.10 1719
h323-gateway voip h323-id ipipgw
h323-gateway voip bind srcaddr 10.0.0.10
interface FastEthernet0/0
ip address 192.168.0.100 255.255.255.0
ip route-cache same-interface
duplex auto
speed auto
dial-peer voice 1 voip
destination-pattern 2...
session target ras
codec transparent
dial-peer voice 2 voip
destination-pattern 1...
session target ras
codec transparent
gateway
timer receive-rtp 1200
gatekeeper
zone local zone0-gk test.com 10.0.0.10 invia zone0-gk outvia zone0-gk
zone local zone1 test.com invia zone0-gk outvia zone0-gk
zone local zone2 test.com invia zone0-gk outvia zone0-gk
no zone subnet zone1 default enable
zone subnet zone1 192.168.0.14/32 enable
no zone subnet zone2 default enable
zone subnet zone2 192.168.0.18/32 enable
zone prefix zone1 1...
zone prefix zone2 2...
no use-proxy zone1 default inbound-to terminal
no use-proxy zone1 default outbound-from terminal
no use-proxy zone2 default inbound-to terminal
no use-proxy zone2 default outbound-from terminal
no shutdown

I have since tried this using OpenPhone instead of NetMeeting (just in case this was a NetMeeting issue, but I am still unable to use the IPIPGW to get up a video call between two local zones.
One OpenPhone believes it is transmitting video data, and the other believes it is receiving video data, but the receiving OpenPhone doesn't display the video (which is consistent with the behaviour observed with NetMeeting). The audio is working.
The output of "show call active video" shows the inbound and outbound audio legs, but only the outbound video leg, not the inbound leg:
Outgoing Channel Number = 259
Type = VIDEO
TX Bandwidth = 8250
RemotePort = 49590
LocalPort = 17538
SelectedQos = best-effort
Incoming Channel Number = 258
Type = AUDIO
RX Bandwidth = 63
RemotePort = 49592
LocalPort = 16766
SelectedQos = best-effort
Outgoing Channel Number = 258
Type = AUDIO
TX Bandwidth = 640
RemotePort = 49592
LocalPort = 16766
SelectedQos = best-effort
Examples on CCO show configurations for using the IPIPGW between an endpoint in a local zone and a remote zone endpoint. I'm unable to find any examples of the use of IPIPGW to set up a call between endpoints in local zones.

Call preservation with Gatekeeper controlled inter-cluster trunks on CM8.5

Is call preservation possible with gatekeeper contolled ICT on CM 8.5 when a subscriber goes down? My testing shows the call drops. Can this be corrected?

In the Service Parameters for CUCM H323. Make sure the Allow Peer Preserve H.323 Call is set to True. By default, its False. I noticed this on my H323 gateways I just migrated... dropped CUCM and my calls dropped when they should have stayed up, but did not. See that helps on the GK

CallManager 4.1(3) - Inter-cluster Trunk (ICT) behaviour and config

Hi Guys,
Trying to get some clarification on this. Currently chasing a few different avenues. If anyone knows of some good detailed docco on this (have tried the standard stuff). Or if anyone has any best practice advice, otherwise any one have any comments or insight on the following conversation:
Stage 1 describes the impact of the device pool setting, which is basically how the local CallManager is selected to process the call.
Stage 2 describes how the local callmanager selects the remote destination callmanager
Stage 1 - Phone on side A attempts to make a call to phone on cluster B
If the source phone is in the same device pool as the ICT on cluster A, then the call will be processed by the primary ccm for that device pool. (assuming it is available)
- It will be processed by the Call Manager is homed to rather than the primary Call Manager.
If the source phone is in a different device pool than the ICT on cluster A, then a random ccm in the ICT config will be selected. (Have asked for clarification here)
- Yep, the docs actually say "Selection of Cisco CallManager nodes occurs in a random order"
Stage 2 - One of the Callmanagers in cluster A now has the call to send to the remote cluster B. This is where your ICT config of the 3 callmanagers comes in. The Callmanager will use a round robin basis to select the destination callmanager.
I am still running with this, but initial thoughts are that if your phones are in the same DP as the ICT, then you are basically going to end up with the primary ccm in that DP processing all the calls. In this instance the primary CCM still selects the remote destination callmanager via round robin basis, so the calls will be distributed fairly evenly to the 3 destination servers.
- Not sourced from primary as stated above
- A key point is for them to understand is that all the Call Managers configured in Cluster A ICT must be in the same device pool in the remote cluster B, and the ICT must also be a member of that device pool. So, if they configure CMgr 4 to be a target device within the ICT configuration, yet CMgr 4 isn't a member of the remote ends ICT device pool they will get failing calls. This is because CMgr 4 will receive an H323 call (H225 signalling) from a source IP address that it knows nothing about and hence the H225 daemon will reject the call. Not sure how the local call Mgr handles the rejection of call.
If you wanted to balance the call processing on the local side. I.e. instead of always selecting the primary CCM in the device pool and therefore splitting the call processing amongst the 3 local ccm's in a random fashion. Then you would want to put your phones into a different device pool than the ICT. This will mean that the local callmanager is selected at random.
- Well maybe, random may not mean truely random so they'd just have to give it a go and monitor it. However, it's unclear at this time if the monitoring tools tell us how many outgoing vs incoming calls are processed, and you need to understand this to determine the outgoing loading of each Call Manager. The CallsActive counter registers both incoming and outgoing calls hence you can't really tell. To monitor it for sure they could set up two ICTs, one for incoming calls on for outgoing then at least the loading would be a little clearer. I think the only overhead here is the config effort which shouldn't be too tricky.
The interesting thing is the "random" part. It doesnt make a lot of sense considering device pools are the perfect place to manually distribute the load evenly. I.e. if I had 3 device pools for the end phones, each of them using a different callmanager as it's primary call processor in the CallManager groups.
- Agreed although I would say the usual top down and circular algorithms should be available.

Trunk configuration in Cisco CallManager Administration depends on the network design and call control protocols that are used in the IP WAN. All protocols require that either a signaling interface (trunk) or a gateway must be created to accept and originate calls. For some IP protocols, such as MGCP, you configure trunk signaling on the gateway. You specify the type of signaling interface when you configure the gateway in Cisco CallManager. For example, to configure QSIG connections to Cisco CallManager, you must add an MGCP voice gateway that supports QSIG protocol to the network. You then configure the T1 PRI or E1 PRI trunk interface to use the QSIG protocol type
This URL should help you:
http://www.cisco.com/en/US/products/sw/voicesw/ps556/products_administration_guide_chapter09186a00801ec5ce.html

JBoss cluster - call to a specific node

Hi!
is it possible to send a remotecall only to a specific node in the cluster?
Simple example:
I have three nodes in my cluster (A, B, C) and i want to send a call only to an object on node C. Node A and B shouldn't be involved in this call.
Best Regards
Hendrik

Hi,
Assuming "doc" is an XMLType variable containing your XML document, you can do :
SELECT insertchildxml(doc, 'ROWSET', '@IS_SUCCESS', '1') INTO doc FROM dual;Slightly off-topic, but to add attributes to ROW elements, DBMS_XMLGEN can handle it for us provided we prefix column aliases with "@".
For example :
SQL> SELECT dbms_xmlgen.getXML('SELECT ''Hello!'' as "@msg" FROM dual') FROM dual;
DBMS_XMLGEN.GETXML('SELECT''HE
<?xml version="1.0"?>
<ROWSET>
<ROW msg = "Hello!">
</ROW>
</ROWSET>
Edited by: odie_63 on 2 nov. 2010 12:50 - added remark on ROW attributes

Inter-Cluster "Locations" Calculations

We have three CUCM 8.5 clusters globally, connected via an MPLS network. The North American cluster has a SIP trunk to Polycom DMA- both the North American CUCM cluster and Polycom DMA cluster is within the same data center. I have a SIP trunk between the NA CUCM and DMA so audio calls from CUCM can join conferences within the Polycom world, and have a route pattern in NA CUCM pointed to DMA.
For redundancy/effeciency pusposes, the EMEA and APAC CUCM clusters should also have route patterns/trunks pointing directly to the DMA in North America. However, my concern is that while those local cluster may be able to calculate BW consumption correctly to North America (because they'll define their SIP trunks to be in the "North America" location), since it doesn't traverse through the NA CUCM, the NA
"Locations" BW caculation will not show an accurate portrayal of calls active to those remote clusters (or amount of voice BW being consumed on our local MPLS access circuit). Therefore, my preference is to have the remote cluster point their DMA route pattern over our Intercluster Trunks, so WAN BW calculations are correct.
My question is: There is no LOCATIONS "Information sharing" between clusters in CUCM 9.1 (target version), so that EMEA cluster would notify N.A. CUCM cluster that he is utilizing his "NA Locations" for calls (going directly to Polycom DMA), and not going through the NA CUCM cluster, so NA CUCM cluster includes that in his Call Admission Control? I'm comfortable with that not existing in CUCM 8.5, but I know there are Locations/CAC enhancements in 9.1 which I'm not too familiar with.
Thanks!

There is definitely location sharing between clusters in 9.1 using enhanced CAC.
Please refer to the SRND here
http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/srnd/collab09/clb09/cac.html#pgfId-1593372
A snapshot is posted here..
Location Bandwidth Manager
The Location Bandwidth Manager (LBM) is a Unified CM Feature Service managed from the serviceability web pages and responsible for all of the Enhanced Location CAC bandwidth functions. The LBM can run on any Unified CM subscriber or as a standalone service on a dedicated Unified CM server in the cluster. A minimum of one instance of LBM must run in each cluster to enable Enhanced Location CAC in the cluster. The LBM performs the following functions:
Locations and links path assembly
Bandwidth calculations over the effective paths in the assembly
Servicing bandwidth requests from the Cisco CallManager service (Unified CM call control)
Replication of bandwidth information to other LBMs within the cluster and between clusters when intercluster Enhanced Location CAC is enabled
Providing configured and dynamic information to serviceability
Updating Location Real-Time Monitoring Tool (RTMT) counters
Using Extensible Markup Language (XML) over TCP for communication to/from the Cisco CallManager service as well as between LBMs

Cluster & Call by reference ( Sorry for the re-posting)

If this is set to 'true', then what happens when the bean is in a diffent
          machine(Cluster)( Does it automatically passes object by 'value' or still
          tries to pass the object by reference, in which it is going to be a empty
          object )
          Looking at the document provided by weblogic , it looks like it
          automatically passes the object by 'value' even if it is set 'true'(Only
          incase of bean is running in a different container/server)
          Thanks
          
          <!ELEMENT enable-call-by-reference (#PCDATA)>


You cannot pass-by-reference a non-RMI Object across 2 VMs, no matter what the flag is, no matter
          what application server you are running under. An object reference in one VM is meaningless in
          another VM, for they do not share the same memory-address-space.
          Even though EJBs are RMI Objects, their method arguments are not unless you explicitly pass the RMI
          interface.
          Gene Chuang
          Join Kiko.com!
          "lal" <[email protected]> wrote in message news:[email protected]...
          > Is this true for WEBLOGIC server (5.1) ?
          > Does the container automatically switches to 'call by value' mode even
          > though the flag is set 'true' for call_by_reference in XML deployment
          > descriptor.(I know this only arise in the fail over process in a cluster
          > environment)
          >
          >
          > "Rob Woollen" <[email protected]> wrote in message
          > news:[email protected]...
          > > Anytime a call goes over the network, it will be call by value.
          > >
          > > Call by reference is only possible within the same server vm.
          > >
          > > -- Rob
          > >
          > > lal wrote:
          > > >
          > > > If this is set to 'true', then what happens when the bean is in a
          > diffent
          > > > machine(Cluster)( Does it automatically passes object by 'value' or
          > still
          > > > tries to pass the object by reference, in which it is going to be a
          > empty
          > > > object )
          > > >
          > > > Looking at the document provided by weblogic , it looks like it
          > > > automatically passes the object by 'value' even if it is set 'true'(Only
          > > > incase of bean is running in a different container/server)
          > > >
          > > > Thanks
          > > >
          > > > 
          > > > <!ELEMENT enable-call-by-reference (#PCDATA)>
          >
          >

Inter cluster trunk/ ip to ip communication with remote office without ccm

dear sir,
We've both ipipgateway configured to communicate with each other. Attachment pngipipgw1 is our local voice router with destination pattern 3XXXX that need to link with other country Japan with destination pattern 7xxxx . All other country locations is ok except the japan which are using non cisco callmanager to link to our local site with cisco call manager 4.1(3) with destination pattern 3XXXX.
Q1.) Based on the ipipgateway configurations of both parties, please advise any finding/thoughts?
Q2.)At our local site, We have nm-hdv with 2 pvdm simm that configured as dspfarm transcoder. Is it enough to have only 2 pvdm simm out of 5 in the nm-hdv? If we add in new pvdm, do we need any configuration at the voice gateway or we just plug in the hardware?
please advise. thank you very much.
-regards-

Hello chialun
Regarding
Q1. Could you explain a little more about what is the problem you have with the calls between those two sites? Please share which number on one side is calling which other number on the other side and what happens with the call.
Q2. It depends on how are you using your Xcoder resources. If some of your conferences or calls are being terminated because you are running out of resources, it will be advisable to add some more pvdm2 to your router. Also after adding the hardware, you would like to change the configuration to increas the maximum number of transcoding sessions.
Regards
Xabier

Inter-cluster JMS?

We are using weblogic 6.1
Is there a way to set up a JMS destination that is visible
to 2 clusters? For example, I set up a topic for two clusters.
When a message is sent, message driven beans in both clusters
will be notified. How would one set this up? Which cluster
does the destination "live in" and how does the other cluster
learn about it?

I'd suggest posting this in the JMS newsgroup.
-- Rob
Chris wrote:
We are using weblogic 6.1
Is there a way to set up a JMS destination that is visible
to 2 clusters? For example, I set up a topic for two clusters.
When a message is sent, message driven beans in both clusters
will be notified. How would one set this up? Which cluster
does the destination "live in" and how does the other cluster
learn about it?

Inter module call ( no ear )

I have an appli say A containing EJB A, and a standalone module say MB containing EJB B.
MB is deployed standalone ( not in an ear).
I do not succeed to call EJB B from EJB A.
there is an ejb-ref in the module of A with an ejb-link to ejb B but when I deploy I get : Error: Unresolved : Test9
I alse have tried this syntax :
<ejb-link>moduleName#Test9<ejb-link>
I also get an error saying it could not find the module.
Any idea ?
thanks
Michel

I suppose you're trying to access the EJB's using "Local Interfaces". If this is the case your problem is due to the scope of every module, I mean MA can only see the LocalInterfaces of its EJB container, so it won't see any Local Interfaces from MB.
If you put this two modules in a single EAR you can use local references from MA to MB adding the MB jar file to the classpath of MA (using the "manifest" archive of the jar file).
I hope this helps you.

Inter cluster calling

Similar Messages

Maybe you are looking for