Conference drops after 52 seconds
Agi Subagio
participants.
When I invite user1, the user1 press button 1, wait for the tone and
then press the # button to joining the conference. After 52 seconds in
conference room without doing anything, the connection is drop by itself.
And the log:
15:15:55.152 2 SIPDATA-018072 out: req [172.16.4.16]:5060 -> udp[172.16.1.74]:42306 INVITE(1076 bytes) sip:a...@172.16.1.74:42306;rinstance=a48394b9014da042
15:15:55.152 2 SIPC-008244 [018072] INVITE sip:a...@172.16.1.74:42306;rinstance=a48394b9014da042 sent [172.16.4.16]:5060 -> udp[172.16.1.74]:42306
15:15:55.254 2 SIPDATA-018073 inp: rsp [0.0.0.0]:5060 <- udp[172.16.1.74]:42306 180-INVITE(506 bytes)
15:15:55.254 2 SIPDATA-018073 sent to SIPC-008244
15:15:55.254 2 SIPC-008244 [018073] 180-INVITE received
15:15:55.254 2 SIGNAL-036978 180 (provisioning) from SIPC-008244
15:16:02.396 2 SIPDATA-018074 inp: rsp [0.0.0.0]:5060 <- udp[172.16.1.74]:42306 200-INVITE(882 bytes)
15:16:02.396 2 SIPDATA-018074 sent to SIPC-008244
15:16:02.396 2 SIPC-008244 [018074] 200-INVITE received
15:16:02.396 2 SIGNAL-036978 200 received from SIPC-008244
15:16:02.400 2 PBXLEG-022794 DIALOG-000123(out) started with a...@mbs.co.id(sip:a...@172.16.1.74:42306;rinstance=a48394b9014da042), refresh=300(active)(canTransfer)
15:16:02.401 2 SIPDATA-000000 created SIPC-008246 to send downstream
15:16:02.401 2 SIPC-008246 [000000] ACK sip:a...@172.16.1.74:42306;rinstance=a48394b9014da042
15:16:02.401 2 SIPDATA-018075 out: req [172.16.4.16]:5060 -> udp[172.16.1.74]:42306 ACK(504 bytes) sip:a...@172.16.1.74:42306;rinstance=a48394b9014da042
15:16:02.401 2 SIPC-008246 [018075] ACK sip:a...@172.16.1.74:42306;rinstance=a48394b9014da042 sent [172.16.4.16]:5060 -> udp[172.16.1.74]:42306
15:16:23.205 2 SIGNAL-036980 NODE-022794: INVITE sip:a...@172.16.1.74:42306;rinstance=a48394b9014da042
15:16:23.205 2 SIGNAL-036980 INVITE sip:a...@172.16.1.74:42306;rinstance=a48394b9014da042 via sip:a...@172.16.1.74:42306;rinstance=a48394b9014da042
15:16:23.205 2 SIGNAL-036980 relaying to sip:a...@172.16.1.74:42306;rinstance=a48394b9014da042 via sip:172.16.1.74:42306;rinstance=a48394b9014da042
15:16:23.205 2 SIGNAL-036980 {1} sent to SIPC-008248: INVITE sip:a...@172.16.1.74:42306;rinstance=a48394b9014da042
15:16:23.205 2 SIPC-008248 INVITE sip:a...@172.16.1.74:42306;rinstance=a48394b9014da042
15:16:23.206 2 SIPDATA-018078 out: req [172.16.4.16]:5060 -> udp[172.16.1.74]:42306 INVITE(969 bytes) sip:a...@172.16.1.74:42306;rinstance=a48394b9014da042
15:16:23.206 2 SIPC-008248 [018078] INVITE sip:a...@172.16.1.74:42306;rinstance=a48394b9014da042 sent [172.16.4.16]:5060 -> udp[172.16.1.74]:42306
15:16:23.313 2 SIPDATA-018079 inp: rsp [0.0.0.0]:5060 <- udp[172.16.1.74]:42306 200-INVITE(882 bytes)
15:16:23.313 2 SIPDATA-018079 sent to SIPC-008248
15:16:23.314 2 SIPC-008248 [018079] 200-INVITE received
15:16:23.314 3 SIPC-008248 2 Record-Route field(s) in non-starting response, clearing
15:16:23.314 2 SIGNAL-036980 200 received from SIPC-008248
15:16:23.314 2 SIPDATA-000000 created SIPC-008250 to send downstream
15:16:23.314 2 SIPC-008250 [000000] ACK sip:a...@172.16.1.74:42306;rinstance=a48394b9014da042
15:16:23.314 2 SIPDATA-018080 out: req [172.16.4.16]:5060 -> udp[172.16.1.74]:42306 ACK(504 bytes) sip:a...@172.16.1.74:42306;rinstance=a48394b9014da042
15:16:23.314 2 SIPC-008250 [018080] ACK sip:a...@172.16.1.74:42306;rinstance=a48394b9014da042 sent [172.16.4.16]:5060 -> udp[172.16.1.74]:42306
15:16:54.397 2 SIPDATA-018083 inp: req [0.0.0.0]:5060 <- udp[172.16.1.74]:42306 BYE(606 bytes) sip:signode-227...@172.16.4.16
15:16:54.397 2 SIPDATA-018083 created SIPS-008514
15:16:54.398 2 SIPS-008514 [018083] BYE sip:signode-227...@172.16.4.16 from udp[172.16.1.74]:42306
15:16:54.398 2 SIPS-008514 created SIGNAL-036982
15:16:54.398 2 SIGNAL-036982 SIPS-008514: BYE sip:signode-227...@172.16.4.16
15:16:54.398 2 SIGNAL-036982 BYE sip:signode-227...@172.16.4.16 via sip:signode-227...@172.16.4.16
15:16:54.398 2 SIGNAL-036982 {1} sent to NODE-022794: BYE sip:signode-227...@172.16.4.16
15:16:54.407 2 SIPDATA-018084 out: rsp [0.0.0.0]:5060 -> udp[172.16.1.74]:42306 200-BYE(363 bytes)
15:16:54.408 2 SIPS-008514 [018084] 200-BYE(final) sent to udp[172.16.1.74]:42306
I'm using CGP 5.2.4 on Linux. Should I change any setting to fix this problem?
#############################################################
This message is sent to you because you are subscribed to
the mailing list <CGat...@mail.stalker.com>.
To unsubscribe, E-mail to: <CGateP...@mail.stalker.com>
To switch to the DIGEST mode, E-mail to <CGatePr...@mail.stalker.com>
To switch to the INDEX mode, E-mail to <CGatePr...@mail.stalker.com>
Send administrative queries to <CGatePro...@mail.stalker.com>
Technical Support
Agi Subagio wrote:
> I set a conference from postmaster account and invite two or more
> participants.
>
> When I invite user1, the user1 press button 1, wait for the tone and
> then press the # button to joining the conference. After 52 seconds in
> conference room without doing anything, the connection is drop by itself.
1. It's highly recommended to upgrade the server to the latest version -
5.2.17. 5.2.4 us too old and may have some bugs.
2. Per the logs at least on of the dialogs was terminated by the client
- it sent the BYE request.
3. To debug this problem you need to collect logs for Real-Time -> Nodes
set to Low level and Real-Time -> SIP -> Sending -> Transport set to All
Info.
> And the log:
>
[]
>
> I'm using CGP 5.2.4 on Linux. Should I change any setting to fix this
> problem?
--
Best regards,
Dmitry Akindinov
=======================================================================
When answering to letters sent to you by the tech.support staff, make
sure the original message you have received is included into your reply.