Cant send/receive fax to remote site on PRI 2

[mjoetech]

Hi,

I have an s8700, CM 5.2 with a remote (LSP) site in Bosten that cant send or receive faxes off their local PRI. I have local analog CO trunks (for backup)that I can termporarily point to the faxes and they then work. However, when I send faxes to the PRI's DID number, the fax machine answered but errors out. The fax machine was swapped out with the same results.

The LEC says it is not a compressed trunk and should send faxes fine. All voice calls are fine and no errors on the DS1. The trunk group is as follows.

TRUNK GROUP

Group Number: 20 Group Type: isdn CDR Reports: y
Group Name: Boston Pri COR: 1 TN: 1 TAC: 820
Direction: two-way Outgoing Display? n Carrier Medium: PRI/BRI
Dial Access? n Busy Threshold: 255 Night Service:
Queue Length: 0
Service Type: public-ntwrk Auth Code? n TestCall ITC: rest
Far End Test Line No:
TestCall BCC: 4

Group Type: isdn

TRUNK PARAMETERS
Codeset to Send Display: 6 Codeset to Send National IEs: 6
Max Message Size to Send: 260 Charge Advice: none
Supplementary Service Protocol: a Digit Handling (in/out): enbloc/enbloc

Trunk Hunt: descend
Digital Loss Group: 13
Incoming Calling Number - Delete: Insert: Format:
Bit Rate: 1200 Synchronization: async Duplex: full
Disconnect Supervision - In? y Out? n
Answer Supervision Timeout: 0
Administer Timers? n CONNECT Reliable When Call Leaves ISDN? n



SIGNALING GROUP

Group Number: 20 Group Type: isdn-pri
Associated Signaling? y Max number of NCA TSC: 2
Primary D-Channel: 002V224 Max number of CA TSC: 2
Trunk Group for NCA TSC:
Trunk Group for Channel Selection: 20
TSC Supplementary Service Protocol: a



Does anyone have any idea what can cause this?

Thanks,

Joe

 

[mjoetech]

yes, I actually did this for the first swap after I saw the T wasn't coming up. I didnt do that today as the users were not happy about dropping their t1 yet again. When I saw the first initial result as the first swap, I felt is wasn't worth repeating the process of removing/rebuilding ports, sig groups,ds-1, etc.. (at least not during the day)

I'll try again after hours, but I'm not feeling hopeful that the card is the issue for some reason..

Joe.

 

[AvayaTier3]

try adding new card in vacant slot
add ds1
add new tg
add new sig group
add trunks
go into MG and set sync to new slot

program route patterns to use new tg

move t1 ckt from old slot to new slot

move back when finished

reprogram

less down time this way. Remove what is not used when done.


A great teacher, does not provide answers, but methods to teach others "How and where to find the answers"

bsh

36 years Bell, AT&T, Lucent, Avaya
Tier 3 for 26 years and counting

http://bshtele.com

 

[sveitch]

Joe - Did you ever get a resolution to this? I am having the exact same situation. I have replaced the MM710 and used a different slot. Same result. I am thinking the carrier is not sending me the clocking but they say otherwise. We have not tried a new G350 chassis as that is the last resort. Tests on the DS1 board all pass but 144 which is the timing slips count. Any help getting this resolved would be appreciated! Thanks!

 

[mjoetech]

Hi, It was a bad G350 gateway. Just as Tier3 suggested. Good luck,

Joe