[cisco-voip] 4.1delay upon call connection.

[Anthony Mendoza]

Ooops, we're on 4.0(2).  That could by why I don't see it..however, 
we'll try the initial setting on the call manager config to see if that 
will help.

Thanks for the input though!
--
Anthony Mendoza

Wes Sisk sent a message, dated 4/11/2005 8:24 AM about:
> I'm looking in 4.1(2) and faststart options are specified on the trunk
> configuration page.
> 
> /Wes
> 
> -----Original Message-----
> From: Anthony Mendoza [mailto:amendoza at Niku.com]
> Sent: Monday, April 11, 2005 11:08 AM
> To: Wes Sisk
> Cc: Nick Marus; cisco-voip at puck.nether.net; Daniel Sexton
> Subject: Re: [cisco-voip] 4.1delay upon call connection.
> 
> 
> Does that apply to inter-cluster trunks as well, or do those still use
> our MGCP and H.323 gateways at each site?  I was under the impression
> that the inter-cluster trunk is directly between the CMs and didn't
> involve my 6509 (in the US) or 2651 (in the UK).
> --
> Anthony Mendoza
> 
> Wes Sisk sent a message, dated 4/11/2005 8:04 AM about:
>  > Anthony,
>  >
>  > You will need to enable fast start outound and inbound on your trunk
>  > devices.
>  >
>  > /Wes
>  >
>  > -----Original Message-----
>  > From: Anthony Mendoza [mailto:amendoza at Niku.com]
>  > Sent: Monday, April 11, 2005 10:56 AM
>  > To: Wes Sisk
>  > Cc: Nick Marus; cisco-voip at puck.nether.net; Daniel Sexton
>  > Subject: Re: [cisco-voip] 4.1delay upon call connection.
>  >
>  >
>  > Wes,
>  >
>  > H323 FastStart Inbound*  == False on both ends of the cluster
>  >
>  > I'm assuming after reading the description that we'll want to test with
>  > that set to true, correct?  Also, if I update this setting on the
>  > publisher will it sync with the subscriber or do I need to do this per
> node?
>  > --
>  > Anthony Mendoza
>  >
>  > Wes Sisk sent a message, dated 4/11/2005 7:47 AM about:
>  >  > Do you both have h323 fast start enabled?
>  >  >
>  >  > /Wes
>  >  >
>  >  > -----Original Message-----
>  >  > From: cisco-voip-bounces at puck.nether.net
>  >  > [mailto:cisco-voip-bounces at puck.nether.net]On Behalf Of Anthony 
> Mendoza
>  >  > Sent: Monday, April 11, 2005 10:43 AM
>  >  > To: Nick Marus
>  >  > Cc: cisco-voip at puck.nether.net; Daniel Sexton
>  >  > Subject: Re: [cisco-voip] 4.1delay upon call connection.
>  >  >
>  >  >
>  >  > Interestingly enough, yes.  We see this between our clusters in the UK
>  >  > and US, but were told it was because we are doing this over a VPN and
>  >  > that extra latency (the few extra ms) is what is causing it.  Also,
>  >  > since we're doing it in this configuration they refuse to do any
> support
>  >  > since we can't establish and guarantee QoS between the sites.  I'd be
>  >  > happy to hear if there was a simple/easy fix for this..  our delay is
>  >  > usually 2-3 seconds.  Between myself and the main IT person out there
> we
>  >  > count on the phone to check delay.
>  >  > --
>  >  > Anthony Mendoza
>  >  >
>  >  > Nick Marus sent a message, dated 4/11/2005 7:31 AM about:
>  >  >  > Anyoe seen calls have no audio for the first 3-4 seconds of an
>  >  >  > established call with 4.1.2??
>  >  >  >
>  >  >  >
>  >  >  >
>  >  >  > --
>  >  >  > Nick Marus
>  >  >  > nmarus at gmail.com.
>  >  >  > _______________________________________________
>  >  >  > cisco-voip mailing list
>  >  >  > cisco-voip at puck.nether.net
>  >  >  > https://puck.nether.net/mailman/listinfo/cisco-voip
>  >  >  >
>  >  >
>  >  >
>  >  > CONFIDENTIALITY NOTICE: The information contained in this message and
>  >  > or attachments is intended only for the person or entity to which 
> it is
>  >  > addressed and may contain confidential and/or privileged material. Any
>  >  > review, retransmission, dissemination, copying, or other use of this
>  >  > information by persons or entities other than the intended 
> recipient is
>  >  > prohibited. If you received this e-mail or its attachments in error,
>  >  > please contact the sender and delete the material from any system and
>  >  > destroy any copies.
>  >  >
>  >  >
>  >
>  >
>  > CONFIDENTIALITY NOTICE: The information contained in this message and
>  > or attachments is intended only for the person or entity to which it is
>  > addressed and may contain confidential and/or privileged material. Any
>  > review, retransmission, dissemination, copying, or other use of this
>  > information by persons or entities other than the intended recipient is
>  > prohibited. If you received this e-mail or its attachments in error,
>  > please contact the sender and delete the material from any system and
>  > destroy any copies.
>  >
>  >
> 
> 
> CONFIDENTIALITY NOTICE: The information contained in this message and
> or attachments is intended only for the person or entity to which it is
> addressed and may contain confidential and/or privileged material. Any
> review, retransmission, dissemination, copying, or other use of this
> information by persons or entities other than the intended recipient is
> prohibited. If you received this e-mail or its attachments in error,
> please contact the sender and delete the material from any system and
> destroy any copies.
> 
> 


CONFIDENTIALITY NOTICE: The information contained in this message and
or attachments is intended only for the person or entity to which it is
addressed and may contain confidential and/or privileged material. Any
review, retransmission, dissemination, copying, or other use of this
information by persons or entities other than the intended recipient is
prohibited. If you received this e-mail or its attachments in error, 
please contact the sender and delete the material from any system and 
destroy any copies.