[asterisk-users] Number of groups?
Hi, I have an application with many outgoing analog ringdown trunks, 64 and was wondering is it better to make these all part of a single group (zapata.conf, group=), or give each one a different group, as they each go to a different place. If I give them each their own group so as to be able to refer to them as g0, g1, etc is there an upper limit on the number of groups? Thanks! --- Andrew___ --Bandwidth and Colocation provided by Easynews.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
RE: [asterisk-users] Help: CallerID Name not being sent on outboundPRI trunk
On 2/28/07, Webster, Andrew [EMAIL PROTECTED] wrote: Outbound calls on my Telus PRI aren't taking the Name portion of the callerID. I've looked at the logs, and it is being set (see below), but the PRI debug output doesn't show the name being sent anywhere. As a result, received calls always display from Unknown (or just the number). Is there some config that I've missed somewhere? I'm running NI-1 (Telus says NI-2 doesn't support the name feature, so they've changed my link type). Version: Asterisk 1.2.14 svn rev 48468 Interesting, just finished a long day with a client that switched from 20+ POTS to a T1 using NI2 and CallerID Name (on inbound). So I guess NI2 does support CallerID Name. NI1/NI2 both support callerID name inbound. My issue is with CallerID outbound. There doesn't seem to be a consensus on the subject. Some people are saying outbound PRI name CallerID just doesn't exist on either NI1 or NI2, but the Telco thinks it can be done, but only on NI1 !?! I've seen dumps where the IE facility code shows the name (inbound), but would like to see an outbound one, if such a beast exists. -- Andrew Asterisk Log: Executing Set(SIP/304-091aafb8, CALLERID(all)=Andrewnn) in new stack (I've replaced the digits with n). PRI debug shows: Protocol Discriminator: Q.931 (8) len=42 Call Ref: len= 2 (reference 4/0x4) (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) Ext: 1 User information layer 1: u-Law (34) [18 03 a9 83 81] Channel ID (len= 5) [ Ext: 1 IntID: Implicit, PRI Spare: 0, Exclusive Dchan: 0 ChanSel: Reserved Ext: 1 Coding: 0 Number Specified Channel Type: 3 Ext: 1 Channel: 1 ] [6c 0c 21 80 nn nn nn nn nn nn nn nn nn nn] Calling Number (len=14) [ Ext: 0 TON: National Number (2) NPI: ISDN/Telephony Numbering Plan (E.164/E.163) (1) Presentation: Presentation permitted, user number not screened (0) 'nn' ] From zapata.conf: callerid=asreceived ;Sangoma A101 port 1 [slot:12 bus:0 span: 1] switchtype=ni1 context=from-zaptel overlapdial=yes facilityenable=yes group=0 signalling=pri_cpe channel = 1-23 Thanks! -- Andrew ___ --Bandwidth and Colocation provided by Easynews.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users ___ --Bandwidth and Colocation provided by Easynews.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users ___ --Bandwidth and Colocation provided by Easynews.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
RE: [asterisk-users] No Caller ID Name PRI NI2
What do you mean by outbound CallerID Name? So that when calling a POTS with CallerID service from telco the Name should show up as you send it? If the answer to the above is yes, then stop trying to do that. It won't work, as the name that the POTS subscriber sees is NOT the one you send, but what the provider of that POTS line sees when the do the lookup on the name that is listed (usualy) with the number received as callerid. Ah, that clarifies things a bit. So I have to tell my telco what I want to have show up for each callerID number that I send? On 2/28/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: I there, I have some trouble to do working caller id name for outgoing calls on the PRI we just installed. Caller id name work on incoming calls only. Caller id number work on incoming and outgoing calls. The provider, Goup Telecom, said that's in what i'm sending. They said that I send the cid name in ascii code and to do it working, I need to send it in hex. So I take some traces but i'm unable to figure where is the problem. What I see In case that work: incoming call: [1c 1c 9f 8b 01 00 a1 16 02 01 01 02 01 00 80 0e 49 4e 46 4f 46 4f 52 54 49 4e 20 46 41 58] Facility (len=30, codeset=0) [ 0x9F, 0x8B, 0x01, 0x00, 0xA1, 0x16, 0x02, 0x01, 0x01, 0x02, 0x01, 0x00, 0x80, 0x0E, 'INFOFORTIN FAX' ] PROTOCOL 1F What I see in case that doesn't work: outgoing call: [28 05 b1 69 6e 66 6f] Display (len= 5) Charset: 31 [ info ] completes traces: working: [ 02 01 da d6 08 02 02 34 05 04 03 80 90 a2 18 03 a9 83 81 1c 1c 9f 8b 01 00 a1 16 02 01 01 02 01 00 80 0e 49 4e 46 4f 46 4f 52 54 49 4e 20 46 41 58 1e 02 82 83 6c 0c 21 83 38 31 39 37 38 30 31 32 37 33 70 0b a1 38 31 39 33 34 30 30 39 37 37 ] Informational frame: SAPI: 00 C/R: 1 EA: 0 TEI: 000EA: 1 N(S): 109 0: 0 N(R): 107 P: 0 76 bytes of data -- ACKing all packets from 106 to (but not including) 107 -- Since there was nothing left, stopping T200 counter -- Stopping T203 counter since we got an ACK -- Nothing left, starting T203 counter Protocol Discriminator: Q.931 (8) len=76 Call Ref: len= 2 (reference 564/0x234) (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) Ext: 1 User information layer 1: u-Law (34) [18 03 a9 83 81] Channel ID (len= 5) [ Ext: 1 IntID: Implicit PRI Spare: 0 Exclusive Dchan: 0 ChanSel: Reserved Ext: 1 Coding: 0 Number Specified Channel Type: 3 Ext: 1 Channel: 1 ] [1c 1c 9f 8b 01 00 a1 16 02 01 01 02 01 00 80 0e 49 4e 46 4f 46 4f 52 54 49 4e 20 46 41 58] Facility (len=30, codeset=0) [ 0x9F, 0x8B, 0x01, 0x00, 0xA1, 0x16, 0x02, 0x01, 0x01, 0x02, 0x01, 0x00, 0x80, 0x0E, 'INFOFORTIN FAX' ] PROTOCOL 1F 8B 0001 00 (CONTEXT SPECIFIC [11]) A1 0016 (CONTEXT SPECIFIC [1]) 02 0001 01 (INTEGER: 1) 02 0001 00 (INTEGER: 0) 80 000E 49 4E 46 4F 46 4F 52 54 49 4E 20 46 41 58 (CONTEXT SPECIFIC [0]) [1e 02 82 83] 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: Calling equipment is non-ISDN. (3) ] [6c 0c 21 83 38 31 39 37 38 30 31 32 37 33] 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) '8197801273' ] [70 0b a1 38 31 39 33 34 30 30 39 37 37] Called Number (len=13) [ Ext: 1 TON: National Number (2) NPI: ISDN/Telephony Numbering Plan (E.164/E.163) (1) '8193400977' ] -- Making new call for cr 564 -- Processing Q.931 Call Setup -- Processing IE 4 (cs0, Bearer Capability) -- Processing IE 24 (cs0, Channel Identification) -- Processing IE 28 (cs0, Facility) Q.932 Interpretation component is not handled Handle Q.932 ROSE Invoke component [ Handling operation 0 ] Handle Name display operation Received caller name 'INFOFORTIN FAX' -- Processing IE 30 (cs0, Progress Indicator) -- Processing IE 108 (cs0, Calling Party Number) -- Processing IE 112 (cs0, Called Party Number) q931.c:3294 q931_receive: call 564 on channel 1 enters state 6 (Call Present) Sending Receiver Ready (110) [ 02 01 01 dc ] Supervisory frame: SAPI: 00 C/R: 1 EA: 0 TEI: 000EA: 1 Zero: 0 S: 0 01: 1 [ RR (receive ready) ] N(R): 110 P/F: 0 0 bytes of data -- Restarting T203 counter -- Restarting T203 counter q931.c:2570 q931_call_proceeding: call 564 on channel 1 enters state 9 (Incoming Call Proceeding) [ 00 01
RE: [asterisk-users] Help: CallerID Name not being sent on outboundPRI trunk
-Original Message- From: [EMAIL PROTECTED] [mailto:asterisk-users- [EMAIL PROTECTED] On Behalf Of Trevor Peirce Sent: Wednesday, February 28, 2007 21:18 To: Asterisk Users Mailing List - Non-Commercial Discussion Subject: Re: [asterisk-users] Help: CallerID Name not being sent on outboundPRI trunk I have a TELUS PRI for a while, resold via Bell... dropped it after a few months due to broken promises and failure to deliver /any/ of the things we said we required when ordering. During this time, I learned that with a TELUS PRI you cannot send name. It's simply dropped at the switch. If you want a name to show up, you have to beg and plead for them to manually update a database of theirs. On top of this, that name will show up on *all* DIDs associated with your block, so you will have to either have no name, a generic name of sorts, or buy individual phone numbers at a higher rate and beg them each time to manually do the update. That doesn't sound promising; however my problem (as shown in the debug output in my original post) is that it appears that the Zaptel drivers aren't even attempting to SEND the name out the PRI, only the number. Is there a setting in the Zapata.conf or zaptel.conf that is necessary to tell it I want it to send the name too? Andrew If you find another way, please do share... but that is 6 months headache we had just to find out that it was impossible to send the name, despite the majority of their technicians stating otherwise. This is in BC. Maybe it's different in Alta? Webster, Andrew wrote: Outbound calls on my Telus PRI aren't taking the Name portion of the callerID. I've looked at the logs, and it is being set (see below), but the PRI debug output doesn't show the name being sent anywhere. As a result, received calls always display from Unknown (or just the number). Is there some config that I've missed somewhere? I'm running NI-1 (Telus says NI-2 doesn't support the name feature, so they've changed my link type). Version: Asterisk 1.2.14 svn rev 48468 Asterisk Log: Executing Set(SIP/304-091aafb8, CALLERID(all)=Andrewnn) in new stack (I've replaced the digits with n). PRI debug shows: Protocol Discriminator: Q.931 (8) len=42 Call Ref: len= 2 (reference 4/0x4) (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) Ext: 1 User information layer 1: u-Law (34) [18 03 a9 83 81] Channel ID (len= 5) [ Ext: 1 IntID: Implicit, PRI Spare: 0, Exclusive Dchan: 0 ChanSel: Reserved Ext: 1 Coding: 0 Number Specified Channel Type: 3 Ext: 1 Channel: 1 ] [6c 0c 21 80 nn nn nn nn nn nn nn nn nn nn] Calling Number (len=14) [ Ext: 0 TON: National Number (2) NPI: ISDN/Telephony Numbering Plan (E.164/E.163) (1) Presentation: Presentation permitted, user number not screened (0) 'nn' ] From zapata.conf: callerid=asreceived ;Sangoma A101 port 1 [slot:12 bus:0 span: 1] switchtype=ni1 context=from-zaptel overlapdial=yes facilityenable=yes group=0 signalling=pri_cpe channel = 1-23 Thanks! -- Andrew ___ --Bandwidth and Colocation provided by Easynews.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users ___ --Bandwidth and Colocation provided by Easynews.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users ___ --Bandwidth and Colocation provided by Easynews.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
[asterisk-users] Help: CallerID Name not being sent on outbound PRI trunk
Outbound calls on my Telus PRI aren't taking the Name portion of the callerID. I've looked at the logs, and it is being set (see below), but the PRI debug output doesn't show the name being sent anywhere. As a result, received calls always display from Unknown (or just the number). Is there some config that I've missed somewhere? I'm running NI-1 (Telus says NI-2 doesn't support the name feature, so they've changed my link type). Version: Asterisk 1.2.14 svn rev 48468 Asterisk Log: Executing Set(SIP/304-091aafb8, CALLERID(all)=Andrewnn) in new stack (I've replaced the digits with n). PRI debug shows: Protocol Discriminator: Q.931 (8) len=42 Call Ref: len= 2 (reference 4/0x4) (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) Ext: 1 User information layer 1: u-Law (34) [18 03 a9 83 81] Channel ID (len= 5) [ Ext: 1 IntID: Implicit, PRI Spare: 0, Exclusive Dchan: 0 ChanSel: Reserved Ext: 1 Coding: 0 Number Specified Channel Type: 3 Ext: 1 Channel: 1 ] [6c 0c 21 80 nn nn nn nn nn nn nn nn nn nn] Calling Number (len=14) [ Ext: 0 TON: National Number (2) NPI: ISDN/Telephony Numbering Plan (E.164/E.163) (1) Presentation: Presentation permitted, user number not screened (0) 'nn' ] From zapata.conf: callerid=asreceived ;Sangoma A101 port 1 [slot:12 bus:0 span: 1] switchtype=ni1 context=from-zaptel overlapdial=yes facilityenable=yes group=0 signalling=pri_cpe channel = 1-23 Thanks! -- Andrew ___ --Bandwidth and Colocation provided by Easynews.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
RE: [asterisk-users] No Caller ID Name PRI NI2
Hi, I'm having a similar problem, but the name isn't even appearing in debug output of PRI (see my other post about this). My PRI is with Telus, and they told me that NI-2 doesn't support CallerID name function, only NI-1. Andrew -Original Message- From: [EMAIL PROTECTED] [mailto:asterisk-users- [EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Wednesday, February 28, 2007 17:03 To: asterisk-users@lists.digium.com Subject: [asterisk-users] No Caller ID Name PRI NI2 I there, I have some trouble to do working caller id name for outgoing calls on the PRI we just installed. Caller id name work on incoming calls only. Caller id number work on incoming and outgoing calls. The provider, Goup Telecom, said that's in what i'm sending. They said that I send the cid name in ascii code and to do it working, I need to send it in hex. So I take some traces but i'm unable to figure where is the problem. What I see In case that work: incoming call: [1c 1c 9f 8b 01 00 a1 16 02 01 01 02 01 00 80 0e 49 4e 46 4f 46 4f 52 54 49 4e 20 46 41 58] Facility (len=30, codeset=0) [ 0x9F, 0x8B, 0x01, 0x00, 0xA1, 0x16, 0x02, 0x01, 0x01, 0x02, 0x01, 0x00, 0x80, 0x0E, 'INFOFORTIN FAX' ] PROTOCOL 1F What I see in case that doesn't work: outgoing call: [28 05 b1 69 6e 66 6f] Display (len= 5) Charset: 31 [ info ] completes traces: working: [ 02 01 da d6 08 02 02 34 05 04 03 80 90 a2 18 03 a9 83 81 1c 1c 9f 8b 01 00 a1 16 02 01 01 02 01 00 80 0e 49 4e 46 4f 46 4f 52 54 49 4e 20 46 41 58 1e 02 82 83 6c 0c 21 83 38 31 39 37 38 30 31 32 37 33 70 0b a1 38 31 39 33 34 30 30 39 37 37 ] Informational frame: SAPI: 00 C/R: 1 EA: 0 TEI: 000EA: 1 N(S): 109 0: 0 N(R): 107 P: 0 76 bytes of data -- ACKing all packets from 106 to (but not including) 107 -- Since there was nothing left, stopping T200 counter -- Stopping T203 counter since we got an ACK -- Nothing left, starting T203 counter Protocol Discriminator: Q.931 (8) len=76 Call Ref: len= 2 (reference 564/0x234) (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) Ext: 1 User information layer 1: u-Law (34) [18 03 a9 83 81] Channel ID (len= 5) [ Ext: 1 IntID: Implicit PRI Spare: 0 Exclusive Dchan: 0 ChanSel: Reserved Ext: 1 Coding: 0 Number Specified Channel Type: 3 Ext: 1 Channel: 1 ] [1c 1c 9f 8b 01 00 a1 16 02 01 01 02 01 00 80 0e 49 4e 46 4f 46 4f 52 54 49 4e 20 46 41 58] Facility (len=30, codeset=0) [ 0x9F, 0x8B, 0x01, 0x00, 0xA1, 0x16, 0x02, 0x01, 0x01, 0x02, 0x01, 0x00, 0x80, 0x0E, 'INFOFORTIN FAX' ] PROTOCOL 1F 8B 0001 00 (CONTEXT SPECIFIC [11]) A1 0016 (CONTEXT SPECIFIC [1]) 02 0001 01 (INTEGER: 1) 02 0001 00 (INTEGER: 0) 80 000E 49 4E 46 4F 46 4F 52 54 49 4E 20 46 41 58 (CONTEXT SPECIFIC [0]) [1e 02 82 83] 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: Calling equipment is non-ISDN. (3) ] [6c 0c 21 83 38 31 39 37 38 30 31 32 37 33] 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) '8197801273' ] [70 0b a1 38 31 39 33 34 30 30 39 37 37] Called Number (len=13) [ Ext: 1 TON: National Number (2) NPI: ISDN/Telephony Numbering Plan (E.164/E.163) (1) '8193400977' ] -- Making new call for cr 564 -- Processing Q.931 Call Setup -- Processing IE 4 (cs0, Bearer Capability) -- Processing IE 24 (cs0, Channel Identification) -- Processing IE 28 (cs0, Facility) Q.932 Interpretation component is not handled Handle Q.932 ROSE Invoke component [ Handling operation 0 ] Handle Name display operation Received caller name 'INFOFORTIN FAX' -- Processing IE 30 (cs0, Progress Indicator) -- Processing IE 108 (cs0, Calling Party Number) -- Processing IE 112 (cs0, Called Party Number) q931.c:3294 q931_receive: call 564 on channel 1 enters state 6 (Call Present) Sending Receiver Ready (110) [ 02 01 01 dc ] Supervisory frame: SAPI: 00 C/R: 1 EA: 0 TEI: 000EA: 1 Zero: 0 S: 0 01: 1 [ RR (receive ready) ] N(R): 110 P/F: 0 0 bytes of data -- Restarting T203 counter -- Restarting T203 counter q931.c:2570 q931_call_proceeding: call 564 on channel 1 enters state 9 (Incoming Call Proceeding) [ 00 01 d6 dc 08 02 82 34 02 18 03 a9 83 81 ] Informational frame: SAPI: 00 C/R: 0 EA: 0 TEI: 000EA: 1 N(S): 107 0: 0 N(R): 110 P: 0 10 bytes of data -- Restarting T203 counter Stopping T_203 timer Starting T_200
RE: [asterisk-users] No Caller ID Name PRI NI2
I posted to Trixbox forum, since that is what I'm running, here's the URL: http://www.trixbox.org/modules/newbb/viewtopic.php?topic_id=11168forum= 4 Andrew -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Wednesday, February 28, 2007 18:24 To: Webster, Andrew Cc: Asterisk Users Mailing List - Non-Commercial Discussion Subject: RE: [asterisk-users] No Caller ID Name PRI NI2 Hi, You're right about what Telus said, this is written in the form that I received to get one but the tech at Group Telecom just respond to me in and say that this is supposed to work with NI2 with that structure: I 1C Standard Facility Length = 21 9F Serv Discrim Networking Extensions PDU Component Begins (hex) 8B0100A10F020101... Also, in that post http://lists.digium.com/pipermail/asterisk-users/2004-December/071501.ht ml The guy seem to say that caller id name is working with NI-2 When I was in line with the tech of GT, I have also tried with 5ess and it wasn't working (sorry, no trace) Can you just past the url of your post about Telus? Thank you, LF Quoting Webster, Andrew [EMAIL PROTECTED]: Hi, I'm having a similar problem, but the name isn't even appearing in debug output of PRI (see my other post about this). My PRI is with Telus, and they told me that NI-2 doesn't support CallerID name function, only NI-1. Andrew -Original Message- From: [EMAIL PROTECTED] [mailto:asterisk-users- [EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Wednesday, February 28, 2007 17:03 To: asterisk-users@lists.digium.com Subject: [asterisk-users] No Caller ID Name PRI NI2 I there, I have some trouble to do working caller id name for outgoing calls on the PRI we just installed. Caller id name work on incoming calls only. Caller id number work on incoming and outgoing calls. The provider, Goup Telecom, said that's in what i'm sending. They said that I send the cid name in ascii code and to do it working, I need to send it in hex. So I take some traces but i'm unable to figure where is the problem. What I see In case that work: incoming call: [1c 1c 9f 8b 01 00 a1 16 02 01 01 02 01 00 80 0e 49 4e 46 4f 46 4f 52 54 49 4e 20 46 41 58] Facility (len=30, codeset=0) [ 0x9F, 0x8B, 0x01, 0x00, 0xA1, 0x16, 0x02, 0x01, 0x01, 0x02, 0x01, 0x00, 0x80, 0x0E, 'INFOFORTIN FAX' ] PROTOCOL 1F What I see in case that doesn't work: outgoing call: [28 05 b1 69 6e 66 6f] Display (len= 5) Charset: 31 [ info ] completes traces: working: [ 02 01 da d6 08 02 02 34 05 04 03 80 90 a2 18 03 a9 83 81 1c 1c 9f 8b 01 00 a1 16 02 01 01 02 01 00 80 0e 49 4e 46 4f 46 4f 52 54 49 4e 20 46 41 58 1e 02 82 83 6c 0c 21 83 38 31 39 37 38 30 31 32 37 33 70 0b a1 38 31 39 33 34 30 30 39 37 37 ] Informational frame: SAPI: 00 C/R: 1 EA: 0 TEI: 000EA: 1 N(S): 109 0: 0 N(R): 107 P: 0 76 bytes of data -- ACKing all packets from 106 to (but not including) 107 -- Since there was nothing left, stopping T200 counter -- Stopping T203 counter since we got an ACK -- Nothing left, starting T203 counter Protocol Discriminator: Q.931 (8) len=76 Call Ref: len= 2 (reference 564/0x234) (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) Ext: 1 User information layer 1: u-Law (34) [18 03 a9 83 81] Channel ID (len= 5) [ Ext: 1 IntID: Implicit PRI Spare: 0 Exclusive Dchan: 0 ChanSel: Reserved Ext: 1 Coding: 0 Number Specified Channel Type: 3 Ext: 1 Channel: 1 ] [1c 1c 9f 8b 01 00 a1 16 02 01 01 02 01 00 80 0e 49 4e 46 4f 46 4f 52 54 49 4e 20 46 41 58] Facility (len=30, codeset=0) [ 0x9F, 0x8B, 0x01, 0x00, 0xA1, 0x16, 0x02, 0x01, 0x01, 0x02, 0x01, 0x00, 0x80, 0x0E, 'INFOFORTIN FAX' ] PROTOCOL 1F 8B 0001 00 (CONTEXT SPECIFIC [11]) A1 0016 (CONTEXT SPECIFIC [1]) 02 0001 01 (INTEGER: 1) 02 0001 00 (INTEGER: 0) 80 000E 49 4E 46 4F 46 4F 52 54 49 4E 20 46 41 58 (CONTEXT SPECIFIC [0]) [1e 02 82 83] 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: Calling equipment is non-ISDN. (3) ] [6c 0c 21 83 38 31 39 37 38 30 31 32 37 33] 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) '8197801273' ] [70 0b a1 38 31 39 33 34 30 30 39 37 37] Called Number (len=13) [ Ext: 1 TON: National Number
RE: [asterisk-users] TDM2400 Hardware Echo Cancel
I have been having the same problems since installing a TDM2400 with hardware echo canceller. The best way to describe the sound is a background crackle or hiss that just can't be filtered out. Increasing the RX gain just makes the problem worse. SIP to SIP calls are flawless. An acquaintance told me the analog line level is too low, but when plugging a regular phone into the line, the signal is plenty loud enough. I am curious if anyone else had similar issues with the TDM2400 card and if they have resolved it. -- Andrew -Original Message- From: [EMAIL PROTECTED] [mailto:asterisk-users- [EMAIL PROTECTED] On Behalf Of Adam Sharples Sent: Tuesday, January 16, 2007 09:00 To: asterisk-users@lists.digium.com Subject: [asterisk-users] TDM2400 Hardware Echo Cancel Good Day List, I'm having some issues with echo cancel on my Asterisk box, and have done extensive reading and have gained some useful pointers from this list but have a couple of hopefully fairly simple questions. The Asterisk box is connected via 20 FXO ports on a TDM2400 with the Hardware echo cancel module. Echo cancel almost works, but the users hear what they describe as a 'crackle' coming back when they talk. I want to tune to echo canceller, but am unsure if any of the options provided have any effect on the hardware module. Do the settings such as echocancel and echotraining in Zapata.conf affect the hardware module? Would I be better removing the hardware module and tuning the software echo canceller? The asterisk box is currently running 1.2.13, with zaptel 1.2. Would you advise upgrading to the newer Zaptel drivers? I don't want to upgrade Asterisk itself just yet. Any help or pointers to documentation regarding the hardware echo cancel module would be greatly appreciated, Thanks, Adam Sharples ___ --Bandwidth and Colocation provided by Easynews.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users ___ --Bandwidth and Colocation provided by Easynews.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
[asterisk-users] TDM2400p and HW echo canceller
Do the zaptel drivers need to be told NOT to use the software echo canceller when using a TDM2400p card with hardware echo canceller, or does the driver figure this out by itself? Thanks, Andrew ___ --Bandwidth and Colocation provided by Easynews.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
RE: [asterisk-users] Re: Choppy sound in voicemail using Asterisk1.2.11 on CENTOS4 guest on vmware server
-Original Message- From: [EMAIL PROTECTED] [mailto:asterisk-users- [EMAIL PROTECTED] On Behalf Of Martin Joseph Sent: Saturday, November 11, 2006 15:01 To: asterisk-users@lists.digium.com Subject: [asterisk-users] Re: Choppy sound in voicemail using Asterisk1.2.11 on CENTOS4 guest on vmware server On 2006-11-10 09:10:30 -0800, Mario François Jauvin [EMAIL PROTECTED] said: This is a multi-part message in MIME format. I have had no success in getting the voicemail working on Asterisk 1.2.11 on CENTOS4(2.6 kernel) guest on vmware server 1.0.1. I tried with or without ztdummy device, renice -20 on asterisk process and even real-time priority on the host Windows XP box for the vmware process. I am running on an AMD Athlon 64 X2 4600+. The behaviour is when the voicemail answer, the voice sound ok but when asterisk starts saying the digits from the extension, the sound starts becoming very choppy. The voice after the digits is still choppy. Does anyone have a suggestion? The codec that asterisk is using with the softphone I am using is the GSM codec. If it sounds like the trouble starts when digits are being spoken, perhaps it's related to your disk controller? Is there a zap channel involved in this setup (ie how is the phone connected)? Don't know much about the whole vmware thing, but it sounds like an interrupt issue perhaps? Marty You don't mention what version of kernel you are using. There are known issues with certain versions of Kernel when running inside VMWARE. 2.6.9-34 branch works well, 2.6.9-42 does not! Andrew ___ --Bandwidth and Colocation provided by Easynews.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
