Okay, I've setup an intercluster trunk on one CM cluster that points to
the foreign CM.  I've setup a route pattern that includes this trunk,
however when I dial I get a busy tone.  What am I missing?  Do I need to
configure a trunk on the other end to make one way calling function?
Both are CM 3.3(4).  After I get the test calls working I'll worry about
CAC and AAR

 

Thanks!

 

 

[ Post a follow-up to this message ]

CM won't accept an H.225 Setup message from any device not in its  =

database.   This goes for ICTs as well as regular voice gateways.    =

This is why your ICTs always need to be fully meshed (ie all servers  =

defined in the trunk on both sides).

-Ryan

On Oct 24, 2005, at 12:09 PM, Burton, Jason wrote:

Okay, I=92ve setup an intercluster trunk on one CM cluster that points  =

to the foreign CM.  I=92ve setup a route pattern that includes this  =

trunk, however when I dial I get a busy tone.  What am I missing?  Do  =

I need to configure a trunk on the other end to make one way calling  =

function?  Both are CM 3.3(4).  After I get the test calls working  =

I=92ll worry about CAC and AAR



Thanks!





 ________________________________________
_______
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

[ Post a follow-up to this message ]

Now that I re-read my email this is a single CM to a single CM not a
cluster.  Sorry about that.

-----Original Message-----
From: Ryan Ratliff [mailto:rratliff@cisco.com]
Sent: Monday, October 24, 2005 11:18 AM
To: Burton, Jason
Cc: cisco-voip@puck.nether.net
Subject: Re: [cisco-voip] Intercluster Trunk what am I missing?

CM won't accept an H.225 Setup message from any device not in its
database.   This goes for ICTs as well as regular voice gateways.
This is why your ICTs always need to be fully meshed (ie all servers
defined in the trunk on both sides).

-Ryan

On Oct 24, 2005, at 12:09 PM, Burton, Jason wrote:

Okay, I've setup an intercluster trunk on one CM cluster that points
to the foreign CM.  I've setup a route pattern that includes this
trunk, however when I dial I get a busy tone.  What am I missing?  Do
I need to configure a trunk on the other end to make one way calling
function?  Both are CM 3.3(4).  After I get the test calls working
I'll worry about CAC and AAR



Thanks!





 ________________________________________
_______
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

[ Post a follow-up to this message ]

This is a great document. 

http://www.cisco.com/en/US/customer...080094729.shtml

You also have to make sure that the calling search space for the trunk is se
t up properly to dial those numbers you are dialing. For example, if on clus
ter A you have route pattern 52XX going to cluster B, then the calling searc
h space of the trunk as configured on cluster B has access to the partition 
which includes the 52XX DNs you want to reach.

You also have to worry about looping which will give you error tone if the n
umber you are dialing is looped back and forth between the clusters too many
 times (either error tone or the clusters will crash - one or the other. ;)


----------------------------------------------------------------------------
----
Lelio Fulgenzi, B.A.
Network Analyst (CCS) * university of Guelph * Guelph, Ontario N1G 2W1
(519) 824-4120 x56354 (519) 767-1060 FAX (JNHN)
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 
"I had a coffee and Coke at lunch today...and now, I've got more jitter than
 an
IP phone on a long haul 10base2 connection"                              LFJ
----- Original Message ----- 
From: Burton, Jason 
To: cisco-voip@puck.nether.net 
Sent: Monday, October 24, 2005 12:09 PM
Subject: [cisco-voip] Intercluster Trunk what am I missing?


Okay, I've setup an intercluster trunk on one CM cluster that points to the 
foreign CM.  I've setup a route pattern that includes this trunk, however wh
en I dial I get a busy tone.  What am I missing?  Do I need to configure a t
runk on the other end to make one way calling function?  Both are CM 3.3(4).
  After I get the test calls working I'll worry about CAC and AAR

 

Thanks!

 

 



----------------------------------------------------------------------------
--


 ________________________________________
_______
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

[ Post a follow-up to this message ]

Man talk about a dumb butt attack.  So I was banging my head against the
wall to find out I had a typo in the ip address for one of the CM's.
Geez go figure it works after you type in the right one.

Thanks!

-----Original Message-----
From: cisco-voip-bounces@puck.nether.net
[mailto:cisco-voip-bounces@puck.nether.net] On Behalf Of Burton, Jason
Sent: Monday, October 24, 2005 11:40 AM
To: Ryan Ratliff
Cc: cisco-voip@puck.nether.net
Subject: RE: [cisco-voip] Intercluster Trunk what am I missing?

Now that I re-read my email this is a single CM to a single CM not a
cluster.  Sorry about that.

-----Original Message-----
From: Ryan Ratliff [mailto:rratliff@cisco.com]
Sent: Monday, October 24, 2005 11:18 AM
To: Burton, Jason
Cc: cisco-voip@puck.nether.net
Subject: Re: [cisco-voip] Intercluster Trunk what am I missing?

CM won't accept an H.225 Setup message from any device not in its
database.   This goes for ICTs as well as regular voice gateways.
This is why your ICTs always need to be fully meshed (ie all servers
defined in the trunk on both sides).

-Ryan

On Oct 24, 2005, at 12:09 PM, Burton, Jason wrote:

Okay, I've setup an intercluster trunk on one CM cluster that points
to the foreign CM.  I've setup a route pattern that includes this
trunk, however when I dial I get a busy tone.  What am I missing?  Do
I need to configure a trunk on the other end to make one way calling
function?  Both are CM 3.3(4).  After I get the test calls working
I'll worry about CAC and AAR



Thanks!





 ________________________________________
_______
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip



 ________________________________________
_______
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

[ Post a follow-up to this message ]

wait until IPv6 comes out and we have to remember stuf like 3ffe:1900:4545:3
:200:f8ff:fe21:67cf

*shiver*


----------------------------------------------------------------------------
----
Lelio Fulgenzi, B.A.
Network Analyst (CCS) * university of Guelph * Guelph, Ontario N1G 2W1
(519) 824-4120 x56354 (519) 767-1060 FAX (JNHN)
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 
"I had a coffee and Coke at lunch today...and now, I've got more jitter than
 an
IP phone on a long haul 10base2 connection"                              LFJ
----- Original Message ----- 
From: Burton, Jason 
To: Burton, Jason 
Cc: cisco-voip@puck.nether.net 
Sent: Monday, October 24, 2005 4:23 PM
Subject: RE: [cisco-voip] Intercluster Trunk what am I missing?


Man talk about a dumb butt attack.  So I was banging my head against the
wall to find out I had a typo in the ip address for one of the CM's.
Geez go figure it works after you type in the right one.

Thanks!

-----Original Message-----
From: cisco-voip-bounces@puck.nether.net
[mailto:cisco-voip-bounces@puck.nether.net] On Behalf Of Burton, Jason
Sent: Monday, October 24, 2005 11:40 AM
To: Ryan Ratliff
Cc: cisco-voip@puck.nether.net
Subject: RE: [cisco-voip] Intercluster Trunk what am I missing?

Now that I re-read my email this is a single CM to a single CM not a
cluster.  Sorry about that.

-----Original Message-----
From: Ryan Ratliff [mailto:rratliff@cisco.com] 
Sent: Monday, October 24, 2005 11:18 AM
To: Burton, Jason
Cc: cisco-voip@puck.nether.net
Subject: Re: [cisco-voip] Intercluster Trunk what am I missing?

CM won't accept an H.225 Setup message from any device not in its  
database.   This goes for ICTs as well as regular voice gateways.    
This is why your ICTs always need to be fully meshed (ie all servers  
defined in the trunk on both sides).

-Ryan

On Oct 24, 2005, at 12:09 PM, Burton, Jason wrote:

Okay, I've setup an intercluster trunk on one CM cluster that points  
to the foreign CM.  I've setup a route pattern that includes this  
trunk, however when I dial I get a busy tone.  What am I missing?  Do  
I need to configure a trunk on the other end to make one way calling  
function?  Both are CM 3.3(4).  After I get the test calls working  
I'll worry about CAC and AAR



Thanks!





 ________________________________________
_______
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip



 ________________________________________
_______
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

 ________________________________________
_______
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

[ Post a follow-up to this message ]

CM also attempts a reverse DNS resolution and looks for that device name, so
you don't have to remember all those digits, so long as you include dns as
part of your IPT infrastructure.

/Wes
-----Original Message-----
From: cisco-voip-bounces@puck.nether.net
[mailto:cisco-voip-bounces@puck.nether.net]On Behalf Of Lelio Fulgenzi
Sent: Monday, October 24, 2005 4:27 PM
To: Burton, Jason
Cc: cisco-voip@puck.nether.net
Subject: Re: [cisco-voip] Intercluster Trunk what am I missing?


wait until IPv6 comes out and we have to remember stuf like
3ffe:1900:4545:3:200:f8ff:fe21:67cf

*shiver*


----------------------------------------------------------------------------
----
Lelio Fulgenzi, B.A.
Network Analyst (CCS) * university of Guelph * Guelph, Ontario N1G 2W1
(519) 824-4120 x56354 (519) 767-1060 FAX (JNHN)
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
"I had a coffee and Coke at lunch today...and now, I've got more jitter than
an
IP phone on a long haul 10base2 connection"
LFJ
----- Original Message -----
From: Burton, Jason
To: Burton, Jason
Cc: cisco-voip@puck.nether.net
Sent: Monday, October 24, 2005 4:23 PM
Subject: RE: [cisco-voip] Intercluster Trunk what am I missing?


Man talk about a dumb butt attack.  So I was banging my head against the
wall to find out I had a typo in the ip address for one of the CM's.
Geez go figure it works after you type in the right one.

Thanks!

-----Original Message-----
From: cisco-voip-bounces@puck.nether.net
[mailto:cisco-voip-bounces@puck.nether.net] On Behalf Of Burton, Jason
Sent: Monday, October 24, 2005 11:40 AM
To: Ryan Ratliff
Cc: cisco-voip@puck.nether.net
Subject: RE: [cisco-voip] Intercluster Trunk what am I missing?

Now that I re-read my email this is a single CM to a single CM not a
cluster.  Sorry about that.

-----Original Message-----
From: Ryan Ratliff [mailto:rratliff@cisco.com]
Sent: Monday, October 24, 2005 11:18 AM
To: Burton, Jason
Cc: cisco-voip@puck.nether.net
Subject: Re: [cisco-voip] Intercluster Trunk what am I missing?

CM won't accept an H.225 Setup message from any device not in its
database.   This goes for ICTs as well as regular voice gateways.
This is why your ICTs always need to be fully meshed (ie all servers
defined in the trunk on both sides).

-Ryan

On Oct 24, 2005, at 12:09 PM, Burton, Jason wrote:

Okay, I've setup an intercluster trunk on one CM cluster that points
to the foreign CM.  I've setup a route pattern that includes this
trunk, however when I dial I get a busy tone.  What am I missing?  Do
I need to configure a trunk on the other end to make one way calling
function?  Both are CM 3.3(4).  After I get the test calls working
I'll worry about CAC and AAR



Thanks!





 ________________________________________
_______
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip



 ________________________________________
_______
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

 ________________________________________
_______
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

[ Post a follow-up to this message ]

I was always taught that DNS Reliance in CCM was a Bad Thing?!?

-----Original Message-----
From: cisco-voip-bounces@puck.nether.net
[mailto:cisco-voip-bounces@puck.nether.net] On Behalf Of Wes Sisk
Sent: Monday, October 24, 2005 4:25 PM
To: Lelio Fulgenzi; Burton, Jason
Cc: cisco-voip@puck.nether.net
Subject: RE: [cisco-voip] Intercluster Trunk what am I missing?


CM also attempts a reverse DNS resolution and looks for that device name, so
you don't have to remember all those digits, so long as you include dns as
part of your IPT infrastructure.

/Wes
-----Original Message-----
From: cisco-voip-bounces@puck.nether.net
[mailto:cisco-voip-bounces@puck.nether.net]On Behalf Of Lelio Fulgenzi
Sent: Monday, October 24, 2005 4:27 PM
To: Burton, Jason
Cc: cisco-voip@puck.nether.net
Subject: Re: [cisco-voip] Intercluster Trunk what am I missing?


wait until IPv6 comes out and we have to remember stuf like
3ffe:1900:4545:3:200:f8ff:fe21:67cf

*shiver*


----------------------------------------------------------------------------
----
Lelio Fulgenzi, B.A.
Network Analyst (CCS) * university of Guelph * Guelph, Ontario N1G 2W1
(519) 824-4120 x56354 (519) 767-1060 FAX (JNHN)
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
"I had a coffee and Coke at lunch today...and now, I've got more jitter than
an
IP phone on a long haul 10base2 connection"
LFJ

----- Original Message -----
From: Burton, Jason <mailto:Jason.Burton@CoreBTS.com>
To: Burton, Jason <mailto:Jason.Burton@CoreBTS.com>
Cc: cisco-voip@puck.nether.net <mailto:cisco-voip@puck.nether.net>
Sent: Monday, October 24, 2005 4:23 PM
Subject: RE: [cisco-voip] Intercluster Trunk what am I missing?

Man talk about a dumb butt attack.  So I was banging my head against the
wall to find out I had a typo in the ip address for one of the CM's.
Geez go figure it works after you type in the right one.

Thanks!

-----Original Message-----
From: cisco-voip-bounces@puck.nether.net
<mailto:cisco-voip-bounces@puck.nether.net>
[mailto:cisco-voip-bounces@puck.nether.net] On Behalf Of Burton, Jason
Sent: Monday, October 24, 2005 11:40 AM
To: Ryan Ratliff
Cc: cisco-voip@puck.nether.net <mailto:cisco-voip@puck.nether.net>
Subject: RE: [cisco-voip] Intercluster Trunk what am I missing?

Now that I re-read my email this is a single CM to a single CM not a
cluster.  Sorry about that.

-----Original Message-----
From: Ryan Ratliff [mailto:rratliff@cisco.com]
Sent: Monday, October 24, 2005 11:18 AM
To: Burton, Jason
Cc: cisco-voip@puck.nether.net <mailto:cisco-voip@puck.nether.net>
Subject: Re: [cisco-voip] Intercluster Trunk what am I missing?

CM won't accept an H.225 Setup message from any device not in its
database.   This goes for ICTs as well as regular voice gateways.
This is why your ICTs always need to be fully meshed (ie all servers
defined in the trunk on both sides).

-Ryan

On Oct 24, 2005, at 12:09 PM, Burton, Jason wrote:

Okay, I've setup an intercluster trunk on one CM cluster that points
to the foreign CM.  I've setup a route pattern that includes this
trunk, however when I dial I get a busy tone.  What am I missing?  Do
I need to configure a trunk on the other end to make one way calling
function?  Both are CM 3.3(4).  After I get the test calls working
I'll worry about CAC and AAR



Thanks!





 ________________________________________
_______
cisco-voip mailing list
cisco-voip@puck.nether.net <mailto:cisco-voip@puck.nether.net>
https://puck.nether.net/mailman/listinfo/cisco-voip
<https://puck.nether.net/mailman/listinfo/cisco-voip>



 ________________________________________
_______
cisco-voip mailing list
cisco-voip@puck.nether.net <mailto:cisco-voip@puck.nether.net>
https://puck.nether.net/mailman/listinfo/cisco-voip
<https://puck.nether.net/mailman/listinfo/cisco-voip>

 ________________________________________
_______
cisco-voip mailing list
cisco-voip@puck.nether.net <mailto:cisco-voip@puck.nether.net>
https://puck.nether.net/mailman/listinfo/cisco-voip
<https://puck.nether.net/mailman/listinfo/cisco-voip>

[ Post a follow-up to this message ]

Messageit's personal opinion, i think dependence on DNS is bad because most
people don't think of DNS as being critical to completing a phone call.
Thus my disclaimer "include DNS as part of your IPT infrastructure".

/Wes
-----Original Message-----
From: Fretz, EA Eric @ IS [mailto:Eric.A.Fretz@L-3Com.com]
Sent: Monday, October 24, 2005 5:33 PM
To: 'Wes Sisk'; Lelio Fulgenzi; Burton, Jason
Cc: cisco-voip@puck.nether.net
Subject: RE: [cisco-voip] Intercluster Trunk what am I missing?


I was always taught that DNS Reliance in CCM was a Bad Thing?!?
-----Original Message-----
From: cisco-voip-bounces@puck.nether.net
[mailto:cisco-voip-bounces@puck.nether.net] On Behalf Of Wes Sisk
Sent: Monday, October 24, 2005 4:25 PM
To: Lelio Fulgenzi; Burton, Jason
Cc: cisco-voip@puck.nether.net
Subject: RE: [cisco-voip] Intercluster Trunk what am I missing?


CM also attempts a reverse DNS resolution and looks for that device name,
so you don't have to remember all those digits, so long as you include dns
as part of your IPT infrastructure.

/Wes
-----Original Message-----
From: cisco-voip-bounces@puck.nether.net
[mailto:cisco-voip-bounces@puck.nether.net]On Behalf Of Lelio Fulgenzi
Sent: Monday, October 24, 2005 4:27 PM
To: Burton, Jason
Cc: cisco-voip@puck.nether.net
Subject: Re: [cisco-voip] Intercluster Trunk what am I missing?


wait until IPv6 comes out and we have to remember stuf like
3ffe:1900:4545:3:200:f8ff:fe21:67cf

*shiver*


--------------------------------------------------------------------------
------
Lelio Fulgenzi, B.A.
Network Analyst (CCS) * university of Guelph * Guelph, Ontario N1G 2W1
(519) 824-4120 x56354 (519) 767-1060 FAX (JNHN)
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
"I had a coffee and Coke at lunch today...and now, I've got more jitter
than an
IP phone on a long haul 10base2 connection"
LFJ
----- Original Message -----
From: Burton, Jason
To: Burton, Jason
Cc: cisco-voip@puck.nether.net
Sent: Monday, October 24, 2005 4:23 PM
Subject: RE: [cisco-voip] Intercluster Trunk what am I missing?


Man talk about a dumb butt attack.  So I was banging my head against the
wall to find out I had a typo in the ip address for one of the CM's.
Geez go figure it works after you type in the right one.

Thanks!

-----Original Message-----
From: cisco-voip-bounces@puck.nether.net
[mailto:cisco-voip-bounces@puck.nether.net] On Behalf Of Burton, Jason
Sent: Monday, October 24, 2005 11:40 AM
To: Ryan Ratliff
Cc: cisco-voip@puck.nether.net
Subject: RE: [cisco-voip] Intercluster Trunk what am I missing?

Now that I re-read my email this is a single CM to a single CM not a
cluster.  Sorry about that.

-----Original Message-----
From: Ryan Ratliff [mailto:rratliff@cisco.com]
Sent: Monday, October 24, 2005 11:18 AM
To: Burton, Jason
Cc: cisco-voip@puck.nether.net
Subject: Re: [cisco-voip] Intercluster Trunk what am I missing?

CM won't accept an H.225 Setup message from any device not in its
database.   This goes for ICTs as well as regular voice gateways.
This is why your ICTs always need to be fully meshed (ie all servers
defined in the trunk on both sides).

-Ryan

On Oct 24, 2005, at 12:09 PM, Burton, Jason wrote:

Okay, I've setup an intercluster trunk on one CM cluster that points
to the foreign CM.  I've setup a route pattern that includes this
trunk, however when I dial I get a busy tone.  What am I missing?  Do
I need to configure a trunk on the other end to make one way calling
function?  Both are CM 3.3(4).  After I get the test calls working
I'll worry about CAC and AAR



Thanks!





 ________________________________________
_______
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip



 ________________________________________
_______
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

 ________________________________________
_______
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

[ Post a follow-up to this message ]

Well, I'd still caution on DNS.  I've had environments where DNS (MS based)
took some major hits, and really screwed the IPT system up.  I'm a firm
believer in IP Addresses only in IPT for now.

That being said, if you have cisco Network Registrar, or *nix based DNS,
you'd be ok more often than not ;-)


_____

From: cisco-voip-bounces@puck.nether.net
[mailto:cisco-voip-bounces@puck.nether.net] On Behalf Of Wes Sisk
Sent: Monday, October 24, 2005 4:40 PM
To: Fretz, EA Eric @ IS; Lelio Fulgenzi; Burton, Jason
Cc: cisco-voip@puck.nether.net
Subject: RE: [cisco-voip] Intercluster Trunk what am I missing?


it's personal opinion, i think dependence on DNS is bad because most people
don't think of DNS as being critical to completing a phone call.  Thus my
disclaimer "include DNS as part of your IPT infrastructure".

/Wes
-----Original Message-----
From: Fretz, EA Eric @ IS [mailto:Eric.A.Fretz@L-3Com.com]
Sent: Monday, October 24, 2005 5:33 PM
To: 'Wes Sisk'; Lelio Fulgenzi; Burton, Jason
Cc: cisco-voip@puck.nether.net
Subject: RE: [cisco-voip] Intercluster Trunk what am I missing?


I was always taught that DNS Reliance in CCM was a Bad Thing?!?

-----Original Message-----
From: cisco-voip-bounces@puck.nether.net
[mailto:cisco-voip-bounces@puck.nether.net] On Behalf Of Wes Sisk
Sent: Monday, October 24, 2005 4:25 PM
To: Lelio Fulgenzi; Burton, Jason
Cc: cisco-voip@puck.nether.net
Subject: RE: [cisco-voip] Intercluster Trunk what am I missing?


CM also attempts a reverse DNS resolution and looks for that device name, so
you don't have to remember all those digits, so long as you include dns as
part of your IPT infrastructure.

/Wes
-----Original Message-----
From: cisco-voip-bounces@puck.nether.net
[mailto:cisco-voip-bounces@puck.nether.net]On Behalf Of Lelio Fulgenzi
Sent: Monday, October 24, 2005 4:27 PM
To: Burton, Jason
Cc: cisco-voip@puck.nether.net
Subject: Re: [cisco-voip] Intercluster Trunk what am I missing?


wait until IPv6 comes out and we have to remember stuf like
3ffe:1900:4545:3:200:f8ff:fe21:67cf

*shiver*


----------------------------------------------------------------------------
----
Lelio Fulgenzi, B.A.
Network Analyst (CCS) * university of Guelph * Guelph, Ontario N1G 2W1
(519) 824-4120 x56354 (519) 767-1060 FAX (JNHN)
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
"I had a coffee and Coke at lunch today...and now, I've got more jitter than
an
IP phone on a long haul 10base2 connection"
LFJ

----- Original Message -----
From: Burton, Jason <mailto:Jason.Burton@CoreBTS.com>
To: Burton, Jason <mailto:Jason.Burton@CoreBTS.com>
Cc: cisco-voip@puck.nether.net
Sent: Monday, October 24, 2005 4:23 PM
Subject: RE: [cisco-voip] Intercluster Trunk what am I missing?

Man talk about a dumb butt attack.  So I was banging my head against the
wall to find out I had a typo in the ip address for one of the CM's.
Geez go figure it works after you type in the right one.

Thanks!

-----Original Message-----
From: cisco-voip-bounces@puck.nether.net
[mailto:cisco-voip-bounces@puck.nether.net] On Behalf Of Burton, Jason
Sent: Monday, October 24, 2005 11:40 AM
To: Ryan Ratliff
Cc: cisco-voip@puck.nether.net
Subject: RE: [cisco-voip] Intercluster Trunk what am I missing?

Now that I re-read my email this is a single CM to a single CM not a
cluster.  Sorry about that.

-----Original Message-----
From: Ryan Ratliff [mailto:rratliff@cisco.com]
Sent: Monday, October 24, 2005 11:18 AM
To: Burton, Jason
Cc: cisco-voip@puck.nether.net
Subject: Re: [cisco-voip] Intercluster Trunk what am I missing?

CM won't accept an H.225 Setup message from any device not in its
database.   This goes for ICTs as well as regular voice gateways.
This is why your ICTs always need to be fully meshed (ie all servers
defined in the trunk on both sides).

-Ryan

On Oct 24, 2005, at 12:09 PM, Burton, Jason wrote:

Okay, I've setup an intercluster trunk on one CM cluster that points
to the foreign CM.  I've setup a route pattern that includes this
trunk, however when I dial I get a busy tone.  What am I missing?  Do
I need to configure a trunk on the other end to make one way calling
function?  Both are CM 3.3(4).  After I get the test calls working
I'll worry about CAC and AAR



Thanks!





 ________________________________________
_______
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip



 ________________________________________
_______
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

 ________________________________________
_______
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

[ Post a follow-up to this message ]