David:

What's you zaptel.conf say?  Are both groups set to pri_net or pri_cpe
signalling?  You'll need that for a crossover cable...

Thanks,

Mark.


Please note:  Effective April 1, my e-mail address is
[EMAIL PROTECTED]

-----Original Message-----
From: David Cook [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, July 03, 2007 1:57 PM
To: [email protected]
Subject: [on-asterisk] Calls not connecting on PRI span

Here is an interesting support problem.

New A102D card. Span 0/1 tied with a cross over cable (to test).

Dial an extension out one span
exten => _30X,1,Dial(Zap/G0/${EXTEN},45)

Should dial out on last channel of group 0 and should arrive on last
channel of group 1 (other span)

[from-internal]
; inbound from (group 1) Nortel defaults to pass-thru to PSTN
; pstn on trunk group 0, descending order
exten => _.,1,MusiconHold()

I should hear music. However I get no connection ... Last message is
"proceeding" below, no ringing yet the channel (47-1) won't hangup.

It's like it doesn't know to connect the two legs of the call!!

    -- Executing [EMAIL PROTECTED]:1] Dial("SIP/7046-1bebd770",
"Zap/G0/300|45") in new stack
    -- Requested transfer capability: 0x00 - SPEECH
    -- Called G0/300
    -- Accepting call from '7046' to '300' on channel 0/23, span 2
    -- Executing [EMAIL PROTECTED]:1] MusicOnHold("Zap/47-1", "") in
new stack
    -- Started music on hold, class 'default', on Zap/47-1
    -- Zap/23-1 is proceeding passing it to SIP/7046-1bebd770
topbx*CLI>


Asterisk 1.4.5
Zaptel 1.4.3
Sangoma Wanpipe 2.3.4-10

Any ideas??

dbc.
--
David Cook

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

This message and any attachments are intended only for the use of the addressee 
and
may contain information that is privileged and confidential. If the reader of 
the 
message is not the intended recipient or an authorized representative of the
intended recipient, you are hereby notified that any dissemination of this
communication is strictly prohibited. If you have received this communication in
error, please notify us immediately by e-mail and delete the message and any
attachments from your system.

Reply via email to