[cisco-voip] gigE interface on NME-CUE - what's it good for?

[Lelio Fulgenzi]

ah. ok. i'm surprised they didn't build a steel cover and screwed it to the chasis so you couldn't use it. 

--- 
Lelio Fulgenzi, B.A. 
Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1 
(519) 824-4120 x56354 (519) 767-1060 FAX (JNHN) 
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 
"Bad grammar makes me [sic]" - Tshirt 


----- Original Message ----- 
From: "Paul" <asobihoudai at yahoo.com> 
To: "Lelio Fulgenzi" <lelio at uoguelph.ca>, "cisco-voip voyp list" <cisco-voip at puck.nether.net> 
Sent: Saturday, December 12, 2009 2:50:51 PM GMT -05:00 US/Canada Eastern 
Subject: Re: [cisco-voip] gigE interface on NME-CUE - what's it good for? 

It's a GigE interface that is unusable with CUE and only exists because the little Linux embedded platform that the NME-CUE is based upon is used for other applications. (AXP comes to immediate mind) 





________________________________ 
From: Lelio Fulgenzi <lelio at uoguelph.ca> 
To: cisco-voip voyp list <cisco-voip at puck.nether.net> 
Sent: Sat, December 12, 2009 11:33:18 AM 
Subject: [cisco-voip] gigE interface on NME-CUE - what's it good for? 


I just noticed a GigE connection on the NME-CUE module we just got in. Just wondering what it's for. Not much information in the CUE installation or design docs. No hits in netpro or list archives. 

The design guide talks about using the backblane as the network connection, which is how we did it with an AIM module. But no mention of the GigE connector. Is it a regularly configurable interface? 

--- 
Lelio Fulgenzi, B.A. 
Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1 
(519) 824-4120 x56354 (519) 767-1060 FAX (JNHN) 
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 
"Bad grammar makes me [sic]" - Tshirt 



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20091212/508a8b15/attachment.html>