MyTeamWork Confrence call

Post Reply
lamhotPS

MyTeamWork Confrence call

Post by lamhotPS »

Hi All,

i already set up MyTeamWork Server 6.0 with OXE 9.0,problem is when the leader try to do confrence call which first ringing should the leader's SIP phone ( using eye beam ) but it's not because another phone is ringing ( other phone set ).
can anyone help,please?

thank's before.
Top
lamhotPS

Post by lamhotPS »

Any help?
Top
cavagnaro

Post by cavagnaro »

logs, please post logs...
Top
lamhotPS

Post by lamhotPS »

Hi Cav,
thank you..


Tue Feb 9 11:13:12 WIT 2010

+-----------------------------------------------------------------------+
| SIP Gateway |
+-----------------------------------------------------------------------+
Machin name : node000001
IP Address : 10.88.88.5

Subnetwork number : 15
SIP Trunk Group : 1

DNS Informations :
DNS local domain name :


+-----------------------------------------------------------------------+
| Trusted IP Address List |
+-----------------------------------------------------------------------+
Trusted IP Address 1 : 10.88.88.7


+-----------------------------------------------------------------------+
| Quaranted IP Address List |
+-----------------------------------------------------------------------+
motortrace (v5.2.0) verbosity = 0037b524
sipmotor trace-level set c (data dump).

Proxy parameters.
=================
initial_timeout 500
timer_t2 4000
recursion 0
min_auth_method 2 NONE=0 DIGEST=2
auth_realm 10.88.88.5
sipConnectionDuration 5000 not used
onlyAuthIncomingCalls 0
quarantine and trusted addresses:
nb_msg_by_period 25
period 3
framework_quarantine_period 1800

Gateway parameters.
===================
url_install 10.88.88.5
url_gw
url_hostname node000001
num_ss_reseau 15
num_faisc 1
proxy_address not used
DNS_localDomName
DNS_type 0 dnsa=0, dnssrv=1
DNS_primaire Unused
DNS_secondaire Unused
prack_required 0
out_proxy 0 AUCUN=0 INTEGRE=1 EXTERNE=2
proxy_port 5060
proxy_transport 1 TCP=0 UDP=1
sipSubsMinDuration 1800
sipSubsMaxDuration 86400
sipSessionTimer 1800
sipMinSessionTimer 900
SessionTimerMethod 0 re-invite=0, update=1
sipCac 0
SDP_in_180 1
sip_info_enable 0
payload 97
seplos 1

Registrar parameters.
=====================
declared_sets 0
min_expiry_date 1800
max_expiry_date 86400

CPU address.
============
physical local 10.88.88.5
physical twin
role Main 10.88.88.5

Licenses parameter.
=====================
nb max licences 70
Top
lamhotPS

Post by lamhotPS »

10/02/10 14:29:24
10/02/10 14:29:43 000001I|---/--/-/---|=4:2199=A4400 Version : R9.0-h1.301-24-ii
-c80s1
10/02/10 14:29:53 000001I|---/--/-/---|=2:4351=Incoherent data: appli INITREM ta
ble ENTITY cause 0 info -1 -1 -1
10/02/10 14:29:53 000001I|---/--/-/---|=2:4351=Incoherent data: appli INITREM ta
ble ENTITY cause 1 info -1 -1 -1
10/02/10 14:29:53 000001I|---/--/-/---|=2:4351=Incoherent data: appli INITREM ta
ble ENTITY cause 2 info -1 -1 -1
10/02/10 14:31:34 000001I|---/--/-/---|=2:1542=Partition 6 is 79 per cent full (
resource 2).
10/02/10 14:31:35 000001M|---/--/-/---|=5:2009=Initialisation CPU role MAIN
10/02/10 14:31:35 000001M|---/--/-/---|=5:2019=UA_FICTIF coupler commissioning
10/02/10 14:31:35 000001M|---/--/-/---|=5:2019=Z coupler commissioning
10/02/10 14:31:35 000001M|---/--/-/---|=5:1367=DECT network initialization
10/02/10 14:31:35 000001M|---/--/-/---|=5:5904=Remote extension network initiali
zation
10/02/10 14:31:35 000001M|---/--/-/---|=4:0425=PRS related activity : Interface
handler started
10/02/10 14:31:35 000001M|019/01/-/---|=5:2019=INTIPA coupler commissioning
10/02/10 14:31:48 000001M|002/00/-/---|=5:0409=The inter-ACT link over IP from (
19 1) is up
10/02/10 14:31:48 000001M|002/00/-/---|=0:5857=GD/GA/INTIP/RGD: reason of reboot
21
10/02/10 14:31:48 000001M|002/00/-/---|=2:5865=GD: Delivery file checking failed
(binmg) 1
10/02/10 14:31:48 000001M|002/00/-/---|=0:5859=MG/RGD: download status 1
10/02/10 14:32:05 000001M|002/01/-/---|=4:0740=Beginning of an INT/IP downloadin
g @:00.80.9f.83.95.e0 (binmg)
10/02/10 14:32:05 000001M|002/01/-/---|=5:0741=End of downloading of an INT/IP b
oard @:00.80.9f.83.95.e0 (binmg)
10/02/10 14:32:07 000001M|002/01/-/---|=4:0740=Beginning of an INT/IP downloadin
g @:00.80.9f.83.95.e0 (binmg)
10/02/10 14:32:07 000001M|002/01/-/---|=5:0741=End of downloading of an INT/IP b
oard @:00.80.9f.83.95.e0 (binmg)
10/02/10 14:32:09 000001M|001/00/-/---|=4:2615=Voice Guide channel lack for VG N
o 5
10/02/10 14:32:17 000001M|---/--/-/---|=4:4017=CSTA server : new creation 1 10.0
.2.74
10/02/10 14:32:18 000001M|002/00/-/---|=5:2019=GD coupler commissioning
10/02/10 14:32:19 000001M|---/--/-/---|=4:4017=CSTA server : new creation 2 10.8
8.88.6
10/02/10 14:32:23 000001M|000/00/-/---|=5:5800=1 SIP trunk group put into servic
e
10/02/10 14:32:33 000001M|002/01/-/---|=0:5857=GD/GA/INTIP/RGD: reason of reboot
2
10/02/10 14:32:33 000001M|002/27/-/---|=4:2491=GPA(2,27) virtual coupler commiss
ioning of the associated coupler GD(2,0)
10/02/10 14:32:53 000001M|---/--/-/---|=2:1462=V24:45: chanel configuration, ope
ration 1, error 5
10/02/10 14:33:04 000001M|002/01/-/---|=5:2019=GA coupler commissioning
10/02/10 14:33:14 000001M|002/09/-/---|=4:2491=GPA(2,9) virtual coupler commissi
oning of the associated coupler GA(2,1)
10/02/10 14:33:31 000001M|002/03/0/000|=4:2113=T2 lapD not established still try
ing
10/02/10 14:33:31 000001M|002/06/0/000|=4:2113=T2 lapD not established still try
ing
10/02/10 14:33:31 000001M|002/04/0/000|=4:2113=T2 lapD not established still try
ing
10/02/10 14:33:37 000001M|---/--/-/---|=3:1125=external alarm : "mtcl login"
10/02/10 14:33:41 000001M|002/03/0/000|=5:2102=T2 access back to normal
10/02/10 14:33:41 000001M|002/03/0/000|=4:2113=T2 lapD not established still try
ing
10/02/10 14:33:41 000001M|002/04/0/000|=5:2102=T2 access back to normal
10/02/10 14:33:41 000001M|002/04/0/000|=4:2113=T2 lapD not established still try
ing
10/02/10 14:33:41 000001M|002/03/0/000|=5:0311=T2 Dlap Established
10/02/10 14:33:41 000001M|002/06/0/000|=5:2102=T2 access back to normal
10/02/10 14:33:41 000001M|002/06/0/000|=4:2113=T2 lapD not established still try
ing
10/02/10 14:33:41 000001M|002/04/0/000|=5:0311=T2 Dlap Established
10/02/10 14:33:42 000001M|002/06/0/000|=5:0311=T2 Dlap Established
10/02/10 14:33:43 000001M|---/--/-/---|=2:1462=V24:46: chanel configuration, ope
ration 1, error 5
10/02/10 14:34:01 000001M|002/03/-/---|=5:2019=PRA coupler commissioning
10/02/10 14:34:01 000001M|002/06/-/---|=5:2019=PRA coupler commissioning
10/02/10 14:34:01 000001M|002/04/-/---|=5:2019=PRA coupler commissioning
10/02/10 14:34:18 000001M|002/07/-/---|=2:2457=PRA coupler (2,7) not initalized
yet
10/02/10 14:34:34 000001M|---/--/-/---|=2:1462=V24:47: chanel configuration, ope
ration 1, error 5
10/02/10 14:35:04 000001M|000/06/-/---|=5:2169=Main CPU initialization completed
10/02/10 14:35:24 000001M|---/--/-/---|=2:1462=V24:48: chanel configuration, ope
ration 1, error 5
10/02/10 14:35:45 000001M|---/--/-/---|=2:5815=Major failure in SIP component
10/02/10 14:35:45 000001M|---/--/-/---|=3:5816=Minor failure in SIP component
10/02/10 14:35:46 000001M|---/--/-/---|=2:5815=Major failure in SIP component
10/02/10 14:35:46 000001M|---/--/-/---|=3:5816=Minor failure in SIP component
10/02/10 14:35:47 000001M|---/--/-/---|=2:5815=Major failure in SIP component
10/02/10 14:35:47 000001M|---/--/-/---|=3:5816=Minor failure in SIP component
10/02/10 14:35:49 000001M|---/--/-/---|=2:5815=Major failure in SIP component
10/02/10 14:35:49 000001M|---/--/-/---|=3:5816=Minor failure in SIP component
10/02/10 14:35:53 000001M|---/--/-/---|=2:5815=Major failure in SIP component
10/02/10 14:35:53 000001M|---/--/-/---|=3:5816=Minor failure in SIP component
10/02/10 14:35:57 000001M|---/--/-/---|=2:5815=Major failure in SIP component
10/02/10 14:35:57 000001M|---/--/-/---|=3:5816=Minor failure in SIP component
10/02/10 14:36:01 000001M|---/--/-/---|=2:5815=Major failure in SIP component
10/02/10 14:36:01 000001M|---/--/-/---|=3:5816=Minor failure in SIP component
10/02/10 14:36:05 000001M|---/--/-/---|=2:5815=Major failure in SIP component
10/02/10 14:36:05 000001M|---/--/-/---|=3:5816=Minor failure in SIP component
10/02/10 14:36:09 000001M|---/--/-/---|=2:5815=Major failure in SIP component
10/02/10 14:36:09 000001M|---/--/-/---|=3:5816=Minor failure in SIP component
10/02/10 14:36:13 000001M|---/--/-/---|=2:5815=Major failure in SIP component
10/02/10 14:36:13 000001M|---/--/-/---|=3:5816=Minor failure in SIP component
10/02/10 14:36:29 000001M|019/00/0/001|=3:1307=MCDU in distri tab entity 0, col
Night , line 4 incorrect or missing
10/02/10 14:36:59 000001M|019/00/0/001|=3:1307=MCDU in distri tab entity 0, col
Night , line 4 incorrect or missing
10/02/10 14:50:02 000001M|---/--/-/---|=3:1125=external alarm : "mtcl login"
10/02/10 14:52:18 000001M|---/--/-/---|=4:4018=CSTA server : 1 connection closed
10/02/10 14:54:03 000001M|000/00/-/---|=5:5800=1 SIP trunk group put into servic
e
10/02/10 15:18:04 000001M|---/--/-/---|=2:5815=Major failure in SIP component
10/02/10 15:31:41 000001M|---/--/-/---|=2:1542=Partition 6 is 79 per cent full (
resource 2).
10/02/10 15:42:04 000001M|---/--/-/---|=2:5815=Major failure in SIP component
10/02/10 16:06:04 000001M|---/--/-/---|=2:5815=Major failure in SIP component
10/02/10 16:07:40 000001M|---/--/-/---|=3:1125=external alarm : "mtcl login"
Top
cavagnaro

Post by cavagnaro »

I meant the SIP logs of the call you describe. Please do a
sipmotor=3
traced

and indicate the desired scenario and what you get.

Also please post a screenshot of the configuration of the phones for that user under TW admin page.
Top
lamhotPS

Post by lamhotPS »

cavagnaro wrote:I meant the SIP logs of the call you describe. Please do a
sipmotor=3
traced

and indicate the desired scenario and what you get.

Also please post a screenshot of the configuration of the phones for that user under TW admin page.

Hi Cav,

PBX Ip : 10.88.88.5
Mytw Server ip : 10.88.88.7

and here's SIP trace i attach with.
You do not have the required permissions to view the files attached to this post.
Top
cavagnaro

Post by cavagnaro »

I see no INVITE message, please run the traces before doing the call and indicate the expected scenario and what you get (indicate phone numbers please)
Also the screenshot of you TW user interface and the DAS rules of your TW
Top
banfield

Post by banfield »

A lot of BYE hehe
Top
alcatec

Post by alcatec »

What does your SIP Proxy setup look like in My Teamwork?
Top
Post Reply

Return to “My Teamwork (ex-eDial)”