search for: t303

...quot;pri show span 1" from me and came back with this: ----quote--- Please check your timers below. How did you determine your settings? * Timer and counter settings: N200: 3 N202: 3 K: 7 T200: 1000 T201: 1000 T202: 2000 T203: 10000 T303: 4000 T305: 30000 T308: 4000 T309: 6000 Our switch: Telcordia National ISDN 2: Range 10 - 90 seconds, default 90 seconds. * T312: 6000 T313: 4000 T316: -1 Our switch: Telcordia National ISDN 2: Range 10 - 120 seconds, default 30 seconds....

...> pri show span 1 Primary D-channel: 3 Status: In Alarm, Up, Active Switchtype: EuroISDN Type: BRI Network PTMP Remote type: Unknown node type Overlap Dial: 0 Logical Channel Mapping: 0 Timer and counter settings: N200: 3 N202: 3 K: 1 T200: 1000 T201: 1000 T202: 10000 T203: 10000 T303: 4000 T305: 30000 T308: 4000 T309: 6000 T312: 6000 T313: 4000 T316: -1 N316: 2 T-HOLD: 4000 T-RETRIEVE: 4000 T-RESPONSE: 4000 T-STATUS: 4000 T-ACTIVATE: 10000 T-DEACTIVATE: 4000 T-INTERROGATE: 4000 T-RETENTION: 30000 T-CCBS1: 4000 T-CCBS2: 2700000 T-CCBS3: 20000...

Hello, I am having odd issues with a new PRI based installation. Outbound calls work for all numbers except those that terminate at Sprint! The telco is new to PRI (this is in the Caribbean) and say that Sprint is rejecting the calls, and asked for our PRI settings so they can work with their switch manufacturer. We are using the bare minimum default settings, but I can imagine that a

...number = none ISDN virtual connect = disabled ISDN Layer 2 is DOWN ISDN Values ISDN Layer 2 values k = 7 N200 = 3 N201 = 260 T200 = 1 seconds T203 = 10 seconds ISDN Layer 3 values T301 = 180 seconds T303 = 4 seconds T304 = 20 seconds T305 = 30 seconds T306 = 30 seconds T308 = 4 seconds T310 = 10 seconds T313 = 10 seconds T316 = 120 seconds T322 = 4 seconds T309 = 90 seconds N303 = 1 -------------...

...pan 1/0: Provisioned, Down, Active localhost*CLI> pri show span 1 Primary D-channel: 16 Status: Provisioned, Down, Active Switchtype: EuroISDN Type: CPE Overlap Dial: 0 Logical Channel Mapping: 0 Timer and counter settings: N200: 3 N202: 3 K: 7 T200: 1000 T202: 10000 T203: 10000 T303: 4000 T305: 30000 T308: 4000 T309: 6000 T313: 4000 T-HOLD: 4000 T-RETRIEVE: 4000 T-RESPONSE: 4000 Overlap Recv: No 3. localhost*CLI> *pri set debug on span 1* Enabled debugging on span 1 TEI=0 MDL-ERROR (G): T200 expired N200 times sending SABME in state 5(Awaiting establishment...

Is anybody else using the following combination: * a TE410P card (wct4xxp driver) * a BT ISDN connection * DAHDI 2.3.0.1 * Asterisk 1.6.2.9 I'm trying to configure a new box to replace a legacy system (same hardware; some old version of Asterisk with Zaptel; works lovely but hopelessly out-of-date) and not having much joy. Specifically, I couldn't get it to see a D-channel on

...he same PRI card? Would somebody help? asterisk*CLI> pri show span 7 Primary D-channel: 202 Status: Provisioned, Up, Active Switchtype: EuroISDN Type: CPE Overlap Dial: 0 Logical Channel Mapping: 0 Timer and counter settings: N200: 3 N202: 3 K: 7 T200: 1000 T202: 10000 T203: 10000 T303: 4000 T305: 30000 T308: 4000 T309: 6000 T313: 4000 T-HOLD: 4000 T-RETRIEVE: 4000 T-RESPONSE: 4000 Overlap Recv: No and [Mar 18 17:04:05] VERBOSE[19844] chan_dahdi.c: TEI=0 MDL-ERROR (I): T200 expired N200 times sending RR/RNR in state 8(Timer recovery) [Mar 18 17:04:05] VERBOSE[198...