[sr-dev] mediaproxy-ng Got LOOKUP, but no usable callstreams found

Richard Fuchs rfuchs at sipwise.com
Mon Oct 28 20:54:44 CET 2013


On 10/28/13 11:59, Juha Heinanen wrote:
> Richard Fuchs writes:
> 
>> Possibly it's because of the non-standard RTCP port in the answer.
>> Technically this is supported but the implementation is more of a hack
>> than anything else for the time being.
> 
> looks like the rtpc port number in 200 ok is not "non-standard"
> anymore.  from rfc 3605 dated october 2003:

That's not what I meant with "non standard". Maybe I should have said:
explicitly specified as a port not equal to the implicit port. But that
would have been too long of a sentence :)

cheers

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 897 bytes
Desc: OpenPGP digital signature
URL: <http://lists.sip-router.org/pipermail/sr-dev/attachments/20131028/a5837a01/attachment.pgp>


More information about the sr-dev mailing list