We now have some Vitelity DIDs failing, and this is on their site:
Monday April 18th 2016, 1:56pm MDT -We have worked with our partner to
resolve the intermittent inbound call completion. Calls are now completing
correctly. If you are still experiencing any issues please open a trouble
ticket
One of the features of the way marketing has worked for the last hundred years
is that every once in a while somebody will call BS when the needle gets too
high with folks parroting vendor whitepapers and collateral.
They are largely ignored, have little no material impact on the planet or
Thanks bud.
On Mon, Apr 18, 2016 at 10:20 AM, Carlos Alvarez
wrote:
> We have a few thousand of them and no reports of trouble. I'm looking
> right now at a different issue so I'm watching a lot of Onvoy calls coming
> in without anything looking wrong.
>
>
> On Mon, Apr
We have a few thousand of them and no reports of trouble. I'm looking
right now at a different issue so I'm watching a lot of Onvoy calls coming
in without anything looking wrong.
On Mon, Apr 18, 2016 at 8:34 AM, Reinventing Rich wrote:
> Or is it just vitelity
Or is it just vitelity again >.<
--
Cheers,
Rich Breton
Give a man a program, you will frustrate him for a day;Teach him how to
program, you will frustrate him for a lifetime.
___
VoiceOps mailing list
VoiceOps@voiceops.org
If the customer truly has an SBC I don’t see why you couldn’t put the Carrier
information in the SDP going out to the customer. Same thing going back,
Customer SDP on 200 OK back to the carrier. Most customers in Hosted PBX
don’t have an SBC however, they have a dumb firewall. In the
Hello,
Is there a mechanism to achieve media bypass from the customer premise SBC
to peering/carrier SBC where in a typical NAT traversal hosted PBX
deployment?
I am talking about multi-vendor SBCs on the access and the peering sides.
Thanks,
Kumudu