Sip trunks to Tandberg VCS

[lhuffman]

I am attempting to connect via SIP to a TANDBERG VCS. The Tandberg is sending the request "OPTIONS" to ask what options the OXE v8.0.1 supports. Does the OXE support this request? Or is this evn my issue? Any comments? Below is a copy of the trace.

OPTIONS sip:10.10.100.10:5060;transport=tcp SIP/2.0

Via: SIP/2.0/TCP 10.10.101.52:5060;branch=z9hG4bK2603b0598b09ce9c231565ecb8aaa60b3853;rport

Call-ID: 33ea72d8db7fbd80@10.10.101.52

CSeq: 31601 OPTIONS

From: <sip:10.10.101.52>;tag=7913a86d58a95798

To: <sip:10.10.100.10:5060>

Max-Forwards: 0

User-Agent: TANDBERG/72 (X4.2)

Supported: com.tandberg.vcs.resourceusage

Content-Length: 0



-------------------------------------------------

1253919843 -> 21A [CRequest::CRequest] Creation of a request (RECEIVED FROM NETWORK)
1253919843 -> [CIOCom::receiveRequest] Received CRequest 21A ref=1
1253919843 -> [CRequest::respond] CResponse 21A ref=1
1253919843 -> 21A [CMessage::send] sip_sendMessage (10.10.101.52:5060)
1253919843 -> SEND MESSAGE TO NETWORK (10.10.101.52:5060 [TCP]) (BUFF LEN = 315)
----------------------utf8-----------------------
SIP/2.0 483 Too Many Hops

To: <sip:10.10.100.10:5060>;tag=ad9592f383934eb89f98fbdd794aaaff

From: <sip:10.10.101.52>;tag=7913a86d58a95798

Call-ID: 33ea72d8db7fbd80@10.10.101.52

CSeq: 31601 OPTIONS

Via: SIP/2.0/TCP 10.10.101.52:5060;branch=z9hG4bK2603b0598b09ce9c231565ecb8aaa60b3853;rport

Content-Length: 0



-------------------------------------------------
1253919843 -> ALARM: 21A [CMessage::send] sip_sendMessage FAILED => HSS ERROR Send failed
1253919843 -> [SIPReportAlarm] Unknow alarm type '4'
1253919843 -> 21A [~CResponse] resp(483) 33ea72d8db7fbd80@10.10.101.52 31601 OPTIONS
1253919843 -> 21A [~CRequest] req 33ea72d8db7fbd80@10.10.101.52 31601 OPTIONS
1253919846 -> main.trace.timer = 480mn
1253919874 -> RECEIVE MESSAGE FROM NETWORK (10.10.101.52:25000 [TCP])

[cavagnaro]

The problem is here:

Max-Forwards: 0

That comes from what I understand from your logs from Tandberg. This is telling that it will not handle any routing, just a straight route, any way to change this on Tandberg side?

[lhuffman]

I am waiting to hear from Tandberg. Am I correct in assuming the OXE cannot respond to this request?

[cavagnaro]

No, the problem is that Tandberg is saying:
I will go only with 0 reroutes, so it is like saying "I will stay only here and will not forward this call anywhere", were that anywhere is the OXE (Next hop), like in routing. So it should be at least one if OXE doesn't forward it to another GW...which in that case the forward will be 2, and so on...

[lhuffman]

Thank you. Most helpful.

[cavagnaro]

Let us know how to solve the issue if it happens to anyone else.

[lhuffman]

Absolutely!

[lhuffman]

Still waiting for resolution. It appears that OXE r8.0.1 patch 11 cannot answer the OPTIONS query from the Tandberg. Am upgrading to patch 31 and trying again.

[William084]

How did you go with the Alcatel toTandberg sip trunk. I appear to be having a similar issue?

[tgn]

Hello all,

i've the same issue here with VCS and OXE. OXE is in R9.0 (h1.301.36)...

any suggestions?

regards...