Re: [cisco-voip] CUBE across VRFs

I’ve seen it come two ways, riding your same MPLS circuit, in which case if you have a dedicated VG you just default route that to your MPLS router and there you go. The other way is like you say and I’ve done that with at&t and I didn’t have to route with them, they NAT’d everything on their s

Re: [cisco-voip] CUBE across VRFs

Really you only talk to one or two IP address at the Service provider, a default route out the internet/SP interface is less than typically critical. From: cisco-voip [mailto:cisco-voip-boun...@puck.nether.net] On Behalf Of Norton, Mike Sent: Wednesday, February 04, 2015 3:05 PM To: Erick Cc:

Re: [cisco-voip] CUBE across VRFs

What I’m failing to understand is... if I set the CUBE’s default route to be my router on my network, then how will CUBE be able to reach the SIP provider’s call servers on the SIP provider’s network? It seems like I will need a routing protocol on whichever side of the CUBE doesn’t get a defaul

Re: [cisco-voip] UCCE Patching

We do quarterly windows updates here, anything more often than that is a nuisance. Ed -Original Message- From: cisco-voip [mailto:cisco-voip-boun...@puck.nether.net] On Behalf Of Ken Rhodes Sent: Wednesday, February 04, 2015 4:22 PM To: cisco-voip@puck.nether.net Subject: [cisco-voip] U

Re: [cisco-voip] CUBE across VRFs

Use Acme Packet instead of CUBE if you need to handle multiple customers/overlapping IPs. To bad they are Oracle now On Wed, Feb 4, 2015 at 2:49 AM, Erick wrote: > Only one voice vrf can be defined in IOS. Global under voice service voip. > > Cube-SP lets you do multiple vrf's but is EoL an

[cisco-voip] UCCE Patching

Just a general UCCE maintenance question for anyone out there. How do you go about patching those windows servers? Do you have a policy to patch them only for critical issues? Do you patch them every quarter, etc? I know Cisco's stance is to follow whatever company policy dictates, however I d

Re: [cisco-voip] Informix Drivers for CCX

what wasn't working about the drivers ? I've used them before without any issues. I suspect maybe it was a 32/64 bit issue. I've also seen some weird behavior where the odbc gui is just finicky about how you enter the data for it to save properly. On Wed, Feb 4, 2015 at 2:23 PM, Matthew Loradi

Re: [cisco-voip] Informix Drivers for CCX

They would just not connect, same setting 3.0 driver and it works ODBC wise. Matthew G. Loraditch – CCNP-Voice, CCNA-R&S, CCDA Network Engineer Direct Voice: 443.541.1518 Facebook | Twitter | LinkedIn

[cisco-voip] Informix Drivers for CCX

I had to open a TAC case because our wallboard stopped working. The ODBC drivers in the 3.70 and 4.1 informix were not working. The TAC solution was to somehow find me an ancient 3.0 version of the Informix SDK. It did start working, but it just doesn't make sense and now our wallboard doesn't w

Re: [cisco-voip] DX series endpoints registered with cucm

Hi Brian, Yes the MCU is in the same Device Pool I’ll pull some new logs and have a look through them again Andy andy.ca...@gmail.com > On 4 Feb 2015, at 16:08, Brian Meade wrote: > > Might want to pull CallManager traces and see what happens when it tries to > allocate the video conferen

Re: [cisco-voip] DX series endpoints registered with cucm

Might want to pull CallManager traces and see what happens when it tries to allocate the video conference bridge. Do you have the MCU in the same device pool as the rest of the devices? On Wed, Feb 4, 2015 at 8:25 AM, Andy wrote: > Hi, > I’m in the process of deploying DX80 and 70 endpoints tha

Re: [cisco-voip] RTMT logs for disconnect signal of RCC

Jefflin, Usually you just want to hit Default then set trace level to Detailed. If SIP is involved, also want to enable SIP Stack trace. Having all the default traces enabled just makes sure nothing gets missed. Brian On Tue, Feb 3, 2015 at 11:29 PM, Jefflin Choi wrote: > Thanks all. we are

Re: [cisco-voip] Selfprovisioning

I know I'm dredging this one up, but to contribute to the knowledge base here - the IVR service will log a message with "isAlreadyProvisioned" anyways, regardless of if it is or if it isn't. The error message about associating the device to the account is related to the end user profile in so

[cisco-voip] DX series endpoints registered with cucm

Hi, I’m in the process of deploying DX80 and 70 endpoints that are registered to CUCM, that piece is ok. I can place calls between them and audio conferencing is fine, my issue is with a conference with video……. I have an MCU5310 running version 4.5(1.45) which I have registered with CUCM 9.1.2