Summary: | ASTERISK-01645: busy tone | ||
Reporter: | wiking (wiking) | Labels: | |
Date Opened: | 2004-05-17 21:03:55 | Date Closed: | 2011-06-07 14:10:33 |
Priority: | Minor | Regression? | No |
Status: | Closed/Complete | Components: | Core/General |
Versions: | Frequency of Occurrence | ||
Related Issues: | |||
Environment: | Attachments: | ( 0) mgcp.conf | |
Description: | in development release i'm getting the following error when i lift up the reciever of my hardphone: chan_mgcp.c:2227 handle_response: Terminating on result 502 from aaln/1@gw52302432-1 and it gives me busy tone. | ||
Comments: | By: Mark Spencer (markster) 2004-05-18 14:19:24 Care to enlighten us with what MGCP device you are using? 502 says "The transaction could not be executed because the endpoint does not have sufficient resources"... By: Mark Spencer (markster) 2004-05-19 18:05:41 You've got to be more responsive if you want assistance with your bug. Please respond by tomorrow if you still care about this bug. By: wiking (wiking) 2004-05-20 04:32:59 sorry for the long delay... I'm trying to use a kinda noname phone (IPH-90). i've opened the phone and it's says that it is a broadmedia g-phone ipx 3200. i'll report the mgcp debug ASAP By: wiking (wiking) 2004-05-20 08:56:13 here's the output of CLI when i turn in 'mgcp debug'. first when i connect my hardphone: MGCP Debugging Enabled MGCP read: RSIP 8094 aaln/1@gw52302432 MGCP 1.0 NCS 1.0 RM: restart from 10.0.0.20:2427MGCP read: RSIP 8094 aaln/1@gw52302432 MGCP 1.0 NCS 1.0 RM: restart from 10.0.0.20:2427Verb: 'RSIP', Identifier: '8094', Endpoint: 'aaln/1@gw52302432', Version: 'MGCP 1.0' 2 headers, 0 lines Handling request 'RSIP' on aaln/1@gw52302432 Transmitting: 200 8094 OK to 10.0.0.20:2427 -- MGCP Asked to indicate tone: on aaln/1@gw52302432-1 in cxmode: inactive Posting Request: RQNT 2 aaln/1@gw52302432 MGCP 1.0 X: 6b8b4567 R: L/hd(N) to 10.0.0.20:2427 Posting Request: AUEP 3 aaln/1@gw52302432 MGCP 1.0 F: A to 10.0.0.20:2427 MGCP read: 200 3 Ok A: a:G723, p:30-60, e:on, s:off, gc:0, v:L;S, m:sendonly;recvonly;sendrecv;inactive from 10.0.0.20:2427MGCP read: 200 3 Ok A: a:G723, p:30-60, e:on, s:off, gc:0, v:L;S, m:sendonly;recvonly;sendrecv;inactive from 10.0.0.20:2427Verb: '200', Identifier: '3', Endpoint: 'Ok', Version: '(null)' 2 headers, 0 lines Retransmitting #1 transaction 2 on [gw52302432] Retransmitting #2 transaction 2 on [gw52302432] Retransmitting #3 transaction 2 on [gw52302432] Retransmitting #4 transaction 2 on [gw52302432] Retransmitting ASTERISK-1 transaction 2 on [gw52302432] May 18 05:07:32 WARNING[5126]: chan_mgcp.c:571 retrans_pkt: Maximum retries exceeded for transaction 2 on [gw52302432] May 18 05:07:32 NOTICE[5126]: chan_mgcp.c:2218 handle_response: Transaction 2 timed out and after this when i pick up the reciever: MGCP read: NTFY 8095 aaln/1@gw52302432 MGCP 1.0 NCS 1.0 X: 0 O: hd from 10.0.0.20:2427MGCP read: NTFY 8095 aaln/1@gw52302432 MGCP 1.0 NCS 1.0 X: 0 O: hd from 10.0.0.20:2427Verb: 'NTFY', Identifier: '8095', Endpoint: 'aaln/1@gw52302432', Version: 'MGCP 1.0' 3 headers, 0 lines Handling request 'NTFY' on aaln/1@gw52302432 Transmitting: 200 8095 OK to 10.0.0.20:2427 -- Creating connection for aaln/1@gw52302432-1 in cxmode: sendrecv callid: 539f02a5643c9869 We're at 10.0.0.25 port 16236 Answering with capability 4 Posting Request: CRCX 4 aaln/1@gw52302432 MGCP 1.0 C: 539f02a5643c9869 L: p:20, a:PCMU M: sendrecv X: 643c9869 v=0 o=root 18791 18791 IN IP4 10.0.0.25 s=session c=IN IP4 10.0.0.25 t=0 0 m=audio 16236 RTP/AVP 0 a=rtpmap:0 PCMU/8000 to 10.0.0.20:2427 -- MGCP Asked to indicate tone: L/dl on aaln/1@gw52302432-1 in cxmode: sendrecv Posting Request: RQNT 5 aaln/1@gw52302432 MGCP 1.0 X: 6b8b4567 R: L/hu(N), L/hf(N), D/[0-9#*](N) S: L/dl to 10.0.0.20:2427 MGCP read: 200 5 Ok from 10.0.0.20:2427MGCP read: 200 5 Ok from 10.0.0.20:2427Verb: '200', Identifier: '5', Endpoint: 'Ok', Version: '(null)' 1 headers, 0 lines Retransmitting #1 transaction 4 on [gw52302432] MGCP read: 502 4 Fail from 10.0.0.20:2427MGCP read: 502 4 Fail from 10.0.0.20:2427Verb: '502', Identifier: '4', Endpoint: 'Fail', Version: '(null)' 1 headers, 0 lines May 18 05:09:50 NOTICE[5126]: chan_mgcp.c:2227 handle_response: Terminating on result 502 from aaln/1@gw52302432-1 -- MGCP mgcp_hangup(MGCP/aaln/1@gw52302432-1) on aaln/1@gw52302432 -- MGCP Asked to indicate tone: L/ro on aaln/1@gw52302432-1 in cxmode: sendrecv Posting Request: RQNT 6 aaln/1@gw52302432 MGCP 1.0 X: 6b8b4567 R: L/hu(N), L/hf(N), D/[0-9#*](N) S: L/ro to 10.0.0.20:2427 MGCP read: 200 6 Ok from 10.0.0.20:2427MGCP read: 200 6 Ok from 10.0.0.20:2427Verb: '200', Identifier: '6', Endpoint: 'Ok', Version: '(null)' 1 headers, 0 lines and the phone gives busy tone By: Mark Spencer (markster) 2004-05-20 10:11:42 This appears to be related to a configuration issue. I notice the endpoint suggests it only speaks G.723 with 30 or 60ms chunks, and Asterisk is configured for PCMU. By: wiking (wiking) 2004-05-20 11:25:48 hmm, well as from the device's manual, the phone is: - Compliant to MGCP 1.0 and NCS 1.0 - Voice compression: Complies with G.723.1 i've just added my mgcp.conf. sorry for being such a lame, but could you give me a "sign" how could i fix this problem - so the phone finally gets working? By: Mark Spencer (markster) 2004-05-22 00:03:49 You need to configure the phone to use G.711 not G.723.1 and it should probably work. By: wiking (wiking) 2004-05-22 05:38:54 i've read through the phone's manual (http://wiking.jol.hu/text/Iph-90.pdf) and i couldn't find a way of changing it's codec. i've tried to find a way with opening the phone, but no luck... is this means that there's no way of using this phone with asterisk? By: Mark Spencer (markster) 2004-05-22 18:11:41 Although I've never seen a device before with this limitation, I've also reviewed the document and clearly -- and for what reason, i have no idea -- only supports G.723.1 and does not allow you to use it in G.711 mode, meaning you would only be able to have asterisk behave as a switch and could not provide any real features, since transcoding G.723.1 requires licensing patents and is *extremely* expensive even in comparision with G.729. |