Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Dial on outbound dialing Magix R4.0

Status
Not open for further replies.

mode1

Programmer
Mar 4, 2008
171
US
Recently cutover 2 Different customer's to a Dynamic PRI. One of the 2 had voice only PRI with no problems on outbound dialing. Had CO install T-Bird on circuit and outbound calls took about 2 seconds. When plugged back into phone system about 10 seconds to dial. If I press # after number speeds up to about 3 to 4 seconds. Customer does not like the thought of having to do this. I adjusted interdigits timers and got delay down to about 4 seconds but then I had issues at times with long distance as well as some 800 calls. Customer is getting antsy. Any other suggestions would be appreciated!
 
Legend/Magix does not let the digits out to the PRI until it knows that you are done dialing. That's what the # signifies. Otherwise, it is storing your digits, comparing them to the ARS tables, and any restrictions that might have been placed against your extension.

You could put a pool button on the phone, to access the PRI channels directly, but that would bypass restrictions. If you don't really use ARS, you could renumber ARS to something else and renumber the PRI pool to 9.
 
TTT, was wondering if you might have an idea why the system worked without delay on a straight voice pri. Does it have something to do with the new PRI being voice and data ran through Adtran router.
 
Do you have a fixed number of channels for voice from the Adtran to the Magix? Is it less than before, and if so, did you remove the unused channels from the pool? Was the previous T1 a PRI or E&M?
 
This is a dynamic PRI voice and data on same circuit full 23 channels for voice. Nothing has changed fromm original pri other than the data being brought through same pri. The adtran is installed from pri provider.
 
Please define what your provider means by "dynamic" PRI.

PRIMARY ISDN service can be used for voice or data. There is no specific type that is either/or. It works for both as is! It is a switched service. It is not dedicated.

So I would be very curious to know what Adtran hardware is installed and what your provider is doing, and what kind of data transport is set up.

....JIM....
 
A "dynamic" PRI is a T-1 interface with an ATM interface (data pipe)usually used for a companies internet access. The device is usually an Adtran New Vista 3200 with a DSX port on the back for the back that provides the PRI portion. Bandwidth is allocated to the "B" channels only when a call is In or Outbound, however, the "D" channel is maintained at all times for call control, or supposed to be. The rest of the time, the bandwidth is used for internet access. Call setup and teardown time is stretched a bit in this process, and occasionally causes issues. It seems to work best when you have 12 or less "B" channels. More than that and it tends to screw up because of the internet requirements of the customer.
It is like using a Paradyne 3160 for voice and data, but the 3160 uses "fixed" channels, the Adtran does not hence the "dynamic".
 
Dynamic PRI is what Mccloud USA calls to use QOS. SO this is a full "23 channel PRI". MCloud QOS enables proper prioritization of voice, Internet, and data traffic, ensuring proper bandwith is available for each application all the time. MCloud dynamic IP service provides the ability to fully integrate voice, Internet,and VPN services on a single IP connection. So back to my original post where does my outbound delay come from after going to this type of service.Thanks in advance!
 
What happens if all 23 channels are in use by the Magix?

When bastardizing a PRI like this, you can't have your cake and eat it too! The problem I see with this type of setup is the CO switch wants to assign a specific BCH, but it is not available. So the Magix and the CO switch negotiate another BCH in order to get the call processed. This type of operation will cause the "call set up" to take longer, hence your delay.

Now depending on what parameters are set, it may provide a minimum in either case, but I don't "see" how you would get all 23 BCHs if X = some amount of bandwidth for data.

One solution may be paring down the 23 channels on both sides of the ADTRAN device to a fixed amount for a minimum, unless Mcleod USA has some other alternative, other than adding another DS1 circuit.

*************
I really think it is about time the providers, ILECs, etc. LOWER THE COSTS of DS1s. They have NOT passed on any of the savings in hardware and provisioning advancements since they have been using fiber or HDSL!!!

....JIM....
 
What they are basically doing is VoIP (internet packetized bit stream)to the customer site then dropping the voice calls out on the DSX interface. A 64K "B" channel for a voice call can be compressed (read: squeezed)to about 7.2K, which when you add the added overhead for the Packet header and control/routing packets works out to about 8k of bandwidth per call. It does depend on which compression Codec they use, there are several. This is one of the basic reasons data (and modem) calls won't work worth a dang over IP, you cannot compress a data call and expect it to work. If you use the G.711 codec (64k-uncompressed) then you can send a "data" call, but guess what?, it takes 80k of bandwidth (16k of overhead) to send the call via IP, not 64k, you do the math.
Mode1, this is why your "voice only" dynamic PRI works "ok", In the Magix you can choose "voice" or "data" or "both" in the PRI setup, I would bet the "working switch is "voice" and the 'iffy' switch is "both"??? It takes the switch additional time to negotiate the call-setup if it is set to "both" because the Adtran has to reach a compromise before 'it' can route the call also.
By the way, you could have different provisioning set up in the Adtran's too. As you can see this can get complex quickly.
 
I was able to go back to this site and try all above mentioned steps. I renumbered PRI pool to 9 and renumbered ars to a different number and this did not work. I put the pri pool directly on a button and this did not work as well. I made both the pri to voice only as well as the ars to voice only and this did not work. The only thing that will work is a # after the number dialed. Anymore suggestions would be greatly appreciated. Thanks!
 
If the two different customers have the same telco vendor, one works properly? and one doesn't, I would ask the vendor for a printout of the Adtran configs from both customers and do a "stare and compare" to see if you can spot any obvious differences between them. PRI can be a funny bird at times, and differences in programming can be the root of all evil.
 
Since the Magix uses the channels in the PRI in a circular fashion, and you describe the PRI as "dynamic", it leads me to beleive that the Magix is requesting channels that the Adtran is not ready to provide, and the two systems are hunting around to find a ready unused channel.

Do you have each line labeled uniquely? Line T1-01, T1-02, etc.? Do you see it picking a different channel every time?

How about if you take ONE channel out of the pool, and put it in a pool all by itself. Then give an extension the pool dial out code, or put it on a button. Then try a few test calls, and see if those go faster. That would eliminate any negoiations on the Magix's part.

 
Hello phonesrus thanks for the responces. When I stated at the beginning of my thread about the 2 customers what I meant is the customer had a previous PRI that was not integrated with their data. The pri was used only for voice. They had a seperate circuit for data. The other customer had a partner with pots lines. Upgraded them to magix with integrated PRI.
 
TTT, I have all channels labeled pri 805 thru and they are in pool 890. I put that pool on a button by its self and dialed out from that pool button still the same delay.
 
But takem for instance, 805 OUT of 890, and put it in 891. Then put a pool 891 button on a set and test, so you know what happens when you access one specific channel without using ARS. If there is still a delay, I'd look to the provider to solve it.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top