search for: unscreen

Displaying 12 results from an estimated 12 matches for "unscreen".

Did you mean: onscreen
2005 May 21
2
Set CallerID in zapata.conf with QuadBri or other solution with parallel call signalling
Hi, we are using asterisk with Junghanns QuadBri and some sip phones. 2 channels are configured in NT mode (ISDN PBX connected, internal ) and 2 channels are connected to the public ISDN network (bri-cpe). We use Bristuff 0.2.0 RC8C from Junghanns. When a call comes in from the public phone for a specific extension (Hotline Number), we initiate a parallelcall to some SIP phones and also to our
2009 Feb 06
1
set caller id on outgoing calls through BRI ISDNlines
...te- -->> custom -->> P[ 1] --> * adding2newbc ext 6666666666 -->> P[ 1] --> * adding2newbc callerid 9999999999 -->> P[ 1] --> pres: -1 screen: -1 -->> P[ 1] --> pres: 0 -->> P[ 1] --> PRES: Allowed (0x0) -->> P[ 1] --> SCREEN: Unscreened (0x0) -->> P[ 1] NO OPTS GIVEN -->> P[ 1] I SEND:SETUP oad:9999999999 dad:6666666666 pid:2626 -->> P[ 1] --> bc_state:BCHAN_CLEANED -->> P[ 1] --> channel:0 mode:TE cause:16 ocause:16 rad: cad: -->> P[ 1] --> info_dad: onumplan:0 dnumplan:0 rnumplan:...
2004 Jul 18
1
CID, international style?
I'm thinking of doing an app to work with the CID that's gotten from the Zap channel. All the CID's I see from within the US are 10 digit numbers. I'm out in the rural areas of the US, and no-one ever calls me from overseas. If they did, what would the CID look like? What does the CallerID look like overseas? How many countries provide it? murf
2006 Feb 23
0
isdn problem
...m TPSA, I always geting timeout . Bellow is isdn signaling dump : --> * CallGrp: PickupGrp: --> rxgain:0 txgain:0 --> * dad:118913 tech:mISDN/2-u25 ctx:default --> * Setting Context to from-tpnet --> TON: Unknown --> TON: Unknown --> PRES: Allowed (0x0) --> SCREEN: Unscreened (0x0) --> * adding2newbc ext 118913 --> * adding2newbc callerid 717201234 I SEND:SETUP oad:717201234 dad:118913 port:2 --> mode:TE cause:16 ocause:16 rad: --> info_dad: onumplan:0 dnumplan:0 rnumplan:0 --> channel:0 caps:Speech pi:0 keypad: --> urate:0 rate:0 mode:0 user1:...
2006 Nov 21
3
IAX access to FWD broken?
I hadn't used FWD for quite a while. A customer sent me an email last week, "Is FWD broken when one tries to use it with IAX?" I have been playing around, and indeed seems to be the case. Is there anyone out there successfully using the two of them together? Thanks. B. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be
2009 Feb 06
1
set caller id on outgoing calls through BRIISDNlines
...> P[ 1] --> * adding2newbc callerid -->> > 9999999999 -->> > -->> P[ 1] --> pres: -1 screen: -1 -->> > -->> P[ 1] --> pres: 0 -->> > -->> P[ 1] --> PRES: Allowed (0x0) -->> > -->> P[ 1] --> SCREEN: Unscreened (0x0) -->> > -->> P[ 1] NO OPTS GIVEN -->> > -->> P[ 1] I SEND:SETUP oad:9999999999 -->> > dad:6666666666 pid:2626 -->> > -->> P[ 1] --> bc_state:BCHAN_CLEANED -->> > -->> P[ 1] --> channel:0 mode:TE cause:16 --...
2009 Feb 06
0
set caller id on outgoing calls through BRI ISDN lines
...OUP/6666666666 P[ 1] --> * dad:6666666666 tech:mISDN/1-u23701 ctx:from-pstn-deviate-custom P[ 1] --> * adding2newbc ext 6666666666 P[ 1] --> * adding2newbc callerid 9999999999 P[ 1] --> pres: -1 screen: -1 P[ 1] --> pres: 0 P[ 1] --> PRES: Allowed (0x0) P[ 1] --> SCREEN: Unscreened (0x0) P[ 1] NO OPTS GIVEN P[ 1] I SEND:SETUP oad:9999999999 dad:6666666666 pid:2626 P[ 1] --> bc_state:BCHAN_CLEANED P[ 1] --> channel:0 mode:TE cause:16 ocause:16 rad: cad: P[ 1] --> info_dad: onumplan:0 dnumplan:0 rnumplan:0 cpnnumplan:0 P[ 1] --> caps:Speech pi:0 keypad: sendin...
2008 Nov 05
0
b410p mIDSN - RNIS signaling problems
...jb: Called Wed Nov 5 21:04:15 2008: P[ 2] --> * CallGrp: PickupGrp: Wed Nov 5 21:04:15 2008: P[ 2] --> CTON: Unknown Wed Nov 5 21:04:15 2008: P[ 2] --> EXPORT_PID: pid:74 Wed Nov 5 21:04:15 2008: P[ 2] --> PRES: Restricted (0) Wed Nov 5 21:04:15 2008: P[ 2] --> SCREEN: Unscreened (0) Wed Nov 5 21:04:15 2008: P[ 2] * Queuing chan 0x9121c28 Wed Nov 5 21:04:15 2008: P[ 2] CONTEXT:numeris-in Wed Nov 5 21:04:15 2008: P[ 2] SENDEVENT: stack->nt:0 stack->uperid:40000204 Wed Nov 5 21:04:15 2008: P[ 2] I SEND:PROCEEDING oad:0610493763 dad:0412 pid:74 Wed Nov 5 21:...
2006 Nov 05
1
asterisk DTMF detection
...n:0 rnumplan: cpnnumplan:0 P[ 4] --> caps:Audio 3.1k pi:3 keypad: sending_complete:1 P[ 4] --> Bearer: Audio 3.1k P[ 4] --> Codec: Alaw P[ 0] --> * NEW CHANNEL dad:9298 oad: P[ 4] --> CTON: Unknown P[ 4] EXPORT_PID: pid:3 P[ 4] --> PRES: Restricted (0) P[ 4] --> SCREEN: Unscreened (0) P[ 4] I SEND:PROCEEDING oad: dad:9298 pid:3 P[ 4] --> bc_state:BCHAN_CLEANED P[ 4] --> channel:1 mode:TE cause:16 ocause:16 rad: cad: P[ 4] --> info_dad: onumplan: dnumplan:0 rnumplan: cpnnumplan:0 P[ 4] --> caps:Audio 3.1k pi:3 keypad: sending_complete:1 -- Executing Set...
2010 Jun 10
2
ISDN -> SIP
...ne P[ 1] --> bc_state:BCHAN_ACTIVATED P[ 1] --> Bearer: Speech P[ 1] --> Codec: Alaw P[ 0] --> * NEW CHANNEL dad:12345 oad:xxx P[ 1] read_config: Getting Config P[ 1] --> CTON: Unknown P[ 1] --> EXPORT_PID: pid:2 P[ 1] --> PRES: Allowed (0) P[ 1] --> SCREEN: Unscreened (0) P[ 1] * Queuing chan 0x89e5410 P[ 1] I SEND:RELEASE oad:xxx dad:12345 pid:2 P[ 1] --> bc_state:BCHAN_ACTIVATED P[ 1] --> channel:1 mode:TE cause:16 ocause:1 rad: cad: P[ 1] --> info_dad: onumplan:2 dnumplan:4 rnumplan: cpnnumplan:0 P[ 1] --> caps:Speech pi:0 keypad: sen...
2006 Apr 28
1
mISDN: No DID/extension information returns busy to caller
...1] --> * dad:10030224326465 tech:mISDN/1-u116 ctx:default P[ 1] --> * adding2newbc ext 10030224326465 P[ 1] --> * adding2newbc callerid 16 P[ 1] update_config: Getting Config P[ 1] --> pres: -1 screen: -1 P[ 1] --> pres: 0 P[ 1] --> PRES: Allowed (0x0) P[ 1] --> SCREEN: Unscreened (0x0) P[ 1] SETOPT: No DSP P[ 1] I SEND:SETUP oad:16 dad:10030224326465 P[ 1] --> mode:TE cause:16 ocause:16 rad: P[ 1] --> facility:FAC_NONE out_facility:FAC_NONE P[ 1] --> info_dad: onumplan:0 dnumplan:0 rnumplan:0 P[ 1] --> screen:0 --> pres:0 P[ 1] --> channel:0 caps:S...
2010 Mar 25
9
Maximum number of PRI calls on 1 asterisk box (no HW echo)
Hi, Does anyone have any good empirical data suggesting what the maximum number of PRI calls (incoming and outgoing) without hardware echo cancellation can be handled on a single box is? I have a TE410P T1 (1st gen) card and I'm seeing interesting errors of D-Channels going down and then coming back up (See below). I've looked at the number of simultaneous calls at each of these points,