Crypto Tag Default about rtpengine HOT 4 CLOSED

Hey,

The ABNF notation of 1*9DIGIT means between 1 and 9 digits, where a digit is defined as 0-9 (RFC4234). This means that a tag of "0" should be valid. The only restriction the RFC places on the tag is that leading zeroes must not be used. Now I don't know if that disqualifies "0" as a valid tag, I'd say it's ambiguous at best.

As such, I think a good client should accept "0" as a valid tag, but as for offering, it's probably safer to start at 1, even though there seem to be other clients out there which also put a "0" tag.

from rtpengine.

Great, thanks for the quick clarification. I suppose if a client starts at 0 in an offer then it would probably accept 0 in the response but the client I'm using starts at 1 in an offer and doesn't seem to like offers with 0.

Could this default be changed ? Sorry, I'm not sure how of the process.

from rtpengine.

Yeah I'll change it, just making sure that there are no negative side effects to this.

You may still want to submit a bug report for your client though. AFAICT, zero is a valid tag and a client should always accept it, even if the client itself prefers to offer with a "1" tag.

from rtpengine.

Thanks for your help, that's great.

from rtpengine.