Subject: [Sipping] Comments on draft draft-ietf-sipping-service-examples-13.txt (sec 2.7, 2.8, 2.9)

From: "Nataraju A.B." <[email-masked]>
Date: Thu, 20 Sep 2007 14:12:16 +0100 (BST)

All, 
Here are few comments about the draft draft-ietf-sipping-service-examples-13.txt
   
  2.7.  Call Forwarding Unconditional
  
<sec 2.7>
     Note that the 181 Call is Being Forwarded response does not have a To
   tag added as the proxy does not wish to establish an early dialog
   with Alice.  Strictly speaking, the proxy is behaving as a User Agent
   in this case as a proxy can not generate non-100 provisional
   responses.
   
        F3 (181 Call is Being Forwarded) Proxy -> Alice
        SIP/2.0 181 Call is Being Forwarded
      Via: SIP/2.0/TLS client.atlanta.example.com:5061
       ;branch=z9hG4bK74bf9
       ;received=192.0.2.103
      From: Alice <sips:[email-masked]>;tag=1234567
      To: Bob <sips:[email-masked]>;tag=9214d
      Call-ID: [email-masked]
      CSeq: 1 INVITE
      Content-Length: 0
  </sec 2.7>
   
  Inconsistent statement for 181 response (to-tag)....
   
  same comment is applicable for sec 2.8 and 2.9 also... 
sec "2.8. Call Forwarding - Busy" 
sec "2.9.  Call Forwarding - No Answer"
   
  I think its better to send the 181 with tag and later terminate the dialog with a BYE request. 
  Anyways sending 181 violates the basic proxy functionality, if we decide to send 181 then it would be better to send the response with tag and then terminate early dialog with a BYE.
   
  Simplest option would be to remove the tag in the 181 response....
   
  Thanks,
  Nataraju A B

 Send instant messages to your online friends http://uk.messenger.yahoo.com 

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use [email-masked] for questions on current sip
Use [email-masked] for new developments of core SIP