Hi,
The syntax for the callid value in RFC3261 is "word [ "@" word ]". The
use of the "localid@host" format is simply one way to make the string
value unique, so is there a reason you want to "split" the value into
different parts (localid, host etc) in the first place?
The "@" character is to my understanding NOT part of "word", so
according to RFC3261 "Call-ID:
87602@[EMAIL PROTECTED]" is not a valid Call-ID value
- no matter which part of the string value you would treat as localid
and which part you treat as host...
word = 1*(alphanum / "-" / "." / "!" / "%" / "*" / "_" / "+" /
"`" / "'" / "~" / "(" / ")" / "<" / ">" / ":" / "\" / DQUOTE / "/" / "["
/ "]" / "?" / "{" / "}" )
I don't remember what RFC2543 says about the use of the "@" character in
the Call-ID value, and I don't have the document in front of me, so
unfortunately I can't comment on any possible backward compability
issue.
Regards,
Christer Holmberg
Ericsson Finland
_______________________________________________
Sip-implementors mailing list
[EMAIL PROTECTED]
http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
