[SIP Beyond VoIP] Notify - 403 Forbidden response

Nitin Jain nitin1.jain at aricent.com
Wed Jan 2 12:22:10 CET 2013

Hi Saúl,

Thanks a lot for your reply.

As per the RFC , I need to send the REFER to conference URI which I will get in contact header of 200 OK.

Conference URI should be different from Conference factory URI in INVITE request Line.

However from Sylkserver trace , both conference uri and conference factory uri are same.

INVITE sip:conference at SIP/2.0

SIP/2.0 200 OK
Contact: <sip:conference at>;isfocus

Please let me know in case any configuration is required so that Sylkserver

should send different conference URI other than conference factory URI.


-----Original Message-----
From: Saúl Ibarra Corretgé [mailto:saul at ag-projects.com]
Sent: Wednesday, January 02, 2013 4:04 PM
To: Nitin Jain
Cc: sipbeyondvoip at lists.ag-projects.com
Subject: Re: [SIP Beyond VoIP] Notify - 403 Forbidden response


On Jan 2, 2013, at 10:44 AM, Nitin Jain wrote:

> Hi ,
> Please find attached the wireshark trace at Sylkserver. Sylkserver did not send INVITE to the user mentioned in the Refer-To Header.
> Also from sylkserver notification trace It looks that Sylkserver is trying to transfer the call.


> Only Difference I could see between working logs(sip simple client) and non working logs (Our own Sip Client) are
> 1. Sip simple client subscribe to conference event package where as our client don't

This is not needed.

> 2. SIP simple Client sends REFER to server out of dialog where as Our client send REFER to server in dialog.

This is the problem. Inviting participants must be done with an out of dialog REFER, as per RFC4579 (sec 5.5). In dialog REFER requests are rejected by SylkServer.


Saúl Ibarra Corretgé
AG Projects

Please refer to http://www.aricent.com/legal/email_disclaimer.html
for important disclosures regarding this electronic communication.

More information about the SIPBeyondVoIP mailing list