[Home]

Summary:ASTERISK-26508: MGCP call flow when going off-hook
Reporter:Andrzej Augustynowicz (andrzeja)Labels:
Date Opened:2016-10-26 16:32:21Date Closed:2020-01-14 11:21:05.000-0600
Priority:MajorRegression?No
Status:Closed/CompleteComponents:Channels/chan_mgcp
Versions:13.11.2 Frequency of
Occurrence
Related
Issues:
Environment:Debian x64 Jessie, Asterisk 13.11.2, 14.0.2,1.8.32.3Attachments:
Description:I have problem with off-hook sequence

[general]
port = 2427
bindaddr = 0.0.0.0
disallow=all
allow=alaw
allow=ulaw


[10.16.128.122]
host=10.16.128.122
dtmfmode=rfc2833
ncs = yes
pktcgatealloc = yes
hangupongateremove = yes
context=XXX
callerid=123456789
line=>aaln/1

--------------------------------------------------------
Start first hook-off - dialtone OK
NTFY 38707614 aaln/1@10.16.128.122 MGCP 1.0 NCS 1.0
X: 28024E6E
O: hd
200 38707614 OK
CRCX 120 aaln/1@[10.16.128.122] MGCP 1.0 NCS 1.0
C: 36db1987362d2ae5
L: p:20, s:off, e:on, a:PCMU
M: inactive
X: 362d2ae5
RQNT 121 aaln/1@[10.16.128.122] MGCP 1.0 NCS 1.0
X: 28024e6e
R: L/hu(N),L/hf(N),L/[0-9#*](N)
S: L/dl
200 120 OK
I: 1F26

v=0
o=- 120 7974 IN IP4 10.16.128.122
s=-
c=IN IP4 10.16.128.122
b=AS:82
t=0 0
m=audio 53456 RTP/AVP 0
a=X-pc-secret:base64:tnPwjAaD25Sz3rYOqDL48NPq2pFdvWVnhH5ovAHVwWwdyHULrzeirLU6yF9mvQ== wdamHeQWysDdsTgy6XSYRoWNGobvIk0s896FiaUIE8PT/uT+4gSx2be8nXaszw==
a=X-pc-csuites-rtp:62/51 64/51 60/51 60/50
a=X-pc-csuites-rtcp:81/71 81/70 80/70
a=X-pc-nrekey:0
a=mptime:20
a=ptime:20
a=sqn: 0
a=cdsc: 1 image udptl t38
000 120 OK
200 121 OK
NTFY 38707615 aaln/1@10.16.128.122 MGCP 1.0 NCS 1.0
X: 28024E6E
O: hu
200 38707615 OK

When on-hook DLCX is not needed?
--------------------------------------------------------------------------------
Start next hook-off = stdder-dialtone (chan_mgcp.c: Off hook, but already have owner on aaln/1@10.16.128.122):

NTFY 38707616 aaln/1@10.16.128.122 MGCP 1.0 NCS 1.0
X: 28024E6E
O: hd
200 38707616 OK
MDCX 122 aaln/1@[10.16.128.122] MGCP 1.0 NCS 1.0
C: 36db1987362d2ae5
L: , a:PCMU, dq-gi:980
M: sendrecv
X: 362d2ae5
I: 1F26
R: L/hu(N),L/hf(N),L/[0-9#*](N)

v=0
o=root 23725 23725 IN IP4 192.168.255.50
s=session
c=IN IP4 192.168.255.50
t=0 0
m=audio 11478 RTP/AVP 0
a=rtpmap:0 PCMU/8000
RQNT 123 aaln/1@[10.16.128.122] MGCP 1.0 NCS 1.0
X: 28024e6e
R: L/hu(N),L/hf(N),L/[0-9#*](N)
100 122

v=0
o=- 120 7975 IN IP4 10.16.128.122
s=-
c=IN IP4 10.16.128.122
b=AS:80
t=0 0
m=audio 53456 RTP/AVP 0
a=X-pc-csuites-rtp:60/50
a=X-pc-csuites-rtcp:80/70
a=X-pc-nrekey:0
a=mptime:20
a=ptime:20
a=sqn: 0
a=cdsc: 1 image udptl t38
200 122 OK
K:
DQ-RI: 2F58

v=0
o=- 120 7975 IN IP4 10.16.128.122
s=-
c=IN IP4 10.16.128.122
b=AS:80
t=0 0
m=audio 53456 RTP/AVP 0
a=X-pc-csuites-rtp:60/50
a=X-pc-csuites-rtcp:80/70
a=X-pc-nrekey:0
a=mptime:20
a=ptime:20
a=sqn: 0
a=cdsc: 1 image udptl t38
000 122 OK
DLCX 125 aaln/1@[10.16.128.122] MGCP 1.0 NCS 1.0
C: 36db1987362d2ae5
X: 362d2ae5
I: 1F26
250 125 Connection was deleted
P: PS=11, OS=1760, PR=0, OR=0, PL=0, JI=0, LA=0, PC/RPS=0, PC/ROS=0, PC/RPL=0, PC/RJI=0
RQNT 123 aaln/1@[10.16.128.122] MGCP 1.0 NCS 1.0
X: 28024e6e
R: L/hu(N),L/hf(N),L/[0-9#*](N)
200 123 OK
RQNT 124 aaln/1@[10.16.128.122] MGCP 1.0 NCS 1.0
X: 28024e6e
R: L/hu(N),L/hf(N),L/[0-9#*](N)
S: L/cg
522 124 No such event or signal
RQNT 126 aaln/1@[10.16.128.122] MGCP 1.0 NCS 1.0
X: 28024e6e
R: L/hu(N),L/hf(N)
S: L/ro
200 126 OK
NTFY 38707617 aaln/1@10.16.128.122 MGCP 1.0 NCS 1.0
X: 28024E6E
O: hu
200 38707617 OK
DLCX 127 aaln/1@[10.16.128.122] MGCP 1.0 NCS 1.0
X: 362d2ae5
RQNT 128 aaln/1@[10.16.128.122] MGCP 1.0 NCS 1.0
X: 28024e6e
R: L/hd(N)
S: L/vmwi(-)
250 127 Connection was deleted
200 128 OK

After that (DLCX?) repeats sequence OK / bad
Comments:By: Asterisk Team (asteriskteam) 2016-10-26 16:32:22.341-0500

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].
By: Asterisk Team (asteriskteam) 2016-10-26 16:32:22.844-0500

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