Unity Connection 15 – Not responding to SIP Options from TIMG

[Bill]

We upgraded Unity Connection from version 12.5.1.17900-31 to 15.0.1.11900-14 using the Data Export method.
Everything seemed to go without issue, but it broke the connection to a couple TIMG’s.
I know the TIMG’s are end of life/support.
The issue is that Unity 15 is not responding to SIP Options from the TIMG’s.
Which works on ver 12.5.
I do see the TIMG’s responding to SIP Options from Unity, but not the other way.
This causes the TIMG to think Unity is offline.
Wondering if anyone has any thoughts as to why Unity would stop responding to SIP Options from the TIMG.
And maybe a possible workaround.
The TIMG’s are running firmware version 6.0.SU10.0.003.
The connection is SIP over UDP 5060.
Thanks

[Maren Mahoney]

Does CUC simply not respond at all to the Options PING from the TIMG, or does it respond with an error message?

How do the messages compare - from a headers/content/format standpoint - for the messages sent by CUC and the messages sent by the TIMG? If they are different, what is different? Can you post an example of an Options PING sent by CUC and another sent by the TIMG?

Maren

[Bill]

Maren, Thanks for the reply.
CUC 15 does not respond at all to the SIP options from the TIMG.
The only thing I thought looked unusual is the Option message has anonymous as the User portion of the message.
I think it is typically blank, but I believe a User is ok. 
I'm trying to upload a couple Wireshark files, but the forum won't let me.
I'll see if I can get them in a different format.
Thanks
PS - Does anyone know how I can upload a Wireshark file ?
I might try a Word doc with Screen shots.

[Bill]

I've attached a couple Word docs with screen shots from Wireshark.
I blocked out the Public IP info.
.117 is Unity Connection, .93 is the TIMG

[Maren Mahoney]

I don't see anything amiss. And I am coming up empty on a bug or change in process for CUC 15. I think the next thing we'd need to do is see if CUC is actually receiving the Options PING and, if so, how it is processing the message.

Gather the MiuSIP and MiuSIPStack microtraces (I think those are the ones we want. I'm coming up empty in the OS-level traces.) If I'm right, they should show the SIP message exchange. You'd for sure see the outbound-from-CUC-to-TIMG ones. If so, you can look to see if CUC is receiving the ones from the TIMG and what it's doing with them.

If you don't see the outbound-from-CUC messages, then we have the wrong traces and we'll have to do more research on the right ones. I don't suppose you have TAC access for this system, do you? If so, they should be able to tell you which trace file would contain these sorts of messages.

Maren

[Bill]

Thank you Maren, for looking into this.
I'm sure Unity is receiving the messages. That's where I got the packet captures.
Using utils network capture then dumping to a file.

We did open a tac case and sent them some macro/micro traces. 
They pushed back on us when we said it was a TIMG.
They said they won't support it.  But the issue seems to be Unity.

I'll review the traces too.
Unfortunately the ver 15 Unity is offline right now, as we had to revert back to the 12.5 servers.
But I do have traces form when it was up.
Thanks

[Bill]

We did collect micro traces went the issue was happening.

Reviewing them I can see Unity is receiving the Options, but not responding.
I see other Options with responses to/from CUCM.

At this point, looks like we are going to pursue a different path.
Possibly replace the TIMG with a QSIG trunks.
I don't think I will have any more updates on this issue.
Thanks for the input.