[SIP Beyond VoIP] Add participants to conference issue

Mon Feb 25 12:24:35 CET 2013

Here is the sip trace for conference. Yes these are also sending in the
same dialog as we need to send INVITE with the same dialog. Also let me
know what is issue in using the same dialog through out the conference.

interface: any
filter: (ip or ip6) and ( port 5090 )
#
U 2013/02/25 15:11:39.051608 192.168.41.104:5060 -> 192.168.41.104:5090
INVITE sip:conf at 192.168.41.104 SIP/2.0
Record-Route: <sip:192.168.41.104;lr=on>
Via: SIP/2.0/UDP 192.168.41.104;branch=z9hG4bKe1ae.8db28817.0
Via: SIP/2.0/UDP 192.168.41.87:5060;rport=5060;branch=z9hG4bK3745c37000012
From: "102"<sip:102 at 192.168.41.104>;tag=b9a43740
To: <sip:conf at 192.168.41.104>
Call-ID: 51b1086e-3 at 192.168.41.87
CSeq: 1679626669 INVITE
Max-Forwards: 69
Contact: "102"<sip:102 at 192.168.41.87:5060>
P-Early-Media: supported
User-Agent: mycompany/2.0
P-Access-Network-Info: IEEE-802.3
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, histinfo
Date: Mon, 25 Feb 2013 09:41:40 GMT
History-Info: <sip:conf at 192.168.41.104>;index=1
Content-Type: application/sdp
Content-Length: 465

v=0
o=- 915513301 813347010 IN IP4 192.168.41.87
s=Voice call
e=me at mycompany.com
c=IN IP4 192.168.41.87
t=0 0
a=sendrecv
m=audio 49000 RTP/AVP 120 105 0 8 18
a=ptime:20
a=maxptime:100
a=sendrecv
a=rtpmap:120 RED/8000
a=fmtp:120 105/105/105/105/105/105/105/105
a=rtpmap:105 AMR/8000
a=fmtp:105
mode-set=0,1,2,3,4,5,6,7;mode-change-neighbor=0;max-red=0;channels=1
a=rtpmap:0 PCMU/8000
a=rtpmap:8 PCMA/8000
a=rtpmap:18 G729/8000
a=fmtp:18 annexb=no

#
U 2013/02/25 15:11:39.062575 192.168.41.104:5090 -> 192.168.41.104:5060
SIP/2.0 100 Trying
Via: SIP/2.0/UDP
192.168.41.104;received=192.168.41.104;branch=z9hG4bKe1ae.8db28817.0
Via: SIP/2.0/UDP 192.168.41.87:5060;rport=5060;branch=z9hG4bK3745c37000012
Record-Route: <sip:192.168.41.104;lr>
Call-ID: 51b1086e-3 at 192.168.41.87
From: "102" <sip:102 at 192.168.41.104>;tag=b9a43740
To: <sip:conf at 192.168.41.104>
CSeq: 1679626669 INVITE
Server: SylkServer-2.3.0
Content-Length:  0

#
U 2013/02/25 15:11:39.068283 192.168.41.104:5090 -> 192.168.41.104:5060
SIP/2.0 180 Ringing
Via: SIP/2.0/UDP
192.168.41.104;received=192.168.41.104;branch=z9hG4bKe1ae.8db28817.0
Via: SIP/2.0/UDP 192.168.41.87:5060;rport=5060;branch=z9hG4bK3745c37000012
Record-Route: <sip:192.168.41.104;lr>
Call-ID: 51b1086e-3 at 192.168.41.87
From: "102" <sip:102 at 192.168.41.104>;tag=b9a43740
To: <sip:conf at 192.168.41.104>;tag=zpnOg.7tpstrcHMiz8qEEhVkIXFHRT8P
CSeq: 1679626669 INVITE
Server: SylkServer-2.3.0
Contact: <sip:conf at 192.168.41.104>
Allow: SUBSCRIBE, NOTIFY, PRACK, INVITE, ACK, BYE, CANCEL, UPDATE, MESSAGE,
REFER
Content-Length:  0

#
U 2013/02/25 15:11:43.101631 192.168.41.104:5090 -> 192.168.41.104:5060
SIP/2.0 200 OK
Via: SIP/2.0/UDP
192.168.41.104;received=192.168.41.104;branch=z9hG4bKe1ae.8db28817.0
Via: SIP/2.0/UDP 192.168.41.87:5060;rport=5060;branch=z9hG4bK3745c37000012
Record-Route: <sip:192.168.41.104;lr>
Call-ID: 51b1086e-3 at 192.168.41.87
From: "102" <sip:102 at 192.168.41.104>;tag=b9a43740
To: <sip:conf at 192.168.41.104>;tag=zpnOg.7tpstrcHMiz8qEEhVkIXFHRT8P
CSeq: 1679626669 INVITE
Server: SylkServer-2.3.0
Allow: SUBSCRIBE, NOTIFY, PRACK, INVITE, ACK, BYE, CANCEL, UPDATE, MESSAGE,
REFER
Contact: <sip:conf at 192.168.41.104>;isfocus
Supported: 100rel, replaces, norefersub, gruu
Content-Type: application/sdp
Content-Length:   179

v=0
o=- 3570774103 3570774104 IN IP4 192.168.41.104
s=SylkServer-2.3.0
c=IN IP4 192.168.41.104
t=0 0
m=audio 50028 RTP/AVP 0
a=rtcp:50029
a=rtpmap:0 PCMU/8000
a=sendrecv

#
U 2013/02/25 15:11:43.115651 192.168.41.104:5060 -> 192.168.41.104:5090
ACK sip:192.168.41.104;lr SIP/2.0
Via: SIP/2.0/UDP 192.168.41.104;branch=z9hG4bKcydzigwkX
Via: SIP/2.0/UDP 192.168.41.87:5060;rport=5060;branch=z9hG4bK345e6b6900013
From: "102"<sip:102 at 192.168.41.104>;tag=b9a43740
To: <sip:conf at 192.168.41.104>;tag=zpnOg.7tpstrcHMiz8qEEhVkIXFHRT8P
Call-ID: 51b1086e-3 at 192.168.41.87
CSeq: 1679626669 ACK
Max-Forwards: 69
User-Agent: mycompany/2.0
Proxy-Authorization: Digest username="102", realm="192.168.41.104",
nonce="USsy/lErMdKd2dH+Nht+6yED0eytILs8", uri="sip:conf at 192.168.41.104",
algorithm=MD5, response="32e9a52e57a21a3b3b64ce1be0306cf0"
Date: Mon, 25 Feb 2013 09:41:44 GMT
History-Info: <sip:conf at 192.168.41.104>;index=1
Content-Length: 0

#
U 2013/02/25 15:11:43.117432 192.168.41.104:5060 -> 192.168.41.104:5090
REFER sip:192.168.41.104;lr SIP/2.0
Via: SIP/2.0/UDP 192.168.41.104;branch=z9hG4bK6fae.33cc8774.0
Via: SIP/2.0/UDP 192.168.41.104;branch=z9hG4bK6fae.23cc8774.0
Via: SIP/2.0/UDP 192.168.41.87:5060;rport=5060;branch=z9hG4bK3a71583a00014
From: "102"<sip:102 at 192.168.41.104>;tag=b9a43740
To: <sip:conf at 192.168.41.104>;tag=zpnOg.7tpstrcHMiz8qEEhVkIXFHRT8P
Call-ID: 51b1086e-3 at 192.168.41.87
CSeq: 1679626670 REFER
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
Refer-To: <sip:101 at 192.168.41.104>
Referred-By: "102"<sip:102 at 192.168.41.104>
Allow:
INVITE,ACK,BYE,CANCEL,REFER,NOTIFY,OPTIONS,PRACK,UPDATE,INFO,MESSAGE,SUBSCRIBE,SERVICE,PING,PUBLISH
Allow-Events: refer, presence
Supported: 100rel, replaces, join, histinfo
Proxy-Authorization: Digest username="102", realm="192.168.41.104",
nonce="USsy/lErMdKd2dH+Nht+6yED0eytILs8", uri="sip:conf at 192.168.41.104",
algorithm=MD5, response="32e9a52e57a21a3b3b64ce1be0306cf0"
Date: Mon, 25 Feb 2013 09:41:44 GMT
Content-Length: 0

#
U 2013/02/25 15:11:43.122951 192.168.41.104:5090 -> 192.168.41.104:5060
SIP/2.0 202 Accepted
Via: SIP/2.0/UDP
192.168.41.104;received=192.168.41.104;branch=z9hG4bK6fae.33cc8774.0
Via: SIP/2.0/UDP 192.168.41.104;branch=z9hG4bK6fae.23cc8774.0
Via: SIP/2.0/UDP 192.168.41.87:5060;rport=5060;branch=z9hG4bK3a71583a00014
Call-ID: 51b1086e-3 at 192.168.41.87
From: "102" <sip:102 at 192.168.41.104>;tag=b9a43740
To: <sip:conf at 192.168.41.104>;tag=zpnOg.7tpstrcHMiz8qEEhVkIXFHRT8P
CSeq: 1679626670 REFER
Contact: <sip:conf at 192.168.41.104>;isfocus
Allow: SUBSCRIBE, NOTIFY, PRACK, INVITE, ACK, BYE, CANCEL, UPDATE, MESSAGE,
REFER
Supported: 100rel, replaces, norefersub, gruu
Server: SylkServer-2.3.0
Content-Length:  0

#
U 2013/02/25 15:11:43.134607 192.168.41.104:5090 -> 192.168.41.104:5060
NOTIFY sip:102 at 192.168.41.87:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.41.104:5090
;rport;branch=z9hG4bKPjdVUMzpKcgZxTaLqFsCNI0Sj0s4vBOq2V
Max-Forwards: 70
From: <sip:conf at 192.168.41.104>;tag=zpnOg.7tpstrcHMiz8qEEhVkIXFHRT8P
To: "102" <sip:102 at 192.168.41.104>;tag=b9a43740
Contact: <sip:conf at 192.168.41.104>;isfocus
Call-ID: 51b1086e-3 at 192.168.41.87
CSeq: 29598 NOTIFY
Route: <sip:192.168.41.104;lr>
Event: refer
Subscription-State: active;expires=89
Allow-Events: conference, refer, presence
User-Agent: SylkServer-2.3.0
Content-Type: message/sipfrag;version=2.0
Content-Length:    20

SIP/2.0 100 Trying

#
U 2013/02/25 15:11:43.138593 192.168.41.104:5060 -> 192.168.41.104:5090
SIP/2.0 200 Notification Delivered
Via: SIP/2.0/UDP 192.168.41.104:5090
;rport=5090;branch=z9hG4bKPjdVUMzpKcgZxTaLqFsCNI0Sj0s4vBOq2V
Record-Route: <sip:192.168.41.104;lr>
From: <sip:conf at 192.168.41.104>;tag=zpnOg.7tpstrcHMiz8qEEhVkIXFHRT8P
To: "102"<sip:102 at 192.168.41.104>;tag=b9a43740
Call-ID: 51b1086e-3 at 192.168.41.87
CSeq: 29598 NOTIFY
User-Agent: mycompany/2.0
P-Access-Network-Info: IEEE-802.3
Event: refer
Date: Mon, 25 Feb 2013 09:41:44 GMT
Content-Length: 0

#
U 2013/02/25 15:11:43.146788 192.168.41.104:5090 -> 192.168.41.104:5060
NOTIFY sip:102 at 192.168.41.87:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.41.104:5090
;rport;branch=z9hG4bKPj16VQAVUP9znLeCsMElKrft9kPTkNFiXo
Max-Forwards: 70
From: <sip:conf at 192.168.41.104>;tag=zpnOg.7tpstrcHMiz8qEEhVkIXFHRT8P
To: "102" <sip:102 at 192.168.41.104>;tag=b9a43740
Contact: <sip:conf at 192.168.41.104>;isfocus
Call-ID: 51b1086e-3 at 192.168.41.87
CSeq: 29599 NOTIFY
Route: <sip:192.168.41.104;lr>
Event: refer
Subscription-State: terminated;reason=noresource
Allow-Events: conference, refer, presence
User-Agent: SylkServer-2.3.0
Content-Type: message/sipfrag;version=2.0
Content-Length:    23

SIP/2.0 403 Forbidden

#
U 2013/02/25 15:11:43.151407 192.168.41.104:5060 -> 192.168.41.104:5090
SIP/2.0 200 Notification Delivered
Via: SIP/2.0/UDP 192.168.41.104:5090
;rport=5090;branch=z9hG4bKPj16VQAVUP9znLeCsMElKrft9kPTkNFiXo
Record-Route: <sip:192.168.41.104;lr>
From: <sip:conf at 192.168.41.104>;tag=zpnOg.7tpstrcHMiz8qEEhVkIXFHRT8P
To: "102"<sip:102 at 192.168.41.104>;tag=b9a43740
Call-ID: 51b1086e-3 at 192.168.41.87
CSeq: 29599 NOTIFY
User-Agent: mycompany/2.0
P-Access-Network-Info: IEEE-802.3
Event: refer
Date: Mon, 25 Feb 2013 09:41:44 GMT
Content-Length: 0

#
U 2013/02/25 15:11:46.278932 192.168.41.104:5090 -> 192.168.41.104:5060
BYE sip:102 at 192.168.41.87:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.41.104:5090
;rport;branch=z9hG4bKPje8e3HvP6AvMgEIy39Tfag3WV8GZRyq9J
Max-Forwards: 70
From: <sip:conf at 192.168.41.104>;tag=RaWjLAp3BzwSlgZGl69rzLwoTSfDVDsX
To: "102" <sip:102 at 192.168.41.104>;tag=3405a4b6
Call-ID: e5624839-3 at 192.168.41.87
CSeq: 5485 BYE
Route: <sip:192.168.41.104;lr>
User-Agent: SylkServer-2.3.0
Content-Length:  0

#
U 2013/02/25 15:11:46.281062 192.168.41.104:5060 -> 192.168.41.104:5090
SIP/2.0 481 Call Leg/Transaction Does Not Exist
Via: SIP/2.0/UDP 192.168.41.104:5090
;rport=5090;branch=z9hG4bKPje8e3HvP6AvMgEIy39Tfag3WV8GZRyq9J
From: <sip:conf at 192.168.41.104>;tag=RaWjLAp3BzwSlgZGl69rzLwoTSfDVDsX
To: "102"<sip:102 at 192.168.41.104>;tag=3405a4b6
Call-ID: e5624839-3 at 192.168.41.87
CSeq: 5485 BYE
User-Agent: mycompany/2.0
P-Access-Network-Info: IEEE-802.3
Date: Mon, 25 Feb 2013 09:41:47 GMT
Content-Length: 0

exit
26 received, 0 dropped

On Mon, Feb 25, 2013 at 4:34 PM, Saúl Ibarra Corretgé
<saul at ag-projects.com>wrote:

>
> On Feb 25, 2013, at 11:56 AM, Ram Anji wrote:
>
> > Thank you,
> >
>
> Please send emails to the list ;-)
>
> > What about the REFER and NOTIFY, why the sylkserver sending 403 for
> NOTIFY even without initiating invite to participant.
> >
>
> I can't possibly know, without looking at a SIP trace. Were they also sent
> in-dialog? If so, it's the same reason as for why the SUBSCRIBE didn't work.
>
>
> Regards,
>
> --
> Saúl Ibarra Corretgé
> AG Projects
>
>
>
> _______________________________________________
> SIPBeyondVoIP mailing list
> SIPBeyondVoIP at lists.ag-projects.com
> http://lists.ag-projects.com/mailman/listinfo/sipbeyondvoip
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ag-projects.com/pipermail/sipbeyondvoip/attachments/20130225/59d2f577/attachment-0001.html>