papa-bear

local telco buying time to fix problem?

Though my tunking experience is limited, I can't see how it is rejected if calls can be made into the system from outside the local area.

rhack

For the calls that work from outside of the local area code, are they coming in on different trunks? Is it possible that you are receiving different digit lengths on different trunk routes? For example if you have inbound dedicated service from say, Sprint or AT&T you may be receiving 4 digits, were on your local trunks you may be receivine 5, 7 or 10? If this is the case, without digit manipulation you may be sending the wrong number of digits to the faxserver.

I have had experience with fax servers that are not flexible in handling different digit lengths. To compensate for it I have had to do some manipulation to get the right digits to the fax server. For example, local telco sends us 10d, tie lines send 7. Internal calling sends 7. Luckily with our switch I could do conditionally routing based on the class of service on the trunks and take appropriate measures to send the right amount of digits.

jack

Just for grins can you out one of the CDP DID #'s and put that number on a set as a dn? Then try pots call does call complete?

__________________
Dogs rollover Phones hunt

Buckshot

That sounds like a telco intercept to me. When telco passes a call on a circuit, and it reaches the far end, a busy circuit at the far end will give out a busy, not an intercept (unless it is your specific message). If it is the telco intercept, then it is possible they arent even sending the call to your destination. Sounds like a vendor meet is on the horizon.

vztech1

thanks for the replies...calls were coming in on same route. That's what was baffling. DCH showed outgoing message:

DCH 1 UIPE_OMSG CC_DISC_REQ REF 0000BE03 CH 4 2 TOD 6:54:35 CK 0EB6E0D6
CAUSE: #42 - SWED EQIP CONGESTION

Dissapointed I didn't catch it, but a support engineer found tandem Tie route to faxserver was set for VCE, he changed it to 3VCE and solved the issue. Why other POTS calls from every other area code we could find to test with worked is still unknown ?????

telecom116

Maybe the local LEC that you use to get your PRI service also acts as the tandem for Intra-LATA calls, maybe even on the same switch. For out of NPA calls, possibly the SS7 call failure information wasn't getting passed along. Again, just assuming...

I had something similar with a TIE line off our 11c to an IVR unit where I was inserting DNIS digits and the box was seeing an extra digit. Finally figured out that during a reconfiguration I accidentely used VOD instead of 3VCE for the type and it was inserting an extra digit used to differentiate between voice and data calls.