RE: [on-asterisk] Calls not connecting on PRI span
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: asterisk@uc.org 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.
Re: [on-asterisk] Calls not connecting on PRI span
zaptel.conf has one pri_cpe and one pri_net I see the calls being made but no connecting message. show channels shows the one call in Ring state and never getting connected. topbx*CLI show channels Channel Location State Application(Data) 0 active channels 0 active calls -- Executing Dial(SIP/7046-052dafd0, 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 Answer(Zap/47-1, ) in new stack -- Executing 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-052dafd0 topbx*CLI show channels Channel Location State Application(Data) Zap/47-1 [EMAIL PROTECTED]:2 Up MusicOnHold() Zap/23-1 [EMAIL PROTECTED]:1Dialing AppDial((Outgoing Line)) SIP/7046-052dafd0[EMAIL PROTECTED]:1RingDial(Zap/G0/300|45) 3 active channels 2 active calls -- Nobody picked up in 45000 ms -- Hungup 'Zap/23-1' -- Channel 0/23, span 2 got hangup request, cause 16 topbx*CLI show channels Channel Location State Application(Data) Zap/47-1 [EMAIL PROTECTED]:2 Up MusicOnHold() SIP/7046-052dafd0[EMAIL PROTECTED]:2Ring(None) 2 active channels 2 active calls -- Timeout on SIP/7046-052dafd0 == CDR updated on SIP/7046-052dafd0 -- Executing Hangup(SIP/7046-052dafd0, ) in new stack == Spawn extension (esi-toronto, t, 1) exited non-zero on 'SIP/7046-052dafd0' topbx*CLI show channels Channel Location State Application(Data) Zap/47-1 [EMAIL PROTECTED]:2 Up MusicOnHold() 1 active channel 1 active call topbx*CLI /var/log/asterisk/cdr-csv/Master.csv ,7046,t,esi-toronto,device 7046,SIP/7046-1bf3ea20,Zap/23-1,Hangup,,2007-07-04 11:13:40,,2007-07-04 11:14:35,55,0,NO ANSWER,DOCUMENTATION McQuiggan, Mark - Broadridge (Toronto) wrote: 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: asterisk@uc.org 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.
RE: [on-asterisk] Calls not connecting on PRI span
Dave: Try a straight-through cable. You need a straight-thru to connect a pri_cpe to a pri_net. You may want to check that the pri_net group timing is set to 1 (primary) in your zaptel.conf, as well (http://www.voip-info.org/wiki/index.php?page=Zaptel.conf+span+syntax). Thanks, M. Please note: Effective April 1, my e-mail address is [EMAIL PROTECTED] -Original Message- From: David Cook [mailto:[EMAIL PROTECTED] Sent: Wednesday, July 04, 2007 11:23 AM To: McQuiggan, Mark - Broadridge (Toronto) Cc: asterisk@uc.org Subject: Re: [on-asterisk] Calls not connecting on PRI span zaptel.conf has one pri_cpe and one pri_net I see the calls being made but no connecting message. show channels shows the one call in Ring state and never getting connected. topbx*CLI show channels Channel Location State Application(Data) 0 active channels 0 active calls -- Executing Dial(SIP/7046-052dafd0, 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 Answer(Zap/47-1, ) in new stack -- Executing 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-052dafd0 topbx*CLI show channels Channel Location State Application(Data) Zap/47-1 [EMAIL PROTECTED]:2 Up MusicOnHold() Zap/23-1 [EMAIL PROTECTED]:1Dialing AppDial((Outgoing Line)) SIP/7046-052dafd0[EMAIL PROTECTED]:1RingDial(Zap/G0/300|45) 3 active channels 2 active calls -- Nobody picked up in 45000 ms -- Hungup 'Zap/23-1' -- Channel 0/23, span 2 got hangup request, cause 16 topbx*CLI show channels Channel Location State Application(Data) Zap/47-1 [EMAIL PROTECTED]:2 Up MusicOnHold() SIP/7046-052dafd0[EMAIL PROTECTED]:2Ring(None) 2 active channels 2 active calls -- Timeout on SIP/7046-052dafd0 == CDR updated on SIP/7046-052dafd0 -- Executing Hangup(SIP/7046-052dafd0, ) in new stack == Spawn extension (esi-toronto, t, 1) exited non-zero on 'SIP/7046-052dafd0' topbx*CLI show channels Channel Location State Application(Data) Zap/47-1 [EMAIL PROTECTED]:2 Up MusicOnHold() 1 active channel 1 active call topbx*CLI /var/log/asterisk/cdr-csv/Master.csv ,7046,t,esi-toronto,device 7046,SIP/7046-1bf3ea20,Zap/23-1,Hangup,,2007-07-04 11:13:40,,2007-07-04 11:14:35,55,0,NO ANSWER,DOCUMENTATION McQuiggan, Mark - Broadridge (Toronto) wrote: 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: asterisk@uc.org 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
Re: [on-asterisk] Calls not connecting on PRI span
On 7/4/07, McQuiggan, Mark - Broadridge (Toronto) [EMAIL PROTECTED] wrote: Dave: Try a straight-through cable. You need a straight-thru to connect a pri_cpe to a pri_net. Maybe I misunderstand, but what you're saying doesn't seem right. I've never connected Asterisk to Asterisk but I've connected Asterisk line side to a bunch of different things (Avaya and Nortel PBXs). I've alway used a T1 crossover cable and then had one side act as NET and the other as CPE. My understanding was that the crossover cable addressed the electrical requirements and the CPE/NET settings addressed signalling requirements. Am I wrong? I would expect that if Dave had the wrong cable, he wouldn't get anything at all in terms of call setup. In fact, I would think the B and D channels wouldn't initialise. Dave Donovan
Re: [on-asterisk] Calls not connecting on PRI span
Correct you are looking for a DS1-X cable. If I recall, T1 cables are RJ48c spec, so in a crossover scenario pin1 goes to pin4 and pin 2 goes to pin5 and vice versa. If you had the wrong cable, the carrier wouldn't even come up, let alone the B or D channels. - Original Message - From: Dave Donovan To: asterisk@uc.org Sent: Wednesday, July 04, 2007 2:01 PM Subject: Re: [on-asterisk] Calls not connecting on PRI span On 7/4/07, McQuiggan, Mark - Broadridge (Toronto) [EMAIL PROTECTED] wrote: Dave: Try a straight-through cable. You need a straight-thru to connect a pri_cpe to a pri_net. Maybe I misunderstand, but what you're saying doesn't seem right. I've never connected Asterisk to Asterisk but I've connected Asterisk line side to a bunch of different things (Avaya and Nortel PBXs). I've alway used a T1 crossover cable and then had one side act as NET and the other as CPE. My understanding was that the crossover cable addressed the electrical requirements and the CPE/NET settings addressed signalling requirements. Am I wrong? I would expect that if Dave had the wrong cable, he wouldn't get anything at all in terms of call setup. In fact, I would think the B and D channels wouldn't initialise. Dave Donovan
RE: [on-asterisk] Calls not connecting on PRI span
Dave, Dave: OK. I'm a moron. I tested on my spare Sangoma and got the green lights to come up on a xover cable. I got a xover between my Avaya and my Asterisk, but I have it connected as net to net (as per voip-info.org), and it's cool. I always assumed I'm getting' old. Please ignore the prvious advice. M. Please note: Effective April 1, my e-mail address is mailto:[EMAIL PROTECTED] [EMAIL PROTECTED] _ From: Dave Donovan [mailto:[EMAIL PROTECTED] Sent: Wednesday, July 04, 2007 2:02 PM To: asterisk@uc.org Subject: Re: [on-asterisk] Calls not connecting on PRI span On 7/4/07, McQuiggan, Mark - Broadridge (Toronto) [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: Dave: Try a straight-through cable. You need a straight-thru to connect a pri_cpe to a pri_net. Maybe I misunderstand, but what you're saying doesn't seem right. I've never connected Asterisk to Asterisk but I've connected Asterisk line side to a bunch of different things (Avaya and Nortel PBXs). I've alway used a T1 crossover cable and then had one side act as NET and the other as CPE. My understanding was that the crossover cable addressed the electrical requirements and the CPE/NET settings addressed signalling requirements. Am I wrong? I would expect that if Dave had the wrong cable, he wouldn't get anything at all in terms of call setup. In fact, I would think the B and D channels wouldn't initialise. Dave Donovan 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.