This is the rule i saw in forums,

>From 3261:

callid = word [ "@" word ]

word = 1*(alphanum / "-" / "." / "!" / "%" / "*" /
"_" / "+" / "`" / "'" / "~" /
"(" / ")" / "<" / ">" /
":" / "\" / DQUOTE /
"/" / "[" / "]" / "?" /
"{" / "}" )

alphanum = ALPHA / DIGIT

All of the mechanisms specified in this document are described in
both prose and an augmented Backus-Naur Form (BNF) defined in RFC
2234 [10]. Section 6.1 of RFC 2234 defines a set of core rules that
are used by this specification, and not repeated here. Implementers
need to be familiar with the notation and content of RFC 2234 in
order to understand this specification. Certain basic rules are in
uppercase, such as SP, LWS, HTAB, CRLF, DIGIT, ALPHA, etc. Angle
brackets are used within definitions to clarify the use of rule
names.

So I thought theremay be a explicit rule defined for call-id generation


Srikanth

On Wed, Oct 19, 2011 at 1:02 PM, Brandon W. Yuille <[email protected]>wrote:

> **
> Hi,
>
> The call id just needs to be a semi-unique identifier. The method for
> generating this is application specific, so there are no requirements for
> this value other than it should be unique in space and time. A common method
> I see in many sip applications is to generate a random value most likely
> also containing the current time concatenated with the ip address or host
> address of the application that is generating the call id.
>
> Example: "Call-ID: [email protected]" or "Call-ID:
> [email protected]"
>
> In that example imagine 0123456789abcdef is a base 16 sudo random number
> with a timestamp mixed in. You could use any base you'd like or come up with
> any form of more uniqueness.
>
> Hope this helps,
> Brandon
>
>
> Srikanth satturi wrote:
>
> anyone please
>
> On Wed, Oct 19, 2011 at 12:40 PM, Srikanth satturi 
> <[email protected]> wrote:
>
>
>
>  Could please anyone help  me out
>
>
> On Wed, Oct 19, 2011 at 12:23 PM, Srikanth satturi 
> <[email protected]> wrote:
>
>
>
>  Could anyone please give me rules for sip call id generation, in RFC 3261
> it is not clear, can i find specs anywhere. Please help me out
>
> --
> Srikanth satturi
>
>
>
>  --
> Srikanth satturi
>
>
>
>


-- 
Srikanth satturi
_______________________________________________
Sip-implementors mailing list
[email protected]
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors

Reply via email to