Re: [Sip-implementors] Multiple Colon (:) as Header delimiter of name-value

[Pravin Kumar]

Hi Gaurav,

You can refer to RFC3261 Call-ID ABNF syntax section:

[RFC3261 - page 228]

Call-ID  =  ( "Call-ID" / "i" ) HCOLON callid
callid   =  word [ "@" word ]

[RFC3261 - page221]

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

If you observe here ":" is allowed in call-id irrespective to position. So
in your case UAS behaviour is not correct to remove the ":". -pravin


On Thu, Aug 13, 2020 at 2:30 PM Gaurav Khare 
wrote:

> Hi,
>
> I have a specific problem relating to SIP header format.
>
> A UAC is sending Call-ID Header in INVITE as below
> Call-ID: :
> vat4082403130ofbcghefckco...@mscsma1.ims.mnc007.mcc748.3gppnetwork.org
>
> My UAS is sending 180 Ringing response as
> Call-ID:
> vat4082403130ofbcghefckco...@mscsma1.ims.mnc007.mcc748.3gppnetwork.org
>  vat4082403130ofbcghefckco...@mscsma1.ims.mnc007.mcc748.3gppnetwork.org>
>
> Notice the two colons in UAC request. In the response my stack is ignoring
> additional Colon(:) but the response is rejected by UAC. I am perplexed as
> to if colon(:) can be a part of Call-ID value or if two Colons(:) can occur
> sequentially delimiting Header name and value.
>
> If someone can point me to a Section of RFC, it will be very helpful.
>
> Thanks in advance,
> Gaurav Khare
>
>
>
> 
>
> DISCLAIMER: The information in this message is confidential and may be
> legally privileged. It is intended solely for the addressee. Access to this
> message by anyone else is unauthorized. If you are not the intended
> recipient, any disclosure, copying, or distribution of the message, or any
> action or omission taken by you in reliance on it, is prohibited and may be
> unlawful. Please immediately contact the sender if you have received this
> message in error. Further, this e-mail may contain viruses and all
> reasonable precaution to minimize the risk arising there from is taken by
> OnMobile. OnMobile is not liable for any damage sustained by you as a
> result of any virus in this e-mail. All applicable virus checks should be
> carried out by you before opening this e-mail or any attachment thereto.
> Thank you - OnMobile Global Limited.
> ___
> Sip-implementors mailing list
> Sip-implementors@lists.cs.columbia.edu
> https://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
>


-- 
Pravin Kumar

+91-8919863869
___
Sip-implementors mailing list
Sip-implementors@lists.cs.columbia.edu
https://lists.cs.columbia.edu/mailman/listinfo/sip-implementors

[Sip-implementors] Terminating early dialog with BYE.

[Pravin Kumar]

According to RFC 3261:
Early Dialog can be terminate sending by BYE or CANCEL for UAC side.
In case of CANCEL we should send 487 for INVITE

UAC   UAS

-INVITE->
< -180--
--CANCEL--- >
< -200 CANCEL---
< ---487 ---
ACK 487--->

But in the of BYE:

UAC   UAS

---INVITE->
< -180-
--BYE  >
< -200 BYE  ---
<--(what should be send)-   (503 or 487)
ACK ->

So in the case of sending BYE by UAC , UAS should send 503 or 487 for INVITE.

Thanks,
Pravin
___
Sip-implementors mailing list
Sip-implementors@lists.cs.columbia.edu
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors