Nomadic issue

Post Reply
User avatar
cavagnaro
Alcatel Unleashed Certified Guru
Alcatel Unleashed Certified Guru
Posts: 7013
Joined: 14 Sep 2005 19:45
Location: Brasil, Porto Alegre
Contact:

Nomadic issue

Post by cavagnaro »

Hi guys,
I'm facing a strange issue with nomadic:

I put my computer or any on nomadic mode, it works, virtual Z is reserved. I call my extension my PC rings but when I answer the other party keeps hearing a ring and call drops.
On tsa_maintenance I can see this:
Args : 3595 / -http_port:3695 / -PMS-monoproc:0 / -bdd-tnomad
18h18:51.841 result 1 . tempo 0
18h18:51.842 LocalLines::Etablish Nomadic Mode
18h18:51.842 Z state: 6097 : Free
18h18:51.842 Establish Nomadic Mode for client 4102
18h18:51.842 Request establish H323
18h18:51.842 Tempo wait alerting message for client 4102
18h18:51.842 Nomadic_tempor : 300 tempo_id = 8
18h18:51.842 Line::SetStateNomadic 6097 Init
18h18:52.110 4400 -> OTS : Z 6097 ringing
18h18:52.110 Tempo wait alerting message for client jcornejo
18h18:52.110 Nomadic_tempor : 300 tempo_id = 8
18h18:52.603 Client -> OTS : Z is ringing, cli = 4102 , ref_msg = 34
18h18:52.603 Ghost to hook-off 6097
18h18:52.603 Tempo wait connection message for client 4102
18h18:52.603 Nomadic_tempor : 200 tempo_id = 8
18h18:52.619 4400 -> OTS : Z 6097 established
18h18:52.620 Stop tempo nomad 6097
18h18:53.111 Error: 4 OTS_AG_CSTA 13 OBJ_NOT_FOUND evtcCrid 18068224 on ots 35
95
18h18:53.315 Client -> OTS : Z is ringing, cli = 4102 , ref_msg = 35
18h18:53.315 Line::SetStateNomadic 6097 Ringing
18h18:53.315 Nomadic_tempor : 300 tempo_id = 9
18h19:00.040 result 0 . tempo 1
18h19:00.102 result 0 . tempo 1
18h19:07.665 4400 -> OTS : Z 6097 releasing
18h19:07.665 Stop tempo nomad 6097
18h19:07.665 Request stop H323
18h19:07.668 SwitchNomad allowed for 5061
18h19:07.668 Line::SetStateNomadic 6097 Releasing
18h19:29.339 result 1 . tempo 0
18h19:29.339 LocalLines::Etablish Nomadic Mode
18h19:29.340 Z state: 6097 : Free
18h19:29.340 Establish Nomadic Mode for client 4102
18h19:29.340 Request establish H323
18h19:29.340 Tempo wait alerting message for client 4102
18h19:29.340 Nomadic_tempor : 300 tempo_id = 10
18h19:29.340 Line::SetStateNomadic 6097 Init
18h19:29.506 4400 -> OTS : Z 6097 ringing
18h19:29.506 Tempo wait alerting message for client jcornejo
18h19:29.506 Nomadic_tempor : 300 tempo_id = 10
18h19:30.270 Client -> OTS : Z is ringing, cli = 4102 , ref_msg = 36
18h19:30.270 Ghost to hook-off 6097
18h19:30.270 Tempo wait connection message for client 4102
18h19:30.270 Nomadic_tempor : 200 tempo_id = 10
18h19:30.286 4400 -> OTS : Z 6097 established
18h19:30.286 Stop tempo nomad 6097
18h19:30.675 Client -> OTS : Z is ringing, cli = 4102 , ref_msg = 37
18h19:30.675 Line::SetStateNomadic 6097 Ringing
18h19:30.675 Nomadic_tempor : 300 tempo_id = 11
18h19:31.106 Error: 4 OTS_AG_CSTA 13 OBJ_NOT_FOUND evtcCrid 18068224 on ots 35
95

18h19:41.835 result 0 . tempo 1
18h19:41.891 result 0 . tempo 1
18h19:45.364 4400 -> OTS : Z 6097 releasing
18h19:45.364 Stop tempo nomad 6097
18h19:45.364 Request stop H323
18h19:45.367 SwitchNomad allowed for 5061
18h19:45.367 Line::SetStateNomadic 6097 Releasing

[root@ebdics ~]# /opt/Alcatel-Lucent/OmniPCXTSA/tsa_maintenance
Usage: [hostname]
Trying connect: ebdics.ebdperu.com 3595

Connection with ebdics.ebdperu.com , port 3595 is OK

You can give arguments -xxx-yyy in command-line, forwarded to main_tsa!

Local commands:
>> filename nb_files size_file to record in local files

write set_client: nbe=


Press return?
0 p|r parameter : put(ex: 0 p -v) or remove(ex:0 r -tcsta)
-1[1=I 2=I+timout] StartTracesMsg -2(ido|*,op|*) AddMask -3 StopTracesMsg
-4 Threads -5 Timer -6 MailBox -7 RecMsg

18h28:05.070 MenuMsgStdin
I tried reloading all qmdcu from OTS but no luck...
IP Trunk is up
I can ping forward and backward
Routing is ok

Does anyone have a clue?

Thanks!
Ignorance is not the problem, the problem is the one who doesn't want to learn

OTUC/ICS ACFE/ACSE R3.0/4.0/5.0/6.0
Certified Genesys CIV 8.5
Certified Genesys Troubleshooting 8.5
Certified Genesys BEP 8.x
Genesys Developer
User avatar
cavagnaro
Alcatel Unleashed Certified Guru
Alcatel Unleashed Certified Guru
Posts: 7013
Joined: 14 Sep 2005 19:45
Location: Brasil, Porto Alegre
Contact:

Re: Nomadic issue

Post by cavagnaro »

Guys found this:

The events: “Error: 4 OTS_AG_CSTA 13 OBJ_NOT_FOUND" can be significant, except if "evtcCrid 0" is found behind. In this specific case it means CSTA events are generated on PBX for tracing purpose. There are actdbg with parameter “cstatrpi” or “challon”.

So on OXE I ran a actdbg and all traces are off...what is challon?? Can't find it...do you have any ideas on what they mean?

Thanks
Ignorance is not the problem, the problem is the one who doesn't want to learn

OTUC/ICS ACFE/ACSE R3.0/4.0/5.0/6.0
Certified Genesys CIV 8.5
Certified Genesys Troubleshooting 8.5
Certified Genesys BEP 8.x
Genesys Developer
Post Reply

Return to “OmniTouch 8400 Instant Communication Suite”