Interoute One siptrunks and Lync CU2 update is a no go for now. – #Lync #Interoute

Hi

Im having some problems with Interoute´s siptrunking service after I`we applied CU2 on my servers.

It might be my configuration or it might be something at the other end (which I think it is)

So if you rely on interoute one for your PSTN connection I would strongly suggest to wait with the CU2 patches on the mediation servers for a while.

I will update this post when I am 100% certain on where the problem is.

Update.

So I opened a case with Interoute and they did check that they send the OPTIONS and I also did some tracing myself and I can see it as seen below.

128 17:48:46 2011-04-29 254.7489520 Unavailable 196.149.141.112 195.81.247.212 SIP SIP:Request: OPTIONS sip:195.81.247.212 SIP/2.0 {SIP:23, TCP:22, IPv4:13}

130 17:48:46 2011-04-29 254.7886492 Unavailable 195.81.247.212 196.149.141.112 SIP SIP:Response: SIP/2.0 200 OK {SIP:23, TCP:22, IPv4:13}

So after some great help from some people from the mediation server team we found that
The FROM header in the 200OK responses to OPTIONS is wrong.

This is what Mediation Server sends:

From: ;epid=35D712543B;tag=427678421c

This is the answer:

From: ;tag=427678421c;epid=35D712543B


That’s why Mediation Server discards the answers from the other end.

To be continued!