Merlin Messaging Not Disconnecting 1

[FordMan77]

Having an issue w/ a Merlin Messaging not disconnecting calls on 3 copper trunks. I have them set to LS-Disconnect YES in the switch, and the ports are rotary enabled (which shouldn't matter for this).

Verizon has disconnect set on their lines. If they test at the Demarc, the calls disconnect fine. Only when the calls reach the switch to they get stuck.

The issue is this: Someone calls site and gets the AA. They hang up before selecting any options and that port of the MM hangs until all ports get locked up and they reboot the switch. When this happens and all ports are locked up, callers just get a busy signal (as they should). It's like the MM doesn't know the caller hung up and keeps the line open.

Is there any settings in the MM that I can look at to resolve this?

 

[merlinman]

Nothing in the MM will do it.

Try changing the HOLD DISCONNECT to short and see if that does anything.

This may require more testing but not by Verizon.

If the above doesn't work, I can tell you another test you can make to see if you are or are not getting Forward Disconnect from the CO.

http://home.comcast.net/~merlinman

 

[ttech]

Did YOU personally test it at the d-marc, or are you taking verizon's word on it?

 

[FordMan77]

Did not test it personally, as it is 2 states away. Having to take Telco's word for it.

 

[FordMan77]

Ok merlinman, I changed the Hold Disconnect to short. No change there. I also changed the Reliable Disconnect to NO for these lines. Still nothing.

What other things might you have in mind to test?

 

[merlinman]

Where does this abandoned call wind up?

Is it in the AA then the General Mailbox?

If so, change the Message Length and Mailbox size for the General Mailbox to be smaller.

OR, you can tell Merlin Messaging to do a disconnect for the Dial Zero time out.

http://home.comcast.net/~merlinman

 

[Dexman]

I would have a difficult time taking the LEC at their word. Is there anyone at the site who is proficient enough that they can run some tests by connecting a basic telephone to each line an verifying that the LEC is actually generating a positive disconnect?

If it ain't broke, I haven't fixed it yet.

 

[FordMan77]

I noticed that when I tried to login to the VM and did not have the correct password enough times that when the Messaging hung up on me the line actually disconnected, as I called back on that same line.

I guessed the password the 2nd time around and got in. After some digging, I found that the dial 0/timeout for AA1 Daytime is set to ring calling group 770, which has 2 members. Below is a copy of that calling group...


Group # : 770 Group Type : AutoLogout
A Call Distribution Type : GROUP RING

A PryAnn No. EXT # LABEL Messaging Announcement
A 1 7176 1
A 2 7177
A 3 7178
A 4 7179
A 5 7180
A 6 7181
A 7 7182
A 8
A 9
A 10
A Secondary Announcement Ext # :
A Messaging Announcement # for Secondary Announcement:
A Time Between Delay Announcements: 0
A Repeat Secondary Announcement: No

A Message Waiting Station :

A Queue Control Limit: 99
A Calls_in_queue Threshold 1: 1
A Calls_in_queue Threshold 2: 1
A Calls_in_queue Threshold 3: 1
A External Alert ext # :
A Overflow Threshold (#) : 1
A Overflow Threshold (Time): 0
A Prompt Based Overflow Option: No
A Overflow to DGC group # :

A Group Coverage :

A Member No. EXT # LABEL
A 1 110 CASEYOP
A 2 124

It looks as though I need to change this group to LINEAR. With the calling group w/ the 2 members for the 0-out set to group ring, this will never cover to VM, which explains why I never get a mailbox, it just rings and rings until I hang up. It is also set to Auto Logout, which to me means that a call comes to the group, it rings both phones. If no one answers, then those 2 phones are logged out. Let me make these changes and I'll report back.

 

[FordMan77]

Alright, I've changed both groups to Linear ring, and changed the dial 0/timeout action to leave a message in the gen. mb. This all works correctly.

I set my reliable disconnect to ON again for these trunks, and changed the Hold timer back to long as it usually is.

Now when I call, I get the AA as usuall, then hang up without pressing anything. I timed it and while attempting to call the same number back, it took 1 min 30 sec. to get through on that line again. All others were busy signal. What I have also noticed is that when that line is still busy, and I call the 3rd number it rings through. This also tells me that they do not have this hunting from Telco, even though they say they do.

Back to telco for now.

 

[FordMan77]

Update- I changed the dial 0/timeout action to disconnect and tested. When I call and press 0 is disconnects my call and I am able to call it right back, so when the Messaging is set to disconnect it works, but when not programmed to do so, it hangs the line.

 

[Dexman]

That would be because you are forcing the Magix to drop the call. The problem is that the LEC doesn't appear to be sending a disconnect if the originating party hangs up first.

If it ain't broke, I haven't fixed it yet.

 

[merlinman]

That was my suspicion all along, but I made the suggestion of the Dial Zero time out to disconnect to prove it once and for all.

What DEXMAN says is absolutely correct, and the Service Provider is NOT PROVIDING a disconnect signal.

Back in my Tier-3 days at AT&T/Lucent/Avaya, I have had to "DEFINE" it for them more than once:

"A positive disconnect signal is a drop (or loss) of loop current for a period of time in the range of 50 to 250 milliseconds."

Once you explain that definition to them you can ask them point blank, "Are you providing such a signal?"

http://home.comcast.net/~merlinman

 

[merlinman]

I misstated the Time Values in my last post.

It should be somewhere between 250 to 1000 milliseconds, with 500 being the ideal.

http://home.comcast.net/~merlinman

 

[FordMan77]

Thank you all! I will push back to Telco to make them fix this.