[Blink] telephone events 101

Jeff Pyle jpyle at fidelityvoice.com
Mon Nov 25 17:34:48 CET 2013

Same experience here.  It was a member of the UC line although I can't
remember if it was UC3xx or UC5xx.  As I recall the payload number was
configurable, but static nonetheless.

The customer with the UC system took it back to Cisco as a bug, and to the
best of my knowledge they accepted it as such to be addressed in a future

The real world indeed.   In this case the real world was a collection of
different endpoints Sonus, Adtran, Asterisk, Freeswitch, Metaswitch,
Polycom and Blink endpoints, most using 101, but some not.  All playing by
the same rules except the UC box.  Lovely.

- Jeff

On Mon, Nov 25, 2013 at 11:27 AM, Andreas Sikkema <asikkema at unet.nl> wrote:

> > No, there is no way for changing this. The telephone-event uses a
> dynamic payload, endpoints should just use the one advertised. We haven't
> found any interoperability issues related to this until now.
> >
> > Out of curiosity, what media server are you using?
> I have seen some Cisco IOS based hardware not playing nice when using
> other payload types than what it expects, especially when some strange
> Cisco proprietary functionality related to payload types has been
> enabled.
> I know these could be considered bugs, but this is the real world ;-)
> --
> Andreas Sikkema
> Senior Service Engineer
> UNET, Almere, the Netherlands
> +31 36 845 4558
> mail: asikkema at unet.nl
> sip: asikkema at unet.nl
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ag-projects.com/pipermail/blink/attachments/20131125/935e340d/attachment.html>

More information about the Blink mailing list