Hello All, I've mostly solved my DID problem from a few days ago. Apparenly the lines weren't configured properly. Now heres the next question. 12 E&M wink lines from telco. I have them all plugging into an Adtran 750 with FXS cards. The Adtran ports are configured DPO. How do I signal this from Zaptel. I have them setup E&M in zaptel.conf and EM_W in zapata.conf. They work, however, no DNIS info is being passed. Do I need to signal these something different like loopstart or kewlstart, so the DNIS info gets passed? I watch the Tx/Rx bits from zttool, and everything looks okay coming from the Adtran. It looks like asterisk isn't winking properly. When I had the lines misconfigured for fxs_ls the DNIS info was passing fine. I'm running zaptel-0.8.0 libpri-0.5.1 And asterisk CVS from 12/23/2003 RedHat 8.0 Dual 2.4 Xeon Processors (hyperthreading disabled) 2Gig Memory Any help would be greatly appreciated. Regards, -sb
> Hello All, > > I've mostly solved my DID problem from a few days ago. Apparenly the > lines weren't configured properly. Now heres the next question. 12 E&M > wink lines from telco. I have them all plugging into an Adtran 750 with > FXS cards. The Adtran ports are configured DPO. How do I signal this > from Zaptel. I have them setup E&M in zaptel.conf and EM_W in > zapata.conf. They work, however, no DNIS info is being passed. Do I need > to signal these something different like loopstart or kewlstart, so the > DNIS info gets passed? I watch the Tx/Rx bits from zttool, and everything > looks okay coming from the Adtran. It looks like asterisk isn't winking > properly.I had a similar problem. I ended up setting the trunks to either just plain em or featd (I don't remember). I chased through the chan_zap source code and decided (maybe incorrectly) that asterisk doesn't look for DNIS digits in E&M Wink mode.
I tried both featd and em in zapata.conf, to no avail. I restarted in between all changes. Is it possible to signal the DPO ports on the 750 with fxo_ls or fxo_ks? This is the last piece to my DID puzzle. Anyone else with experience on this oddball config? Thanks, -sb -----Original Message----- From: asterisk-users-admin@lists.digium.com [mailto:asterisk-users-admin@lists.digium.com]On Behalf Of James Sharp Sent: Friday, January 30, 2004 11:52 AM To: asterisk-users@lists.digium.com Subject: Re: [Asterisk-Users] Adtran 750 DID question.> Hello All, > > I've mostly solved my DID problem from a few days ago. Apparenly the > lines weren't configured properly. Now heres the next question. 12 E&M > wink lines from telco. I have them all plugging into an Adtran 750 with > FXS cards. The Adtran ports are configured DPO. How do I signal this > from Zaptel. I have them setup E&M in zaptel.conf and EM_W in > zapata.conf. They work, however, no DNIS info is being passed. Do I need > to signal these something different like loopstart or kewlstart, so the > DNIS info gets passed? I watch the Tx/Rx bits from zttool, and everything > looks okay coming from the Adtran. It looks like asterisk isn't winking > properly.I had a similar problem. I ended up setting the trunks to either just plain em or featd (I don't remember). I chased through the chan_zap source code and decided (maybe incorrectly) that asterisk doesn't look for DNIS digits in E&M Wink mode. _______________________________________________ Asterisk-Users mailing list Asterisk-Users@lists.digium.com http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Did you say you were using Adtran FXS cards? Bisker, Scott (7805) wrote:> Hello All, > > I've mostly solved my DID problem from a few days ago. Apparenly the lines weren't configured properly. Now heres the next question. 12 E&M wink lines from telco. I have them all plugging into an Adtran 750 with FXS cards. The Adtran ports are configured DPO. How do I signal this from Zaptel. I have them setup E&M in zaptel.conf and EM_W in zapata.conf. They work, however, no DNIS info is being passed. Do I need to signal these something different like loopstart or kewlstart, so the DNIS info gets passed? I watch the Tx/Rx bits from zttool, and everything looks okay coming from the Adtran. It looks like asterisk isn't winking properly. > > When I had the lines misconfigured for fxs_ls the DNIS info was passing fine. > > I'm running > zaptel-0.8.0 > libpri-0.5.1 > And asterisk CVS from 12/23/2003 > RedHat 8.0 > Dual 2.4 Xeon Processors (hyperthreading disabled) > 2Gig Memory > > Any help would be greatly appreciated. > > Regards, > > -sb > _______________________________________________ > Asterisk-Users mailing list > Asterisk-Users@lists.digium.com > http://lists.digium.com/mailman/listinfo/asterisk-users > To UNSUBSCRIBE or update options visit: > http://lists.digium.com/mailman/listinfo/asterisk-users > >
Yes. Adtran FXS cards. Did you say you were using Adtran FXS cards? Bisker, Scott (7805) wrote:> Hello All, > > I've mostly solved my DID problem from a few days ago. Apparenly the lines weren't configured properly. Now heres the next question. 12 E&M wink lines from telco. I have them all plugging into an Adtran 750 with FXS cards. The Adtran ports are configured DPO. How do I signal this from Zaptel. I have them setup E&M in zaptel.conf and EM_W in zapata.conf. They work, however, no DNIS info is being passed. Do I need to signal these something different like loopstart or kewlstart, so the DNIS info gets passed? I watch the Tx/Rx bits from zttool, and everything looks okay coming from the Adtran. It looks like asterisk isn't winking properly. > > When I had the lines misconfigured for fxs_ls the DNIS info was passing fine. > > I'm running > zaptel-0.8.0 > libpri-0.5.1 > And asterisk CVS from 12/23/2003 > RedHat 8.0 > Dual 2.4 Xeon Processors (hyperthreading disabled) > 2Gig Memory > > Any help would be greatly appreciated. > > Regards, > > -sb > _______________________________________________ > Asterisk-Users mailing list > Asterisk-Users@lists.digium.com > http://lists.digium.com/mailman/listinfo/asterisk-users > To UNSUBSCRIBE or update options visit: > http://lists.digium.com/mailman/listinfo/asterisk-users > >_______________________________________________ Asterisk-Users mailing list Asterisk-Users@lists.digium.com http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
I posted this below message few days ago, but some how it didn't show up in the mailing list. When some one calls into your DID Trunk line what symptom do you see on Adtran as well as on Asterisks console? Asterisk winks properly in FXO DPO mode, we had checked this things with our Telco instruments. If your PBX doesn't wink to Telco, your DID line's will become busy, that is one way to check whether Asterisk is winking properly or not. What series FXS card you are using? Is it L1 or L2? Because only L1 series cards work with our DID trunk line. I don't know why and still Adtran technical support is not able to figure out. I have same configuration running in my office and finally with all the help from Digium and adtran, problem seems to be less. Still fully it is not resolved yet because FXS L2 is not working. Hopefully Adtran will release new firmware. Regards, Kekin -----Original Message----- From: Kekin Dand Sent: Tuesday, January 27, 2004 5:24 PM To: asterisk-users@lists.digium.com Subject: Re:Incoming DID call Voice Problems I had similar problem and it took all most 2 months to resolve it. Few things you have check in your Adtran 750 configuration. 1. For incoming DID trunk line it has to terminated on FXS card. (Which I think you already did) 2. FXS card needs to be set on FXS DPO mode in order to work properly. 3. Your DID trunk line should be configured in Asterisk as "em" in zaptel.conf and e&m_w in Zapata.conf. Reason you are facing this problem either your battery is not getting reversed and Telco can't see Answer Supervision on your line when the calls get connected. If you have ohms meter or multimeter check your DID line voltages. When inbound call comes in and both parties go off hook you should see positive voltage on that line, in idle situation(on hook) you will negative 48V. Yes, local calls are different then long distance. Answer Supervision is not required for local calls. Only for long distance it is required, so that Telco can start billing. Hope this should resolve your problem. Regards, Kekin Subject: RE: [Asterisk-Users] Incoming DID call Voice Problems Date: Mon, 26 Jan 2004 09:31:32 -0500 From: "Bisker, Scott (7805)" <sbisker@harvardgrp.com> To: <asterisk-users@lists.digium.com> Reply-To: asterisk-users@lists.digium.com I have an updated question on this one. It seems that only inbound long distance calls (calls from outside the local calling area) on our DID trunk have one-way voice. I have my adtran 750 fxs lines configured as FXS Loopstart with all the defaults. Again, the problem is that once = the call bridges, the outside caller can hear the person they called, = but the inside person can't hear the caller. This happens regardless of = the internal technology, SIP, Zap, H323. Could it be possible that inbound long distance calls are signalled different than inbound local calls? Inbound calls on the PRI work flawlessly. Any ideas -sb
I guess asterisk is winking properly then, because the line rings when dialed.
In zaptel.conf the lines are set to e&m and in zapata.conf they are set to
e&m_w. The FXS cards are series L1.
What I'm seeing is that the DNIS info is not being passed through to
asterisk. Since I get no DNIS, it shoves the call to my s extension.
This is what I see on console
-- Starting simple switch on 'Zap/3-1'
Once I see the call come in I do a show channel and here is what I get.
-- General --
Name: Zap/3-1
Type: Zap
UniqueID: 1075499367.29
Caller ID: (N/A)
DNID Digits: (N/A)
State: Ring (4)
Rings: 1
NativeFormat: 68
WriteFormat: 4
ReadFormat: 4
1st File Descriptor: 48
Frames in: 212
Frames out: 0
Time to Hangup: 0
-- PBX --
Context: local
Extension: s
Priority: 1
Call Group: 0
Pickup Group: 0
Application: (N/A)
Data: (None)
Stack: -1
Blocking in: ast_waitfor_nandfds
Any ideas on this?
-sb
...
When some one calls into your DID Trunk line what symptom do you see on
Adtran as well as on Asterisks console?
Asterisk winks properly in FXO DPO mode, we had checked this things with our
Telco instruments. If your PBX doesn't wink to Telco, your DID line's
will
become busy, that is one way to check whether Asterisk is winking properly
or not.
What series FXS card you are using? Is it L1 or L2? Because only L1 series
cards work with our DID trunk line. I don't know why and still Adtran
technical support is not able to figure out.
I have same configuration running in my office and finally with all the help
from Digium and adtran, problem seems to be less.
Still fully it is not resolved yet because FXS L2 is not working.
Hopefully Adtran will release new firmware.
Regards,
Kekin
-----Original Message-----
From: Kekin Dand
Sent: Tuesday, January 27, 2004 5:24 PM
To: asterisk-users@lists.digium.com
Subject: Re:Incoming DID call Voice Problems
I had similar problem and it took all most 2 months to resolve it.
Few things you have check in your Adtran 750 configuration.
1. For incoming DID trunk line it has to terminated on FXS card. (Which I
think you already did)
2. FXS card needs to be set on FXS DPO mode in order to work properly.
3. Your DID trunk line should be configured in Asterisk as "em" in
zaptel.conf and e&m_w in Zapata.conf.
Reason you are facing this problem either your battery is not getting
reversed and Telco can't see Answer Supervision on your line when the calls
get connected. If you have ohms meter or multimeter check your DID line
voltages. When inbound call comes in and both parties go off hook you should
see positive voltage on that line, in idle situation(on hook) you will
negative 48V.
Yes, local calls are different then long distance. Answer Supervision is not
required for local calls. Only for long distance it is required, so that
Telco can start billing.
Hope this should resolve your problem.
Regards,
Kekin
Subject: RE: [Asterisk-Users] Incoming DID call Voice Problems
Date: Mon, 26 Jan 2004 09:31:32 -0500
From: "Bisker, Scott (7805)" <sbisker@harvardgrp.com>
To: <asterisk-users@lists.digium.com>
Reply-To: asterisk-users@lists.digium.com
I have an updated question on this one. It seems that only inbound long
distance calls (calls from outside the local calling area) on our DID trunk have
one-way voice. I have my adtran 750 fxs lines configured as FXS Loopstart with
all the defaults. Again, the problem is that once = the
call bridges, the outside caller can hear the person they called, = but the
inside person can't hear the caller. This happens regardless of = the
internal technology, SIP, Zap, H323.
Could it be possible that inbound long distance calls are signalled different
than inbound local calls? Inbound calls on the PRI work flawlessly.
Any ideas
-sb
_______________________________________________
Asterisk-Users mailing list
Asterisk-Users@lists.digium.com
http://lists.digium.com/mailman/listinfo/asterisk-users
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users
On Friday, January 30, 2004 3:56 PM, Bisker, Scott (7805) [SMTP:sbisker@harvardgrp.com] wrote:> I guess asterisk is winking properly then, because the line ringswhen> dialed. In zaptel.conf the lines are set to e&m and in zapata.conf > they are set to e&m_w. The FXS cards are series L1. > > What I'm seeing is that the DNIS info is not being passed through to > asterisk. Since I get no DNIS, it shoves the call to my sextension.>Have you verified that immediate = no in zapata.conf? If not, then * may not be waiting for the digits before trying to find a match. Don Pobanz
Yes. immediate=no is in zapata.conf before the channel declaration. This makes absolutely no sense at all. -sb -----Original Message----- From: asterisk-users-admin@lists.digium.com [mailto:asterisk-users-admin@lists.digium.com]On Behalf Of Don Pobanz Sent: Friday, January 30, 2004 5:11 PM To: 'asterisk-users@lists.digium.com' Subject: RE: [Asterisk-Users] Re: Adtran 750 DID question. On Friday, January 30, 2004 3:56 PM, Bisker, Scott (7805) [SMTP:sbisker@harvardgrp.com] wrote:> I guess asterisk is winking properly then, because the line ringswhen> dialed. In zaptel.conf the lines are set to e&m and in zapata.conf > they are set to e&m_w. The FXS cards are series L1. > > What I'm seeing is that the DNIS info is not being passed through to > asterisk. Since I get no DNIS, it shoves the call to my sextension.>Have you verified that immediate = no in zapata.conf? If not, then * may not be waiting for the digits before trying to find a match. Don Pobanz _______________________________________________ Asterisk-Users mailing list Asterisk-Users@lists.digium.com http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Scott, You can't see DNIS on any channels/Line? If I understand correctly you can't see digits coming in from your Telco? And it falls into your S context? Try changing your Adtran Firmware, I tried on L35 and L36 it didn't worked properly, so I am using L34. Also, try changing the wink time in Zapata.h from 150MS to 250MS, once you change the timing you have to recompile Zapata. Kd Subject: RE: [Asterisk-Users] Re: Adtran 750 DID question. Date: Fri, 30 Jan 2004 19:16:26 -0500 From: "Bisker, Scott (7805)" <sbisker@harvardgrp.com> To: <asterisk-users@lists.digium.com> Reply-To: asterisk-users@lists.digium.com Yes. immediate=3Dno is in zapata.conf before the channel declaration. This makes absolutely no sense at all. -sb