[cisco-voip] T1 dropoffs.

[peter.casanave at us.army.mil]

Eric,

   We figured out the problem. It was a software problem in the tactical circuit switch. We have patched it and since have it up and good. By IDSN I meant the default switch type i.e. 5ess which we are using. We are using ds0-groups on a T1 emulating a 5ess. For our pri circuits we emmulate a dms-100. 
   Here is one thing I had a couple of questions about. If you are not running MGCP in your voice network and your gateway router accesses the T1s by dial-peer instruction, are their any commands required for the gateway to access PBX. I my situation I have a c3745 with 4 T1s. We have two in use right now and may add the other two soon. The two T1s are going to the same PBX. I know MGCP would probably make this work easier but, we are not using this at this time. My current dial-peers are identical for both T1s. The following is an example of how my dial-peers look now:

dial-peer voice 1 pots
 destination-pattern .......
 port 3/0:0
 foward-digits all

dial-peer voice 2 pots
 destination-pattern .......
 port 3/1:0
 foward-digits all

The problem is that we do not have high call volume at this time but, here soon these circuits will be saturated. Will this method work. Is this the best way? And will this load balance at all? I know this may be elementary but, we, my Platoon of Soldiers, are learning this on the fly out of books. We have no formal training. Kevin Knowlen and I who are both members of this mailing-list have extensive router experience but not much with voice. Thank you all for your time.

V/R,
PETER CASANAVE
SSG, USA
BBN Platoon Sergeant

-------------- next part --------------
A non-text attachment was scrubbed...
Name: peter.casanave.vcf
Type: text/x-vcard
Size: 270 bytes
Desc: Card for <peter.casanave at us.army.mil>
Url : https://puck.nether.net/pipermail/cisco-voip/attachments/20040723/b3fa02fa/peter.casanave.vcf