Problems connecting to OXE

charpdy · Post by **charpdy** » 10 May 2010 13:44

What happens in the SIP trace when you look from the teamwork server ?
Monitoring/SIP logs

Have you managed the SIP proxy in Teamwork ?
Can you call the conferencing number from OXE ?

Just my 2€ (ya i know, inflation in EU is crazy)

alex · Post by **alex** » 11 May 2010 02:23

RobertBreu wrote: the trace on oxe is empty...nothing!

Looks like a SIP proxy in MTW's configuration is wrong. Where MTW is sending INVITE's when calling OXE's extension?
You can check MTW's SIP call traces in Admin menu "Monitoring/SIP logs".
When the configuration is OK there must be a string like that

INVITE sip:<OXE_extension>@<OXE_address> SIP/2.0

RobertBreu · Post by **RobertBreu** » 11 May 2010 14:46

Hi,

i have just checked the sip-logs...for me it looks like that the invite message from the teamworker-server is wrong, her an example:

192.168.92.204 = OXE
192.168.92.208 = MTW

2010-05-11 20:21:44.765951
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 192.168.92.208:5060;branch=z9hG4bK132233142;received=192.168.92.204:5060
Call-ID: 963602151@192.168.92.208
CSeq: 1 INVITE
From: "robert.breu" <sip:robert.breu@call-data.de>;tag=3495733440132233140
To: sip:+@192.168.92.204
Content-Length: 0

2010-05-11 20:21:44.817164
SIP/2.0 404 Not Found
Via: SIP/2.0/UDP 192.168.92.208:5060;branch=z9hG4bK132233142;received=192.168.92.204:5060
Call-ID: 963602151@192.168.92.208
CSeq: 1 INVITE
From: "robert.breu" <sip:robert.breu@call-data.de>;tag=3495733440132233140
To: <sip:+@192.168.92.204>;tag=8e64ccbe5644ece51ee248d2cb00b6af
User-Agent: OmniPCX Enterprise R9.1 i1.605.14
Allow: INVITE, ACK, CANCEL, BYE, PRACK, NOTIFY, REFER, SUBSCRIBE, OPTIONS, UPDATE
Content-Length: 0

2010-05-11 20:21:44.817608
ACK sip:+@192.168.92.204 SIP/2.0
Via: SIP/2.0/UDP 192.168.92.208:5060;branch=z9hG4bK132233142
Call-ID: 963602151@192.168.92.208
CSeq: 1 ACK
From: "robert.breu" <sip:robert.breu@call-data.de>;tag=3495733440132233140
To: <sip:+@192.168.92.204>;tag=8e64ccbe5644ece51ee248d2cb00b6af
User-Agent: Alcatel-Lucent 8460 ACS 8.1.0b5031
Max-Forwards: 70
Content-Length: 0

I want to dial extension 22 but i think the teamworkserver just dials + ?? (I have marked the parts that maybe wrong)
Is this an issue with these DAS Rules??
The trace on the oxe shows the same!

From the oxe i can't dial to the teamworkserver. When i dial the number of the external voice mail to reach the MTW-Server i get a busy-tone (in my example i dial the extension 548). Do i have to set the extension (548) somewhere in the teamwork-server to reach it?

Thanks a lot for your help

alex · Post by **alex** » 12 May 2010 03:01

RobertBreu wrote:Is this an issue with these DAS Rules??

Sure. Do you have a DAS rule for extension calling?
Check this post on old forum basic DAS rules thanks to cavagnaro.

RobertBreu · Post by **RobertBreu** » 12 May 2010 11:32

Hi,

ok i have tried some DAS-Rules and now i can dial to extensions on the oxe. But what do i have to configure when i want to dial from oxe to mtw? I have tried to create an external voicemail system but this doesn't work? What do i have to configure on the MTW?

cavagnaro · Post by **cavagnaro** » 12 May 2010 13:28

Please follow the installation guide, it is explained all in there..

alex · Post by **alex** » 13 May 2010 02:36

Actually, cav is right. If you open "My Teamwork Site preparation guide", chapter 9, you have all the instructions how to connect MTW and OXE. I see no sense in retyping it here.

chris2109 · Post by **chris2109** » 26 May 2010 15:26

yep...it seems that you´ve not setup the registration in the teamwork platform under configuration / SIP proxies...here you must declare the SIP User Name...also it is necessary to configure the External Voice Mail in the OXE...

banfield · Post by **banfield** » 28 May 2010 18:55

RobertBreu please add me on msn messenger daniel_banfield@hotmail.com i show you have to do the configuraton in OXE and TWK. BR Daniel