[recon-devel] telephone-event payload format ID 104?

[Daniel Pocock]

I've noticed that reCon is using payload ID 104 (instead of the more
common 101) for telephone-event.

When it starts up, it logs

Added codec to session capabilities: id=110 type=TELEPHONE-EVENT
rate=8000 plen=20000 payloadid=104 fmtp=0-15

and when it sends an INVITE, the id in the SDP is 104

Is there any reason for this? Is it likely to cause interoperability
problems for anybody?

The id 110 comes from an enum in sipXtapi (in SdpCodec.h) but this
doesn't appear to relate directly to the payload format ID

[Scott Godin]

The payload type comes from sipXtapi. See
ConverstaionManager::buildSessionCapabilities:
codec.payloadType() = sdpcodec->getCodecPayloadFormat();

It will dynamically generate payload id's based on the list of supported
codecs and whether each codec has a static type/id or not: see
SdpCodecList::bindPayloadTypes() in sipXSdpLib.

Anyone that properly implements dynamic payload types should not have an
issue with this.

Scott

Post by Daniel Pocock
I've noticed that reCon is using payload ID 104 (instead of the more
common 101) for telephone-event.
When it starts up, it logs
Added codec to session capabilities: id=110 type=TELEPHONE-EVENT
rate=8000 plen=20000 payloadid=104 fmtp=0-15
and when it sends an INVITE, the id in the SDP is 104
Is there any reason for this? Is it likely to cause interoperability
problems for anybody?
The id 110 comes from an enum in sipXtapi (in SdpCodec.h) but this
doesn't appear to relate directly to the payload format ID
_______________________________________________
recon-devel mailing list
List Archive: http://list.resiprocate.org/archive/recon-devel/