OXO and LYNC 2013

[besacier]

@cavagnaro

OXO

[cavagnaro]

? Check the Message 403. The user agent is OXO, but the one who sends the 403 message is Lync...OXO may be replicating the message but Lync is warning you something there

[besacier]

Hi Guys

I've found what was the 403 error
In fact I have 2 lynch front end servers lyncfront1 and lyncfront2
and my sip trunk with the OXO is just between the OXO and lyncfront1
In the trace we can see that when lyncfront2 tries to send a sip request to the OXO , the OXO says forbidden

but all this does not help me because it still don't understand why I can reach my internal extensions from my Lync client with any problem and why I cannot dial external numbers, when I dial an external number I still have that 404 error

[Jtmurphy76]

@cavagnaro, did you resolve the Lync integration issue. I only manage to get communication from the Lync to the OXO, not from OXO to Lync via a private SIP trunk.
Change canonical dialling formats and allowing UDP to TCP, but still no joy. This is all with Rel 9.2.
next would be to test with Rel 10.1

[cavagnaro]

? Me? I never had this issue on fist place was helping the OP only. Or trying at least. On your case, same as others, check logs and follow Alcatel tested scenario.

[besacier]

Hi Guys

So here's some fresh news

it's simply impossible to link an OXO with Lync 2013 because Lync 2013 does not support SIP UDP at all

so what I did I added an asterisknow VM between my Lync 2013 and My OXO

so now I have

ISDN >> OXO >> SIP TPC/UDP >> Asterisknow >> SIP TCP >> Lync

So now I can:
- ring my lync client with an internal phone
-ring an internal phone with the lync client
-ring a speed dialing extension from the lync client

but I still can't ring an external number from the lync client
I have an error 404 not found

[cavagnaro]

Now makes sense to you why Alcatel docs state clearly to use an AudioCodes in the middle? Why do what provider says and tested? Right? All they want is complicate life.
For your 404 error, again, logs mister, you are sending some wrong data somewhere and 404 as a web page means, what? "Not Found". So no error, just check your logs

[pax]

I don’t think it is possible with R9.X. But I am running a direct SIP trunk between Lync 2013 and The OXE R11.1. The main key for getting it to work is:
Use TCP as transport type and Singel codec G711 as Type of negotiation on the external GW level.
Trunk connected to the External GW should be ISDN all countries as Q931 singal variant.

[besacier]

Ok Guys

Everything working except for the outgoing/external (call)

Here is a zip file with my OXO setup and the sip trace

Can you please have a look and tell me where the error is

the error should reside on the OXO side because everything else is working

Waiting for your advices

Cheers

Christian

[pax]

I again hope your weekend was good! When I read your thread I see a deferens between the case and the external case.

In the internal case the calling number is just the ext. (sip:236@10.70.0.242)

But in the external case that you display the calling number is (sip:+41215600229:ext=429@isl.ch;user=phone)

That mite very well confuses the OXE, and gives the sip respond showed in the logs. Try at the Lync side to manipulate the calling number at trunk level so you only sends the calling number like in the example for the internal number. Hint: ^\+41215600(\d{3});ext=\d{3}$
Also let domain be the same IP as you have in the allowed IP table in the OXE.