When I last did any interop testing on Vector, 101 was in my SDP offers (0 8 18 101), and we were able to select that. I think that L3's preference on Viper was inband, but RFC2833 should be available on Vector as long as it's part of your "profile". Since the Vector platform is based on Sonus, L3 may have been reluctant to set this up early on based on some of the RFC2833 issues referenced in today's other thread on the topic. In general with L3 ELS/LI, if you don't have a feature you think should be included, your SE can help get the changes made to your signaling profile. -Scott -----Original Message----- From: voiceops-bounces at voiceops.org [mailto:voiceops-bounces at voiceops.org] On Behalf Of Brian Sneddon Sent: Friday, August 07, 2009 11:20 AM To: voiceops at voiceops.org Subject: Re: [VoiceOps] Level3 VECTOR and RFC2833 I was specifically informed when migrating to Vector a couple years ago that RFC2833 was not supported on the platform. We had been using it extensively on Viper. If this has changed now I'd love to switch back to 2833, but I'm not too hopeful. :) Brian ----- "David Hiers" <David_Hiers at adp.com> wrote:

Hi You VECTORed people,

What that rumbling I heard about VECTOR not supprting RFC2833 DTMF?

Real? Myth? Dream?

David

This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail and delete the message and any attachments from your system.

_______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org https://puck.nether.net/mailman/listinfo/voiceops

VoiceOps mailing list VoiceOps at voiceops.org https://puck.nether.net/mailman/listinfo/voiceops