[cisco-voip] CUBE not requesting codec... call fails... need to force SDP in invite...

[Lelio Fulgenzi]

Speaking of CUBE, just wondering what the common practice is for physical deployment. We have two routers which will eventually house our MGCP gateways in HQ and one router at each of our remote sites, again, MGCP. 

If I want to deploy CUBE, is it usually installed separately from the main campus router? 

--- 
Lelio Fulgenzi, B.A. 
Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1 
(519) 824-4120 x56354 (519) 767-1060 FAX (ANNU) 
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 
Cooking with unix is easy. You just sed it and forget it. 
- LFJ (with apologies to Mr. Popeil) 


----- Original Message -----
From: "Roger Wiklund" <roger.wiklund at gmail.com> 
To: "Jonathan Charles" <jonvoip at gmail.com> 
Cc: "Cisco VOIP" <cisco-voip at puck.nether.net> 
Sent: Wednesday, January 25, 2012 3:27:19 AM 
Subject: Re: [cisco-voip] CUBE not requesting codec... call fails... need to force SDP in invite... 

On Wed, Jan 25, 2012 at 3:54 AM, Jonathan Charles <jonvoip at gmail.com> wrote: 
> Because, as far as I can tell, Cisco does not support SIP to SIP on the 
> CUBE... and it doesn't work. 
> 
> You need to be H.323 to the CUBE, then SIP to the provider. 

Hi, 

SIP-SIP is definitely the way to go, should be easier on the CPU to 
not have to convert between the two, and also easier to troubleshoot. 

I'm running SIP-SIP with DO-EO and RTP flow-around. 

I wrote some notes about it that may be useful (even if you are not 
running flow-around) 

http://wiklunds.wordpress.com/2012/01/02/sip-delayed-offer-to-early-offer-with-rtp-flow-around-support-in-cube-8-6/ 

Regards 
Roger 
_______________________________________________ 
cisco-voip mailing list 
cisco-voip at puck.nether.net 
https://puck.nether.net/mailman/listinfo/cisco-voip 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20120125/74a6fe83/attachment.html>