I work for a software application developer whose solution is accessed through a telephony interface. Typically our server/telephony board gets connected to a customer PBX/IP-PBX.
I have some documentation on the MD110 and have picked through enough on-line and tech-board postings on the system to talk intelligently with the customer and get their inbound/outbound calls working.
They have structured their dial plan such that they see our directly connected ISDN-PRI trunk. Users dial an access code and route across this trunk to our server, we answer the call and begin call treatment.
We are not getting a clean disconnect. We seem to be passing ISDN Disconnect messages with cause code 16 [normal call clearing] to the MD110 okay but they are ignore that request.
I noticed a question on this bulletin board related to answer on an MD110 ISDN trunk and how parameters in the SIG Field of Route Category Initiate had to be programmed to recognize the appropriate answer signal.
I wonder if this same ROCAI field had to be programmed to recognize disconnects.
I have some documentation on the MD110 and have picked through enough on-line and tech-board postings on the system to talk intelligently with the customer and get their inbound/outbound calls working.
They have structured their dial plan such that they see our directly connected ISDN-PRI trunk. Users dial an access code and route across this trunk to our server, we answer the call and begin call treatment.
We are not getting a clean disconnect. We seem to be passing ISDN Disconnect messages with cause code 16 [normal call clearing] to the MD110 okay but they are ignore that request.
I noticed a question on this bulletin board related to answer on an MD110 ISDN trunk and how parameters in the SIG Field of Route Category Initiate had to be programmed to recognize the appropriate answer signal.
I wonder if this same ROCAI field had to be programmed to recognize disconnects.
