Re: [Sip-implementors] error 488

Hi Somesh , Thanks , I am getting it checked ,will revert later. Thanks, Best Regards sAlil veRmA -Original Message- From: Shanbhag, Somesh (NSN - IN/Bangalore) Sent: Tuesday, July 05, 2011 11:14 AM To: Verma, Salil (NSN - IN/Gurgaon) Cc: sip-implementors@lists.cs.columbia.edu Su

Re: [Sip-implementors] error 488

The traces indicate the cause value of 65 in Q.850 which states "Bearer capability not implemented". This means UAS didn't like one of the fields in the following: Access transport (9 bytes length) Optional Parameter: 3 (Access transport)

Re: [Sip-implementors] Call Transfer In dialog REFER

Hi Isshed, For your 3rd query, Referred-by is populated by Party A (in dialog 1 with B) in REFER request so that when party C receives INVITE from Party B (in dialog 3), then it comes to know that this call has been referred to him. In that scenario, Party C may require to apply some policies o

Re: [Sip-implementors] Regarding Subscription Termination

Hi Brett Thanks for the reply. In our call scenario(Blind Call Transfer), Core Network is sending REFER to AS. AS replies with 202 Accepted Message followed by BYE Message to Core Network. As per the below description, AS has to send NOTIFY and Core network has to reject it in order to cancel th

[Sip-implementors] Call Transfer In dialog REFER

Hi All, Below are the call flow of a consultative call transfer using in dialog REFER. Transferor---TransfereeTarget 1) <==INVITE/200/ACk=>(dialog 1) 2) transferor puts it

Re: [Sip-implementors] error 488

Would need to see the request to provide more details. > We are getting this cause Reason: Q.850;cause=65 > We are getting error 488 (not acceptable media ) when > ever we make a call. > > Any suggestion . The following is a snippet from RFC 3398 section 7.2.4.1 ISDN Cause Code to Status

Re: [Sip-implementors] Regarding Subscription Termination

> But, in RFC 5589, it is specified that we can terminate > the subscription using BYE. The above statement is not a correct interpretation of the RFC 5589 snippet. The BYE does not terminate the subscription. However as indicated by RFC 3515 section 2.4.4, the Transferor can terminate the su

Re: [Sip-implementors] Regarding Subscription Termination

Hi Experts In RFC 5057, it is mentioned that BYE cannot be used to terminate the subscription created by REFER. Normal termination of a usage has no effect on other usages sharing the same dialog. For instance, terminating a subscription with a NOTIFY/Subscription-State: terminated

Re: [Sip-implementors] error 488

Please do attach the callflow with messages. Thanks, Somesh -Original Message- From: Verma, Salil (NSN - IN/Gurgaon) Sent: Monday, July 04, 2011 12:47 PM To: Shanbhag, Somesh (NSN - IN/Bangalore); 'sip-implementors@lists.cs.columbia.edu' Subject: RE: [Sip-implementors] error 488 Hi So

Re: [Sip-implementors] error 488

2011/7/4 Verma, Salil (NSN - IN/Gurgaon) : > We are getting error 488  (not acceptable media ) when ever we make a > call . Is it so hard to open RFC 3261 and search for the meaning of 488 response code?? -- Iñaki Baz Castillo ___ Sip-implementors ma

Re: [Sip-implementors] error 488

Hi Somesh , We are getting this cause Reason: Q.850;cause=65 Thanks, Best Regards sAlil veRmA Tech . Supp. Grp ( Care Team ) NCS : sip: salil.ve...@nsn.com +91 9958298813 0124-4199262 -Original Message- From: Shanbhag, Somesh (NSN - IN/Bangalore) Sent: Monday, July 04, 2011 12:4

Re: [Sip-implementors] error 488

The UAS is not liking the SDP which the UAC has sent. Please send the SDP which the UAC is sending. Most probably, you will have one of the m= lines which it cannot understand. Regards, Somesh -Original Message- From: sip-implementors-boun...@lists.cs.columbia.edu [mailto:sip-impleme

[Sip-implementors] error 488

Hi Experts , We are getting error 488 (not acceptable media ) when ever we make a call . Any suggestion . Thanks, Best Regards sAlil veRmA Tech . Supp. Grp ( Care Team ) NCS : sip: salil.ve...@nsn.com +91 9958298813 0124-4199262 _