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 TouchToneTommy on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Denial Event 1220 Question 1

Status
Not open for further replies.

bwilch

Technical User
May 5, 2003
627
US
We have two sites tied together. They're trying to place a call from the primary site (which is an S8500) to the secondary site (S8300) and we're getting an denail event. The line from the list trace reads: "Denial event 1220: ISDN recovery timer expiry D1=0x3d D2=0x66" Any suggestions on how to resolve this error?

Thank you for any insight you may have.
 
Sorry for the lack of detail. Was hoping I could figure out what the 1220 was or see if it triggered any response. Basically we have 2 sites, Primary (P) and Secondary (S). The P is an S8500. We are using an VPN circuit to connect it to the S which is an S8300. Basically this is setup as two sites UDP'd together. The digital S phones can dial and connect to the P site without incident. However, when we initiate a call from the P site to the S set, we get dead air on the P set and the S set will ring, if ansewred, there is only dead air. When doing the list trace on the P site, we get the ISDN 1220 error. On the remote site, we see it activate the trunk, dial the station, then terminate the trunk.

This hasn't worked before, this is something new we are setting up. The two sites are configured basically the same as far as the sig group and trunk groups.
 
are they IP, if so on the signal group form make"calls share ip signaling connection" yes.
 
Seen that before, try removing the signaling groups and adding them again with different signaling group numbers. If this does not work replace the CLAN on the S8500 site and be sure to check the IP network (switches, routers etc.)for errors during transmition of data...

Petran.
 
We found the issue. It ended up being the port number. The port numbers were the default (I think 1720). We had to change them to something else. Once we did, everything started working fine. Thanks for the suggestions!
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top