[Home]

Summary:ASTERISK-28330: call gets disconnected every 30 sec after answer
Reporter:vivek Kumar shah (vivek.shah@ncell.axiata.com)Labels:pjsip
Date Opened:2019-03-07 21:42:46.000-0600Date Closed:2019-03-08 04:25:28.000-0600
Priority:MinorRegression?
Status:Closed/CompleteComponents:pjproject/pjsip
Versions:16.2.1 Frequency of
Occurrence
Related
Issues:
Environment:centos 7Attachments:
Description:Hi ,

I am using asterisk 16.2 and PJsip driver . When the phone is answered , the call get disconnected with bye every 30 secs. Please help.

I am getting multiple  following message before bye.


<--- Transmitting SIP response (793 bytes) to UDP:10.9.10.114:35032 --->
SIP/2.0 200 OK
Via: SIP/2.0/UDP 10.9.10.114:35032;rport=35032;received=10.9.10.114;branch=z9hG4bK-524287-1---76e95a686b04e46c
Call-ID: 2LJiP5hVJcRW4yhOgD3V-Q..
From: <sip:phone1@10.40.111.48>;tag=9d7c0517
To: <sip:251@10.40.111.48>;tag=9b1afd32-127c-4924-bb3b-9715d7a807b5
CSeq: 2 INVITE
Server: Asterisk PBX 16.2.0
Allow: OPTIONS, REGISTER, SUBSCRIBE, NOTIFY, PUBLISH, INVITE, ACK, BYE, CANCEL, UPDATE, PRACK, MESSAGE, REFER
Contact: <sip:10.33.111.48:5060>
Supported: 100rel, replaces, norefersub
Content-Type: application/sdp
Content-Length:   228

v=0
o=- 1139927487 2 IN IP4 10.40.111.48
s=Asterisk
c=IN IP4 10.40.111.48
t=0 0
m=audio 12354 RTP/AVP 8 101
a=rtpmap:8 PCMA/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16
a=ptime:20
a=maxptime:150
a=sendrecv
Comments:By: Asterisk Team (asteriskteam) 2019-03-07 21:42:47.311-0600

Thanks for creating a report! The issue has entered the triage process. That means the issue will wait in this status until a Bug Marshal has an opportunity to review the issue. Once the issue has been reviewed you will receive comments regarding the next steps towards resolution.

A good first step is for you to review the [Asterisk Issue Guidelines|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines] if you haven't already. The guidelines detail what is expected from an Asterisk issue report.

Then, if you are submitting a patch, please review the [Patch Contribution Process|https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process].

Please note that once your issue enters an open state it has been accepted. As Asterisk is an open source project there is no guarantee or timeframe on when your issue will be looked into. If you need expedient resolution you will need to find and pay a suitable developer. Asking for an update on your issue will not yield any progress on it and will not result in a response. All updates are posted to the issue when they occur.
By: Asterisk Team (asteriskteam) 2019-03-07 21:42:48.977-0600

We appreciate the difficulties you are facing, however information request type issues would be better served in a different forum.

The Asterisk community provides support over IRC, mailing lists, and forums as described at http://asterisk.org/community. The Asterisk issue tracker is used specifically to track issues concerning bugs and documentation errors.

If this issue is actually a bug please use the Bug issue type instead.

Please see the Asterisk Issue Guidelines [1] for instruction on the intended use of the Asterisk issue tracker.

Thanks!

[1] https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines
By: Asterisk Team (asteriskteam) 2019-03-07 22:00:21.367-0600

This issue has been reopened as a result of your commenting on it as the reporter. It will be triaged once again as applicable.