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

MWI stopped working, 1

Status
Not open for further replies.

rejackson

IS-IT--Management
Oct 4, 2005
627
US
MM 5.2.1 on SIP to audocodes then QSIG to CM 6.3. MWI stopped out of the blue. Not working on any stations. Several different errors in operational history viewer. All seem to have something to do with Port 0 but I dont know what that is.

I have done the MWI data base rebuild and the FEDBsync but neither made a difference.

MWI request to 'Reset' the lamp has been called for extension: 101463 on port 0
WARNING NT significant event with ID '3221227238' was reported with strings 'Reset\n101463\nProxy/gateway temporarily unavailable\n'.

MWI request to 'Reset' the lamp has been called for extension: 101496 on port 0
MWI notification being sent to high-level component for extension 101486, error Reset, request Proxy/gateway temporarily unavailable from port 0
MWI request to 'Set' the lamp has been called for extension: 101497 on port 0
MWI notification being sent to high-level component for extension 101497, error Set, request Proxy/gateway temporarily unavailable from port 0

 
Hi Of all the threads I have looked at this one seems to be the closest at describing the issue we are trying to resolve.
We are setting up call accounting on ships using CO trunks for the shorelines. We are wanting to monitor outgoing long distance phone call. We need to be able to capture the outgoing long distance #'s called using our CDR. We are using a G650 platform with S8400 servers. We are using VDN to vectors to TAC for each of the 12 CO shoreline trunks we are connected to. If we dial the TAC # for each CO trunk directly then th outgoing # we get a CDR of all the outgoing digits dialed and We can see the digits doing a list trace trunk. If we dial the long distance # directly we do not get the digits dialed in the CDR. The list trace shows that the TAC was dialed and it went to the vector but no outgoing phone # is displayed. We have tried and researched all we can with regards to this and have used every possible CDR parameter and trunk parameter setting. The outgoing LD phone # does get dialed and answered so those digits must be somewhere!
How can we get the outgong digits in the CDR when using VDN and vector to a TAC?
Thanks.
Jerry DePasquale
Tellecom
Truestone LLC


 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top