Hi
I Don�t know the quality of Nortel equipment for VoIP, but I would not 
recommend on any case, to use custom queueing if you have voice, as it
can create variable delays, and lower a lot your final voice quality.
Stay with LLC (correctly configured) on all of the path...
VoIP should get almost perfect quality, if you provide the correct
bandwidth/delay for the path

Regards!

John Neiberger wrote:
> 
> We have implemented VoIP at two of our branches as a test.  We are using
> Nortel ITG cards in the branch PBX to convert the calls to IP and then we
> connect the card to a Cisco 2924XL switch with all voice traffic in its own
> VLAN.  Then the traffic hits a 2620 router with LLQ configured.  The voice
> calls then go through another branch with custom queueing configured, then
> to the destination branch with the same setup as the first branch.
> 
> This is now up and running without any serious glitches, but the users at
> the branches complain that all incoming calls sound like cell phone calls.
> Is this the type of quality we can expect from this technology?  Is it a
> natural result of packetizing real-time voice traffic?  Or, can we expect
> better?
> 
> Any thoughts or tips would be appreciated.
> 
> Thanks,
> John
> 
> _______________________________________________________
> Send a cool gift with your E-Card
> http://www.bluemountain.com/giftcenter/
> 
> _________________________________
> FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
> Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]

-- 
---
Javier Contreras Albesa
Professional Trainer

PRO IN Training S.L.
PROfessional Information Networks
World Trade Center, Moll de Barcelona S/N
Edif Sur, Planta 4

Phone: (+34) 93-5088850             E-mail:    
[EMAIL PROTECTED]
Fax:      (+34) 93-5088860             Internet:  http://www.proin.com

SHAPING THE FUTURE - BE PART OF IT!

_________________________________
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]

Reply via email to