On 4/6/11 3:02 PM, Bryant Zimmerman wrote:
Thanks for your response. I have added the patch for 18818 per Michel Verbrask's
recomendation. It appers that it has made quite a difference. I don't have an
PRI
connections as all of our PRI's are connected via SIP gateways. I did run into
serveral instances wher I had to kill -9 the process as well but post patch I
have
been in good shape know on wood. I hope there will be a new release that will
address the stability issues very soon if they release 1.8.4 without cleaning
this
up I won't move unitl it is addressed.
looking back at the messages file for the past 2 days. it
just hanged on totally different events none of which related
to Local channels.
as far as the PRI not hearing early media issue. here's the
excerpt from the messages file after "pri debug on" command:
*********************
-- Executing [18008291011@out_going_x:1] Dial("SIP/4988-6-00000b45",
"DAHDI/r1/18008291011,,f") in new stack
-- Making new call for cref 32974
-- Requested transfer capability: 0x00 - SPEECH
> DL-DATA request
> Protocol Discriminator: Q.931 (8) len=51
> TEI=0 Call Ref: len= 2 (reference 206/0xCE) (Sent from originator)
> Message Type: SETUP (5)
TEI=0 Transmitting N(S)=87, window is open V(A)=87 K=7
> Protocol Discriminator: Q.931 (8) len=51
> TEI=0 Call Ref: len= 2 (reference 206/0xCE) (Sent from originator)
> Message Type: SETUP (5)
> [04 03 80 90 a2]
> Bearer Capability (len= 5) [ Ext: 1 Q.931 Std: 0 Info transfer capability:
Speech (0)
> Ext: 1 Trans mode/rate: 64kbps, circuit-mode
(16)
> User information layer 1: u-Law (34)
> [18 03 a1 83 8a]
> Channel ID (len= 5) [ Ext: 1 IntID: Implicit Other(PRI) Spare: 0 Preferred
Dchan: 0
> ChanSel: As indicated in following octets
> Ext: 1 Coding: 0 Number Specified Channel Type: 3
> Ext: 1 Channel: 10 Type: CPE]
> [28 06 b1 45 64 77 69 6e]
> Display (len= 6) Charset: 31 [ Edwin ]
> [6c 0c 21 83 34 31 35 34 33 39 34 39 38 38]
> Calling Number (len=14) [ Ext: 0 TON: National Number (2) NPI: ISDN/Telephony
Numbering Plan (E.164/E.163) (1)
> Presentation: Presentation allowed of network
provided number (3) '4154394988' ]
> [70 0c 80 31 38 30 30 38 32 39 31 30 31 31]
> Called Number (len=14) [ Ext: 1 TON: Unknown Number Type (0) NPI: Unknown
Number Plan (0) '18008291011' ]
q931.c:5039 q931_setup: Call 32974 enters state 1 (Call Initiated). Hold
state: Idle
-- Called r1/18008291011
< Protocol Discriminator: Q.931 (8) len=13
< TEI=0 Call Ref: len= 2 (reference 206/0xCE) (Sent to originator)
< Message Type: STATUS (125)
< [08 03 80 ab 28]
< Cause (len= 5) [ Ext: 1 Coding: CCITT (ITU) standard (0) Spare: 0 Location:
User (0)
< Ext: 1 Cause: Access information discarded (43), class =
Network Congestion (resource unavailable) (2) ]
< Cause data 1: 28 (40)
< [14 01 01]
< Call State (len= 3) [ Ext: 0 Coding: CCITT (ITU) standard (0) Call state: Call
Initiated (1)
Received message for call 0x8fd2298 on 0x90d9cf0 TEI/SAPI 0/0, call->pri is
0x90d9cf0 TEI/SAPI 0/0
-- Processing IE 8 (cs0, Cause)
-- Processing IE 20 (cs0, Call State)
< Protocol Discriminator: Q.931 (8) len=10
< TEI=0 Call Ref: len= 2 (reference 206/0xCE) (Sent to originator)
< Message Type: CALL PROCEEDING (2)
< [18 03 a9 83 8a]
< Channel ID (len= 5) [ Ext: 1 IntID: Implicit Other(PRI) Spare: 0 Exclusive
Dchan: 0
< ChanSel: As indicated in following octets
< Ext: 1 Coding: 0 Number Specified Channel Type: 3
< Ext: 1 Channel: 10 Type: CPE]
Received message for call 0x8fd2298 on 0x90d9cf0 TEI/SAPI 0/0, call->pri is
0x90d9cf0 TEI/SAPI 0/0
-- Processing IE 24 (cs0, Channel Identification)
q931.c:7104 post_handle_q931_message: Call 32974 enters state 3 (Outgoing Call
Proceeding). Hold state: Idle
-- DAHDI/34-1 is proceeding passing it to SIP/4988-6-00000b45
< Protocol Discriminator: Q.931 (8) len=13
< TEI=0 Call Ref: len= 2 (reference 206/0xCE) (Sent to originator)
< Message Type: PROGRESS (3)
< [08 02 82 ff]
< Cause (len= 4) [ Ext: 1 Coding: CCITT (ITU) standard (0) Spare: 0 Location:
Public network serving the local user (2)
< Ext: 1 Cause: Interworking, unspecified (127), class =
Interworking (7) ]
< [1e 02 82 81]
< Progress Indicator (len= 4) [ Ext: 1 Coding: CCITT (ITU) standard (0) 0: 0
Location: Public network serving the local user (2)
< Ext: 1 Progress Description: Call is not
end-to-end ISDN; further call progress information may be available inband. (1) ]
Received message for call 0x8fd2298 on 0x90d9cf0 TEI/SAPI 0/0, call->pri is
0x90d9cf0 TEI/SAPI 0/0
-- Processing IE 8 (cs0, Cause)
-- Processing IE 30 (cs0, Progress Indicator)
-- PROGRESS with cause code 127 received
-- DAHDI/34-1 is making progress passing it to SIP/4988-6-00000b45
***********************************
i used the same SIP station to dial the same 800 number
on both versions (1.8.3.2 & 1.6.2.17). the output are
pretty much identical except on 1.8.3.2, after the
"PROGRESS with cause code 127..." message. i would hear
nothing until the other side timed out & hang up, whereas on
1.6.2.17. i got the "DAHDI/... is making progress passing it to SIP..."
message and can hear the early media from the other side.
For Now 1.8.3..2 is very bad.
agreed...
--
Edwin Lam <edwin....@officegeneral.com>
Systems Engineer, OfficeWyze, Inc.
Ph: +1 415 439 4988 Fax: +1 415 283 3370
http://pgpkeys.mit.edu:11371/pks/lookup?op=get&search=0xD6506D20
--
_____________________________________________________________________
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
New to Asterisk? Join us for a live introductory webinar every Thurs:
http://www.asterisk.org/hello
asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users
