Re: [cisco-voip] Columbia CUBE to Claro outbound issue

2016-04-03 Thread Hank Keleher (AM)
n Cc: cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net> Subject: Re: [cisco-voip] Columbia CUBE to Claro outbound issue Yeah, I have. Everything points to the issue being on their side but of course they say everything is okay as long as we’re doing this, that and the other. Which

Re: [cisco-voip] Columbia CUBE to Claro outbound issue

2016-04-03 Thread Ryan Huff
alf of Hank Keleher (AM) <hank.kele...@dimensiondata.com> Sent: Sunday, April 3, 2016 8:35 PM To: Daniel Pagan; Horton, Jamin Cc: cisco-voip@puck.nether.net Subject: Re: [cisco-voip] Columbia CUBE to Claro outbound issue Yeah, I have. Everything points to the issue being on their side but

Re: [cisco-voip] Columbia CUBE to Claro outbound issue

2016-04-03 Thread Hank Keleher (AM)
;cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net>" <cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net>> Subject: RE: [cisco-voip] Columbia CUBE to Claro outbound issue Personally, I would push back to them and simply provide them with the request

Re: [cisco-voip] Columbia CUBE to Claro outbound issue

2016-04-03 Thread Daniel Pagan
orton, Jamin <jamin.hor...@oneneck.com> Cc: cisco-voip@puck.nether.net Subject: Re: [cisco-voip] Columbia CUBE to Claro outbound issue I tried hard coding both UDP and TCP. Setting it to UDP produced the same result where as TCP had the same CC disconnect of 53 and SIP disconnect cause

Re: [cisco-voip] Columbia CUBE to Claro outbound issue

2016-04-02 Thread Hank Keleher (AM)
voip@puck.nether.net>" <cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net>> Subject: Re: [cisco-voip] Columbia CUBE to Claro outbound issue I just had this same issue yesterday. 2 hours later after banging my head against they keyboard I figured out it was my se

Re: [cisco-voip] Columbia CUBE to Claro outbound issue

2016-04-02 Thread Horton, Jamin
uot; <hank.kele...@us.didata.com<mailto:hank.kele...@us.didata.com>> Cc: "cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net>" <cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net>> Subject: Re: [cisco-voip] Columbia CUBE to Claro outbound

Re: [cisco-voip] Columbia CUBE to Claro outbound issue

2016-04-02 Thread Hank Keleher (AM)
016 at 13:30 To: "Hank.Keleher" <hank.kele...@us.didata.com<mailto:hank.kele...@us.didata.com>> Cc: "cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net>" <cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net>> Subject: Re: [cisco

Re: [cisco-voip] Columbia CUBE to Claro outbound issue

2016-04-02 Thread Ryan Huff
Are you always getting the same 404 "unallocated number" response? Thanks, Ryan > On Apr 2, 2016, at 1:05 PM, Hank Keleher (AM) > wrote: > > Greetings! > > Does anyone have a CUBE configuration that works with Claro based in Columbia > you can share with me?

[cisco-voip] Columbia CUBE to Claro outbound issue

2016-04-02 Thread Hank Keleher (AM)
Greetings! Does anyone have a CUBE configuration that works with Claro based in Columbia you can share with me? I have inbound working just fine but oubound keeps getting rejected. Below is an example of the config and relevant debug. They are saying that it should work even though I’ve