[SIP Beyond VoIP] Notify - 403 Forbidden response

Saúl Ibarra Corretgé saul at ag-projects.com
Wed Jan 2 09:47:41 CET 2013


Hi,

Are you referring to the 403 in the *body* of the NOTIFY request? If so it means that SylkServer got a 403 when it tried to add the new user to the conference, so you should inspect the traffic between SylkServer and the invited user's server.


Regards,

On Dec 17, 2012, at 5:58 PM, Nitin Jain wrote:

> Hi,
>  
>  
> I upgraded the Sylk Server to 2.2.1 still we are getting 403 Forbidden response. Please find below the wire shark trace.
>  
>  
> REFER sip:conference at 172.16.103.42 SIP/2.0
> Via: SIP/2.0/UDP 10.203.147.10:5060;branch=z9hG4bK642456048-1798
> Route: <sip:172.16.103.21;lr;ftag=ICF_637518048-1796>
> Max-Forwards: 70
> Supported: replaces,199
> From: <sip:nitin at 172.16.103.21>;tag=ICF_637518048-1796
> To: <sip:conference at 172.16.103.42>;tag=tJhxfm-u5YNxtS9Rw2ZyW4NdgKU5y6Jd
> Call-ID: 637518048-1794 at 10.203.147.10
> CSeq: 2 REFER
> Contact: <sip:nitin at 10.203.147.10;transport=udp>
> Refer-To: <sip:1 at 172.16.103.21;method=INVITE>
> Referred-By: <sip:nitin at 172.16.103.21>
> Allow: INVITE,ACK,CANCEL,BYE,OPTIONS,REFER
> Content-Length: 0
>  
>  
> SIP/2.0 202 Accepted
> Via: SIP/2.0/UDP 10.203.147.10:5060;branch=z9hG4bK642456048-1798
> Record-Route: <sip:172.16.103.21;lr;ftag=ICF_637518048-1796>
> Call-ID: 637518048-1794 at 10.203.147.10
> From: <sip:nitin at 172.16.103.21>;tag=ICF_637518048-1796
> To: <sip:conference at 172.16.103.42>;tag=tJhxfm-u5YNxtS9Rw2ZyW4NdgKU5y6Jd
> CSeq: 2 REFER
> Contact: <sip:conference at 172.16.103.42>;isfocus
> Allow: SUBSCRIBE, NOTIFY, PRACK, INVITE, ACK, BYE, CANCEL, UPDATE, MESSAGE, REFER
> Supported: 100rel, replaces, norefersub, gruu
> Server: SylkServer-2.2.1
> Content-Length:  0
>  
>  
> NOTIFY sip:nitin at 10.203.147.10;transport=udp SIP/2.0
> Record-Route: <sip:172.16.103.21;lr=on;ftag=tJhxfm-u5YNxtS9Rw2ZyW4NdgKU5y6Jd>
> Via: SIP/2.0/UDP 172.16.103.21;branch=z9hG4bK708f.41643576.0
> Via: SIP/2.0/UDP 172.16.103.42:5060;rport=5060;branch=z9hG4bKPjm8GlJEexLBEgduHeXooDBGUR4mC6htjs
> Max-Forwards: 69
> From: <sip:conference at 172.16.103.42>;tag=tJhxfm-u5YNxtS9Rw2ZyW4NdgKU5y6Jd
> To: <sip:nitin at 172.16.103.21>;tag=ICF_637518048-1796
> Contact: <sip:conference at 172.16.103.42>;isfocus
> Call-ID: 637518048-1794 at 10.203.147.10
> CSeq: 495 NOTIFY
> Event: refer
> Subscription-State: active;expires=90
> Allow-Events: conference, refer, presence
> User-Agent: SylkServer-2.2.1
> Content-Type: message/sipfrag;version=2.0
> Content-Length:    20
> P-hint: rr-enforced
>  
>  
> SIP/2.0 100 Trying
> NOTIFY sip:nitin at 10.203.147.10;transport=udp SIP/2.0
> Record-Route: <sip:172.16.103.21;lr=on;ftag=tJhxfm-u5YNxtS9Rw2ZyW4NdgKU5y6Jd>
> Via: SIP/2.0/UDP 172.16.103.21;branch=z9hG4bK408f.a51c2d.0
> Via: SIP/2.0/UDP 172.16.103.42:5060;rport=5060;branch=z9hG4bKPje0OwByP7An3WrbzjDdK5w9V82I8sRMNM
> Max-Forwards: 69
> From: <sip:conference at 172.16.103.42>;tag=tJhxfm-u5YNxtS9Rw2ZyW4NdgKU5y6Jd
> To: <sip:nitin at 172.16.103.21>;tag=ICF_637518048-1796
> Contact: <sip:conference at 172.16.103.42>;isfocus
> Call-ID: 637518048-1794 at 10.203.147.10
> CSeq: 496 NOTIFY
> Event: refer
> Subscription-State: terminated;reason=noresource
> Allow-Events: conference, refer, presence
> User-Agent: SylkServer-2.2.1
> Content-Type: message/sipfrag;version=2.0
> Content-Length:    23
> P-hint: rr-enforced
>  
>  
> SIP/2.0 403 Forbidden
> NOTIFY sip:nitin at 10.203.147.10;transport=udp SIP/2.0
> Record-Route: <sip:172.16.103.21;lr=on;ftag=tJhxfm-u5YNxtS9Rw2ZyW4NdgKU5y6Jd>
> Via: SIP/2.0/UDP 172.16.103.21;branch=z9hG4bK708f.41643576.0
> Via: SIP/2.0/UDP 172.16.103.42:5060;rport=5060;branch=z9hG4bKPjm8GlJEexLBEgduHeXooDBGUR4mC6htjs
> Max-Forwards: 69
> From: <sip:conference at 172.16.103.42>;tag=tJhxfm-u5YNxtS9Rw2ZyW4NdgKU5y6Jd
> To: <sip:nitin at 172.16.103.21>;tag=ICF_637518048-1796
> Contact: <sip:conference at 172.16.103.42>;isfocus
> Call-ID: 637518048-1794 at 10.203.147.10
> CSeq: 495 NOTIFY
> Event: refer
> Subscription-State: active;expires=90
> Allow-Events: conference, refer, presence
> User-Agent: SylkServer-2.2.1
> Content-Type: message/sipfrag;version=2.0
> Content-Length:    20
> P-hint: rr-enforced
>  
>  
> Regards,
> Nitin
>  
> From: ANIL KARADAĞ [mailto:anil.karadag at gmail.com] 
> Sent: Monday, December 17, 2012 2:24 PM
> To: Nitin Jain
> Subject: Re: [SIP Beyond VoIP] Notify - 403 Forbidden response
>  
> Hi Nitin,
>  
>  
> Onur found the problematic line, please see [1]. And i think if sylkserver v1.3.0 has the same line, you can modify it to fix the problem. 
>  
>  
>  
> [1] http://lists.ag-projects.com/pipermail/sipbeyondvoip/2012-October/002374.html
>  
>  
> thanks
> 
> On Mon, Dec 17, 2012 at 9:09 AM, Nitin Jain <nitin1.jain at aricent.com> wrote:
> Hi  Anil ,
>  
> Thanks for the reply. I have searched the mailing list and found out that there it was  version 2.1.0 of Sylk server  where as we are using 1.3.0
>  
> So just wanted to know whether version 1.3.0 supports add participant or not or do we need to  install 2.1.0 or higher?
>  
>  
>  
> Regards
> Nitin
>  
> From: ANIL KARADAĞ [mailto:anil.karadag at gmail.com] 
> Sent: Monday, December 17, 2012 12:23 PM
> To: Nitin Jain
> Cc: sipbeyondvoip at lists.ag-projects.com
> Subject: Re: [SIP Beyond VoIP] Notify - 403 Forbidden response
>  
> Hi Nitin,
>  
>  
> I think your case is same with [1]. In addition please search your problem in the archives of the mail list[2] before sending.
>  
>  
>  
> [1] http://lists.ag-projects.com/pipermail/sipbeyondvoip/2012-October/002360.html
>  
> [2] http://lists.ag-projects.com/pipermail/sipbeyondvoip/
>  
>  
> thanks
> 
> On Sat, Dec 15, 2012 at 8:29 PM, Nitin Jain <nitin1.jain at aricent.com> wrote:
> Hi all,
> 
> 
> I am trying to add a participant to the conference by sending REFER request after initial conference creation .
> 
> Sequence is as below:-
> 
> 
> 1  Invite request  / 200 Ok response
> 
> 2. Refer request / 202 accepted response
> 
> 3. Notify 100 trying / Notify 403 Forbidden from sylk server
> 
> However server is not sending INVITE to the other user mention in the Refer-To header field of REFER request.
> 
> Also I am using our own client for conference creation and OpenSer server.
> 
> So all request /response go through Openser sip server which is running on system other than on which Sylk server is running.
> 
> Is there any configuration I need to change ?
> 
> 
> Regards
> Nitin
> 
> .
> 
> 
> 
> 
> 
> 
> 
> ===============================================================================
> Please refer to http://www.aricent.com/legal/email_disclaimer.html
> for important disclosures regarding this electronic communication.
> ===============================================================================
> _______________________________________________
> SIPBeyondVoIP mailing list
> SIPBeyondVoIP at lists.ag-projects.com
> http://lists.ag-projects.com/mailman/listinfo/sipbeyondvoip
> 
> 
>  
> -- 
> Anıl KARADAĞ
> http://anilkaradag.info/blog
> 
> 
> 
> 
> ===============================================================================
> Please refer to http://www.aricent.com/legal/email_disclaimer.html
> for important disclosures regarding this electronic communication.
> ===============================================================================
> 
> 
>  
> -- 
> Anıl KARADAĞ
> http://anilkaradag.info/blog
> 
> 
> 
> 
> ===============================================================================
> Please refer to http://www.aricent.com/legal/email_disclaimer.html
> for important disclosures regarding this electronic communication.
> ===============================================================================
> _______________________________________________
> SIPBeyondVoIP mailing list
> SIPBeyondVoIP at lists.ag-projects.com
> http://lists.ag-projects.com/mailman/listinfo/sipbeyondvoip

-- 
Saúl Ibarra Corretgé
AG Projects







More information about the SIPBeyondVoIP mailing list