search for: pri_event_r

...w it is supposed to behave? From all the docs I can find, it doesn't seem so. Seems to me that the s extension in [default] should work. What are other people's experiences hooking up TDM hardware for incoming calls? The message is coming from chan_zap.c in the function pri_dchannel, case: PRI_EVENT_RING, line 8563, as an else clause for (overlapdial && ast_canmatch_extension). I am running asterisk-1.2/zaptel-1.2/libpri-1.2 branches on CentOS 4.2 x86_64, Dual Opteron, with Sangoma 104d's hooked right up to a switch in a datacenter on T-1's configured as PRI with a dchannel Th...

Hi We interfaced our ASCOTEL PBX to Asterisk. by EuroISDN PRI , DSS1 It works fine on channels 1- 15, but on 17-31 the miststood each other. Asterisk speaks in Timeslots, the PBX in B-channels The signalling is ok, but the bridging is shifted. The first incoming connection is bridged to "nirwana" also no indication is hearable, calling a second internal subcribes bridges them to the

Hi, Yet another question, now that I have callerid working correctly, I'm trying to work out how to utilise the different numbers I have. I have a 100 number range allocated to my E1/PRI/OnRamp service. My incoming calls are handled like this: Advertised/published number is an analogue line terminating on a X101P. If the analog line is busy, it has a call diversion to the PRI on a TE405P

...0.10005.0.4 1 operationValue = ROSE_NI2_InformationFollowing 1 unknown Enumerated(10 0x0A) = 0 0x0000 1 !! ROSE invoke operation not handled! ROSE_NI2_InformationFollowing 1 q931.c:7587 post_handle_q931_message: Call 457 enters state 6 (Call Present). Hold state: Idle Span: 1 Processing event: PRI_EVENT_RING 1 q931.c:4906 q931_call_proceeding: Call 457 enters state 9 (Incoming Call Proceeding). Hold state: Idle 1 1 > DL-DATA request 1 > Protocol Discriminator: Q.931 (8) len=10 1 > TEI=0 Call Ref: len= 2 (reference 457/0x1C9) (Sent to originator) 1 > Message Type: CALL PROCEEDING (2) 1...

...ing IE 108 (cs0, Calling Party Number) PRI Span: 1 -- Processing IE 112 (cs0, Called Party Number) PRI Span: 1 -- Processing IE 125 (cs0, High-layer Compatibility) PRI Span: 1 q931.c:8281 post_handle_q931_message: Call 14783 enters state 6 (Call Present). Hold state: Idle Span 1: Processing event PRI_EVENT_RING(5) PRI Span: 1 q931.c:5477 q931_call_proceeding: Call 14783 enters state 9 (Incoming Call Proceeding). Hold state: Idle PRI Span: 1 PRI Span: 1 > DL-DATA request PRI Span: 1 > Protocol Discriminator: Q.931 (8) len=10 PRI Span: 1 > TEI=0 Call Ref: len= 2 (reference 14783/0x39BF) (Sent...

...esentationAllowedSimple Context Specific [0 0x00] = PRI Span: 1 <4F 4D 41 58 20 43 4F 52-50 20 4E 20 47 53 4D> - "<source_caller_name>" PRI Span: 1 q931.c:8646 post_handle_q931_message: Call 23832 enters state 6 (Call Present). Hold state: Idle Span 1: Processing event PRI_EVENT_RING(5) *PRI Span: 1 q931.c:7135 q931_hangup: Hangup other cref:23832* *PRI Span: 1 q931.c:6892 __q931_hangup: ourstate Call Present, peerstate Call Initiated, hold-state Idle* *PRI Span: 1 q931.c:6081 q931_disconnect: Call 23832 enters state 11 (Disconnect Request). Hold state: Idle* PRI Span:...

...7 49> - "Cell Phone WI" [Jan 14 12:56:04] VERBOSE[13262] chan_dahdi.c: [Jan 14 12:56:04] PRI Span: 4 q931.c:8281 post_handle_q931_message: Call 6918 enters state 6 (Call Present). Hold state: Idle [Jan 14 12:56:04] VERBOSE[13262] sig_pri.c: [Jan 14 12:56:04] Span 4: Processing event PRI_EVENT_RING [Jan 14 12:56:04] VERBOSE[13262] chan_dahdi.c: [Jan 14 12:56:04] PRI Span: 4 q931.c:5477 q931_call_proceeding: Call 6918 enters state 9 (Incoming Call Proceeding). Hold state: Idle [Jan 14 12:56:04] VERBOSE[13262] chan_dahdi.c: [Jan 14 12:56:04] PRI Span: 4 [Jan 14 12:56:04] VERBOSE[13262] chan...