Sorry guys, but reaching out in desperation. I'm the AE (not a tech) with an unhappy customer.
TL;DR version. one extension (only) in a CAG disconnects after 32 seconds of a SIP call. Other four work normally.
Details.
Environment is CM R6.1, Session Manager, System Manager, Portwell ASBC. AT&T SIP Trunks, approx 100.
DID directed to a Virtual extension. This Virtual Extension goes to Coverage Answer Group 9.
Group 9 has only five (5) members. All with J179's, FW converted to H.323 and Aliased as 9611G.
Four of these members have no problem at all in answering calls.
If the fifth member (3288)answers, is disconnected after 32 seconds. (Note: 3288 was originally the only person on that team and no problems. Only after building and deploying the Coverage answer Group did this crop up)
Wireshark in front of SBC says we get ACK from AT&T on calls for the four extensions with no issues.
Wireshark report does NOT see ACK from AT&T if extension 3288 answers. So call is disconnected at 32 seconds. AT&T insists they are sending it though.
We added a sixth member for grins. Took 3288 out. works fine.
Put 3288 back in again and the sixth member disconnects at 32 seconds as well. but other four remain working.
Moved 3288 to #1 position in the group. Still disconnects.
Internal calls to this virtual extension test ok. no disconnects, as you might expect.
DID calls to 3288 work fine. no disconnect.
NOC technician has done a stare and compare on all phones. See's no differences between phones. And, we've groomed the naming convention for consistency. Didn't help.
And AT&T appears to have no interest in a joint troubleshooting session. We've shared the Wireshark results and they don't want to even see it.
if any ideas on where to look next, I'll pass it along to my team.
Thanks!
TL;DR version. one extension (only) in a CAG disconnects after 32 seconds of a SIP call. Other four work normally.
Details.
Environment is CM R6.1, Session Manager, System Manager, Portwell ASBC. AT&T SIP Trunks, approx 100.
DID directed to a Virtual extension. This Virtual Extension goes to Coverage Answer Group 9.
Group 9 has only five (5) members. All with J179's, FW converted to H.323 and Aliased as 9611G.
Four of these members have no problem at all in answering calls.
If the fifth member (3288)answers, is disconnected after 32 seconds. (Note: 3288 was originally the only person on that team and no problems. Only after building and deploying the Coverage answer Group did this crop up)
Wireshark in front of SBC says we get ACK from AT&T on calls for the four extensions with no issues.
Wireshark report does NOT see ACK from AT&T if extension 3288 answers. So call is disconnected at 32 seconds. AT&T insists they are sending it though.
We added a sixth member for grins. Took 3288 out. works fine.
Put 3288 back in again and the sixth member disconnects at 32 seconds as well. but other four remain working.
Moved 3288 to #1 position in the group. Still disconnects.
Internal calls to this virtual extension test ok. no disconnects, as you might expect.
DID calls to 3288 work fine. no disconnect.
NOC technician has done a stare and compare on all phones. See's no differences between phones. And, we've groomed the naming convention for consistency. Didn't help.
And AT&T appears to have no interest in a joint troubleshooting session. We've shared the Wireshark results and they don't want to even see it.
if any ideas on where to look next, I'll pass it along to my team.
Thanks!