OXO and LYNC 2013
OXO and LYNC 2013
Hi Everyone
I've seen many subject about connecting the OXE to Lync via Direct SIP
is it possible with the OXO, does it work, do you have a guide ?
Cheers
Christian
I've seen many subject about connecting the OXE to Lync via Direct SIP
is it possible with the OXO, does it work, do you have a guide ?
Cheers
Christian
Re: OXO and LYNC 2013
Ok Guys
So here's some news of my experiment linking an OXO with Lync (Part 1)
What I did:
On the Lync side
I defined my oxo main cpu ip in the link topology as a PSTN gateway and a trunk I defined dial plans, voice policy, route PSTN usage and trunk configuration in the voice routing section of the link control panel
on the OXO side
in Voip parameter I assigned 2 channel for trunk. I did the setup for the trunk : I added the trunk to the internal numbering plan in order to have our phones able to call/reach lync clients then I configured the private numbering plan to be able to call our users from the lync client (I assume from what I've seen in the documentation) Then ARS (that's where everything becomes difficult, I don't really understand how it's working)
first able the trunk list so index 1 the main trunk and 2 the new sip trunk and the the ARS table : and to finish the ARS gateway parameters:
So here's some news of my experiment linking an OXO with Lync (Part 1)
What I did:
On the Lync side
I defined my oxo main cpu ip in the link topology as a PSTN gateway and a trunk I defined dial plans, voice policy, route PSTN usage and trunk configuration in the voice routing section of the link control panel
on the OXO side
in Voip parameter I assigned 2 channel for trunk. I did the setup for the trunk : I added the trunk to the internal numbering plan in order to have our phones able to call/reach lync clients then I configured the private numbering plan to be able to call our users from the lync client (I assume from what I've seen in the documentation) Then ARS (that's where everything becomes difficult, I don't really understand how it's working)
first able the trunk list so index 1 the main trunk and 2 the new sip trunk and the the ARS table : and to finish the ARS gateway parameters:
You do not have the required permissions to view the files attached to this post.
Re: OXO and LYNC 2013
My experiments (Part 2)
Results:
ok so at the moment:
I can call internal users from my lync client by dialing their internal extension (eg. 229) everything is fine , audio quality is good I can even pause and resume the call , transfer is not working but I'll troubleshoot that later
I can't call external numbers , according to the packet capture I've done from the pbx the pbx is receiving the external number but is answering Unallocated number , it's like the OXO is looking is in internal numbering plan and didn't find the number instead of using the main trunk to reach it , I don't know what to do if someone can provide me some help my internal users can't call the lync client: on a phone i'm dialing *500 to get the line then I dial the extension (eg. 229) and nothing happens
so let's do another sip trace and what what my surprise the oxo send sip request to lync but with the UDP tranport mode , so the lync mediation server does not look at it Question:
What did I missed , why am I not able to dial external numbers from my lync client ???
why is the oxo receiving and accepting sip request in tcp transport mode and why is it sending request to my lync server un UDP mode, is there a way to change this ???
I'm waiting for your answers
Cheers
Christian
Results:
ok so at the moment:
I can call internal users from my lync client by dialing their internal extension (eg. 229) everything is fine , audio quality is good I can even pause and resume the call , transfer is not working but I'll troubleshoot that later
I can't call external numbers , according to the packet capture I've done from the pbx the pbx is receiving the external number but is answering Unallocated number , it's like the OXO is looking is in internal numbering plan and didn't find the number instead of using the main trunk to reach it , I don't know what to do if someone can provide me some help my internal users can't call the lync client: on a phone i'm dialing *500 to get the line then I dial the extension (eg. 229) and nothing happens
so let's do another sip trace and what what my surprise the oxo send sip request to lync but with the UDP tranport mode , so the lync mediation server does not look at it Question:
What did I missed , why am I not able to dial external numbers from my lync client ???
why is the oxo receiving and accepting sip request in tcp transport mode and why is it sending request to my lync server un UDP mode, is there a way to change this ???
I'm waiting for your answers
Cheers
Christian
You do not have the required permissions to view the files attached to this post.
Re: OXO and LYNC 2013
Hi for long distance call use canonical format -oxo does it understand the +
for calling lync users please put whole trace
for calling lync users please put whole trace
Re: OXO and LYNC 2013
Hi Haroun
Thx for your answer
For the Lync clients trying to call an external number
I'm using the canonical format in the trace you can see sip:+33607599239, I also tried to use 0 instead of the + : sip:0033607599239 but it not working either
I believe I missed something with my ARS setup but what , I don't know
for the internal users trying to reach the Lync clients
here's the full trace as you can see there the Oxo retries several times but there's no answer from the Lync server because the Oxo is using the UDP transport mode when Lync only listen to the TCP transport mode
Thx for your answer
For the Lync clients trying to call an external number
I'm using the canonical format in the trace you can see sip:+33607599239, I also tried to use 0 instead of the + : sip:0033607599239 but it not working either
I believe I missed something with my ARS setup but what , I don't know
for the internal users trying to reach the Lync clients
here's the full trace as you can see there the Oxo retries several times but there's no answer from the Lync server because the Oxo is using the UDP transport mode when Lync only listen to the TCP transport mode
You do not have the required permissions to view the files attached to this post.
- tot3nkopf
- Alcatel Unleashed Certified Guru
- Posts: 4058
- Joined: 02 Feb 2006 10:41
- Location: Germany & Romania
- Contact:
Re: OXO and LYNC 2013
Your sip trunk is declared as public. So your seizure (0) from Lync will be analyzed in the public numbering plan not in the private.
Anyway I do not see the external seizing prefix in the private either.
Related post:
viewtopic.php?f=227&t=22692&hilit=asterisk+tot3nkopf
Anyway I do not see the external seizing prefix in the private either.
Related post:
viewtopic.php?f=227&t=22692&hilit=asterisk+tot3nkopf
Re: OXO and LYNC 2013
for internal call you got
SIP/2.0 403 Forbidden
Allow: INVITE, ACK, CANCEL, BYE, OPTIONS, PRACK, REFER, NOTIFY, UPDATE
User-Agent: OXO920/067.001 GW_920/078.001
Reason: Q.850;text=" Incoming calls barred within CUG";cause=55
To: <sip:10.70.0.242>;tag=3f7ba277542091ae359a864e1e75d6b1
From: <sip:lyncfront2.isl.ch:5060;transport=Tcp;ms-opaque=a07b37a511d1458d>;tag=7598e1464b;epid=FFD855A72E
Call-ID: 1f4eb473fc224e47a68db6331ecc5e9b
CSeq: 10376 OPTIONS
Via: SIP/2.0/TCP 10.100.0.9:53435;branch=z9hG4bKc4fad714
Content-Length: 0
calls are them allowed from oxo to lync
SIP/2.0 403 Forbidden
Allow: INVITE, ACK, CANCEL, BYE, OPTIONS, PRACK, REFER, NOTIFY, UPDATE
User-Agent: OXO920/067.001 GW_920/078.001
Reason: Q.850;text=" Incoming calls barred within CUG";cause=55
To: <sip:10.70.0.242>;tag=3f7ba277542091ae359a864e1e75d6b1
From: <sip:lyncfront2.isl.ch:5060;transport=Tcp;ms-opaque=a07b37a511d1458d>;tag=7598e1464b;epid=FFD855A72E
Call-ID: 1f4eb473fc224e47a68db6331ecc5e9b
CSeq: 10376 OPTIONS
Via: SIP/2.0/TCP 10.100.0.9:53435;branch=z9hG4bKc4fad714
Content-Length: 0
calls are them allowed from oxo to lync
Re: OXO and LYNC 2013
Hi tot3nkopftot3nkopf wrote:Your sip trunk is declared as public. So your seizure (0) from Lync will be analyzed in the public numbering plan not in the private.
Anyway I do not see the external seizing prefix in the private either.
Related post:
viewtopic.php?f=227&t=22692&hilit=asterisk+tot3nkopf
Thx for your answer
You said that I declared my sip trunk as public but as far as I can seen in the screenshot I posted public is not checked
How do you setup the seizure for the external prefix I looked at the link but I haven't found ?
Re: OXO and LYNC 2013
Hi Harounharoun wrote:for internal call you got
SIP/2.0 403 Forbidden
Allow: INVITE, ACK, CANCEL, BYE, OPTIONS, PRACK, REFER, NOTIFY, UPDATE
User-Agent: OXO920/067.001 GW_920/078.001
Reason: Q.850;text=" Incoming calls barred within CUG";cause=55
To: <sip:10.70.0.242>;tag=3f7ba277542091ae359a864e1e75d6b1
From: <sip:lyncfront2.isl.ch:5060;transport=Tcp;ms-opaque=a07b37a511d1458d>;tag=7598e1464b;epid=FFD855A72E
Call-ID: 1f4eb473fc224e47a68db6331ecc5e9b
CSeq: 10376 OPTIONS
Via: SIP/2.0/TCP 10.100.0.9:53435;branch=z9hG4bKc4fad714
Content-Length: 0
calls are them allowed from oxo to lync
On the Lync side I allowed everything coming from the OXO ip , but how can I do that on the OXO side ???