Using a 4 port Perle Iolan device to send call accounting, wakeup calls, and interface a hotel's property management system. About weekly the property has to reset the Perle iolan because they are not getting call records. The property does not appear to have problems with the PMS interface as guest names / checkin/out is processing without complaints. When the Perle iolan is reset, the call accounting system is flooded with records being kept in the Mitel system. Perle says that there is no setting in their system to keep the UDP connection up and running. Any ideas?
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 strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Mitel 3300 ICP and Call accounting interface
- Thread starter busster
- Start date
- Thread starter
- #2
E2T Comms may or may not be related but usually indicates you have not statically assigned the E2T in your DHCP settings.
There is an island of opportunity in the middle of every difficulty.
Miss that though, and you're pretty much doomed!
There is an island of opportunity in the middle of every difficulty.
Miss that though, and you're pretty much doomed!
Mitelpassion
IS-IT--Management
assuming it's a 3300,
if you are reffering to the smdr records flooding the call accounting software then firstly it's not a UDP port, but a TCP port. port 1752 to be specific.
The "connection" as you refer to it doesn't have to be kept up, it's always ready. The accounting software needs to connect to port 1752 to "come and get" the records. If the software doesn't probe this port then the Mitel will buffer x amount of lines. when the buffer is full it will re-write the older records...
again assuming it's a mitel 3300. not sure how the other models work.
what is the IP address of your controller and what is the IP address of your E2T card. is it perhaps the same? you would more than likely be experiencing TDM call problems if you have E2T comms card alarms..hope this helps
if you are reffering to the smdr records flooding the call accounting software then firstly it's not a UDP port, but a TCP port. port 1752 to be specific.
The "connection" as you refer to it doesn't have to be kept up, it's always ready. The accounting software needs to connect to port 1752 to "come and get" the records. If the software doesn't probe this port then the Mitel will buffer x amount of lines. when the buffer is full it will re-write the older records...
again assuming it's a mitel 3300. not sure how the other models work.
what is the IP address of your controller and what is the IP address of your E2T card. is it perhaps the same? you would more than likely be experiencing TDM call problems if you have E2T comms card alarms..hope this helps
- Thread starter
- #6
Have cdr and wake up calls both going to 1754. This appears to be working. Changed a flow control setting in the Perle IOlan device today. Hopefully this resolves the issue. Still have the E2T alarm. Yes it is a Mitel 3300 icp. Am new to the 3300, but do not see an ip address assigned to a E2T. See the ip address of the controller.
Mitelpassion
IS-IT--Management
chances are if you're e2t doesn't have an ip address you won't be able to make IP to TDM calls, so generally a call from an IP phone to an external ISDN or analogue trunk wont work. The call will be set up but no audio.
good luck with the rest. Like I said the Mitel just outputs the cdr's to the ports..
E
good luck with the rest. Like I said the Mitel just outputs the cdr's to the ports..
E
- Thread starter
- #8
The E2T comms error does not necessarily indicate a problem with the functionality.
I posted earlier that the E2T card requires a static address from DHCP. Not having a static address will sometimes generate the E2T comms error.
Is your system providing a static address?
There is an island of opportunity in the middle of every difficulty.
Miss that though, and you're pretty much doomed!
I posted earlier that the E2T card requires a static address from DHCP. Not having a static address will sometimes generate the E2T comms error.
Is your system providing a static address?
There is an island of opportunity in the middle of every difficulty.
Miss that though, and you're pretty much doomed!
Mitelpassion
IS-IT--Management
busster, I now understand why you don't have any issues. E2T stands for Ethernet (IP) To TDM. This is the component that converts traditional TDM to IP and vice versa.
Seeing that you don't have any IP devices on your network you wont need the E2T...
E
Seeing that you don't have any IP devices on your network you wont need the E2T...
E
- Thread starter
- #11
Mitelpassion
IS-IT--Management
if you want to get rid of the alarm you should give the E2T an IP. DHCP static makes no difference allthough giving it at static will provide you with some sort of control....
E
E
- Status
Similar threads
- Locked
- Question