[SIP Beyond VoIP] Add participants to conference issue

Saúl Ibarra Corretgé saul at ag-projects.com
Mon Feb 25 11:14:52 CET 2013


On Feb 25, 2013, at 11:11 AM, Ram Anji wrote:

> Thanks for the response.  
> 
> In my case INVITE is not initiated to the participant from sylkserver. That's the reason i am not added in the diagram.
> 
> Here I am enclosed the trace at sylkserver.
> 
> 
> And Following is the SUBSCRIBE request and response. tell me what is the wrong in subscribe request.
> 

The RURI is wrong. It doesn't have the URI of an existing room so it's discarded. Also, it has to be sent out of dialog.

> 
> 
> #
> U 2013/02/25 14:56:51.338465 192.168.41.104:5060 -> 192.168.41.104:5090
> SUBSCRIBE sip:192.168.41.104;lr SIP/2.0

^^^ The RURI should point to the room you are subscribing to.

> Via: SIP/2.0/UDP 192.168.41.104;branch=z9hG4bK14ff.8eeaad1.0
> Via: SIP/2.0/UDP 192.168.41.104;branch=z9hG4bK14ff.7eeaad1.0
> Via: SIP/2.0/UDP 192.168.41.87:5060;rport=5060;branch=z9hG4bKf364754e00016
> From: "102"<sip:102 at 192.168.41.104>;tag=ad638bca
> To: <sip:conf at 192.168.41.104>;tag=Em6h9UJEvGQscvNpU41FYKWVz6SDHqcn

^^^ Apparently you sent this in-dialog. That is not supported and actually discouraged, you should send it outside of the INVITE dialog.

> Call-ID: 4531014b-3 at 192.168.41.87
> CSeq: 436296327 SUBSCRIBE
> Max-Forwards: 68
> Contact: "102"<sip:102 at 192.168.41.87:5060>
> User-Agent: mycompany/2.0
> P-Access-Network-Info: IEEE-802.3
> Event: conference
> Expires: 180
> Allow: INVITE,ACK,BYE,CANCEL,REFER,NOTIFY,OPTIONS,PRACK,UPDATE,INFO,MESSAGE,SUBSCRIBE,SERVICE,PING,PUBLISH
> Allow-Events: refer, presence
> Supported: 100rel, replaces, join, eventlist, histinfo
> Proxy-Authorization: Digest username="102", realm="192.168.41.104", nonce="USsvglErLlb4ftyYbWXLCYk8Ca4XoRoN", uri="sip:conf at 192.168.41.104", algorithm=MD5, response="0b0c842af8ed47ee987011ff913a2852"
> Date: Mon, 25 Feb 2013 09:26:52 GMT
> Content-Length: 0
> 
> 
> 
> #
> U 2013/02/25 14:56:51.354368 192.168.41.104:5090 -> 192.168.41.104:5060
> SIP/2.0 500 Unhandled by dialog usages
> Via: SIP/2.0/UDP 192.168.41.104;received=192.168.41.104;branch=z9hG4bK14ff.8eeaad1.0
> Via: SIP/2.0/UDP 192.168.41.104;branch=z9hG4bK14ff.7eeaad1.0
> Via: SIP/2.0/UDP 192.168.41.87:5060;rport=5060;branch=z9hG4bKf364754e00016
> Call-ID: 4531014b-3 at 192.168.41.87
> From: "102" <sip:102 at 192.168.41.104>;tag=ad638bca
> To: <sip:conf at 192.168.41.104>;tag=Em6h9UJEvGQscvNpU41FYKWVz6SDHqcn
> CSeq: 436296327 SUBSCRIBE
> Server: SylkServer-2.3.0
> Content-Length:  0
> 
> 
> 
> 
> On Fri, Feb 22, 2013 at 8:20 PM, Saúl Ibarra Corretgé <saul at ag-projects.com> wrote:
> 
> On Feb 22, 2013, at 3:35 PM, Ram Anji wrote:
> 
> > Hi,
> >
> > I am integrated sylkserver with kamailio server for conference. Here i am facing issues while adding participants to conference by using REFER.
> >
> > Following is event flow for my conference and refer request with sylkserver. Here I am getting forbidden in NOTIFY, and no call is initiated to participants.
> >
> > Please suggest me if there is any changes required at sylkserver.
> >
> >
> 
> Hi Ram,
> 
> SylkServer doesn't seem to like the SUBSCRIBE request you are sending, hence the 400 response. Also, the 403 seems to be the pyload of the NOTIFY, that is, the response code that the generated INVITE (not shown in the diagram) got. Can you please share a SIP trace for this scenario? You may send it to me privately if it contains sensible data.
> 
> 
> Regards,
> 
> --
> Saúl Ibarra Corretgé
> AG Projects
> 
> 
> 
> 
> <2>

--
Saúl Ibarra Corretgé
AG Projects





More information about the SIPBeyondVoIP mailing list