4068 or 4028 couldn't call conference center

Post Reply
Sam2009
Member
Posts: 149
Joined: 14 Jan 2009 02:25

4068 or 4028 couldn't call conference center

Post by Sam2009 » 12 Feb 2013 07:42

hi
i have MyTeam work R 8.5.0b6114 with OXR R10 ( with IP Touch 4018 + 4028 + 4068 sets)
i use it for audio conferernce.
i can call Conference center (Dir= 3015) from any internal 4018 set and from external lines. :)
But NOT form 4028 or 4068 sets :(
when i restart MTW server , 4028 & 4068 can call conference center for sometime (about 30 min) then it fails to make calls anymore.

could anyone help me

User avatar
alex
Senior Member
Posts: 1328
Joined: 06 Jul 2004 07:27
Location: Russia
Contact:

Re: 4068 or 4028 couldn't call conference center

Post by alex » 13 Feb 2013 01:01

1. Get a SIP trace of successful 4018's conference call
2. Get a SIP trace of unsuccessful 4068's call
3. Compare them and find out the cause
4. ????
5. PROFIT!
I mean you can get an idea what's wrong with 4068's call by comparing two traces. :)
If it looks like a duck, swims like a duck, and quacks like a duck, then it probably is a duck.

Sam2009
Member
Posts: 149
Joined: 14 Jan 2009 02:25

Re: 4068 or 4028 couldn't call conference center

Post by Sam2009 » 27 Aug 2013 05:35

Hi
i get SIP trace for failed call using 4028 & successful call using 4018 , By comparing i didn't find any things.
please advise me.

kindly find these log:

Log for call from internal set 4028 : 3172 call 3015 via AA , call failed
SIP messages from the following logs
/var/log/tnslog/tp240dvr.log-2013-08-21-00-00
/var/log/tnslog/tp240dvr.log
2013-08-21 12:57:35.995207
INVITE sip:3015@10.234.17.38;user=phone SIP/2.0
Via: SIP/2.0/UDP 10.234.24.10;branch=z9hG4bK607197cee5d070b5b0e7f4033b834330;received=10.234.24.10:5060
Call-ID: 01cbcee445a522cbd645fd32f0d0ff0d@10.234.24.10
CSeq: 125137642 INVITE
From: "IT System En" <sip:3172@10.234.24.10;user=phone>;tag=abaa173d720c63b72b43af3506275da5
To: <sip:3015@10.234.17.38;user=phone>
Contact: <sip:3172@10.234.24.10;transport=UDP>
User-Agent: OmniPCX Enterprise R10.0 j1.410.45
Accept-Language: en
Allow: INVITE, ACK, CANCEL, BYE, PRACK, NOTIFY, REFER, SUBSCRIBE, OPTIONS, UPDATE, INFO
Supported: histinfo,replaces,timer,path
Session-Expires: 1800;refresher=uac
Min-SE: 900
P-Alcatel-CSBU: categparty=internal;call_condition=localdirect
Max-Forwards: 70
Content-Length: 265
Content-type: application/sdp

v=0
o=OXE 1377075345 1377075345 IN IP4 10.234.24.10
s=abs
c=IN IP4 10.234.25.49
t=0 0
m=audio 32514 RTP/AVP 8 4 97
a=sendrecv
a=rtpmap:8 PCMA/8000
a=ptime:20
a=maxptime:30
a=rtpmap:4 G723/8000
a=ptime:30
a=maxptime:30
a=rtpmap:97 telephone-event/8000

2013-08-21 12:57:35.995743
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 10.234.24.10;branch=z9hG4bK607197cee5d070b5b0e7f4033b834330
Call-ID: 01cbcee445a522cbd645fd32f0d0ff0d@10.234.24.10
CSeq: 125137642 INVITE
From: "IT System En" <sip:3172@10.234.24.10;user=phone>;tag=abaa173d720c63b72b43af3506275da5
To: <sip:3015@10.234.17.38;user=phone>
Contact: <sip:3015@10.234.17.38:5060>
User-Agent: Alcatel-Lucent 8460 ACS 8.5.0b6114
Allow: ACK,BYE,CANCEL,INFO,REFER,MESSAGE,INVITE,NOTIFY
Accept-Language: en
Content-Length: 0


2013-08-21 12:57:35.996174
SIP/2.0 200 OK
Via: SIP/2.0/UDP 10.234.24.10;branch=z9hG4bK607197cee5d070b5b0e7f4033b834330
Call-ID: 01cbcee445a522cbd645fd32f0d0ff0d@10.234.24.10
CSeq: 125137642 INVITE
From: "IT System En" <sip:3172@10.234.24.10;user=phone>;tag=abaa173d720c63b72b43af3506275da5
To: <sip:3015@10.234.17.38;user=phone>;tag=638708234241521418
Contact: <sip:3015@10.234.17.38:5060>
User-Agent: Alcatel-Lucent 8460 ACS 8.5.0b6114
Allow: ACK,BYE,CANCEL,INFO,REFER,MESSAGE,INVITE,NOTIFY
Session-Expires: 1800;refresher=uac
Supported: timer
Accept-Language: en
Content-Length: 218
Content-type: application/sdp

v=0
o=edial_ivr 638708234241521418 241521420 IN IP4 10.234.17.38
s=phone-call
c=IN IP4 10.234.17.38
t=0 0
m=audio 12000 RTP/AVP 8 0 101
a=rtpmap:8 PCMA/8000/1
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15

2013-08-21 12:57:36.006592
ACK sip:3015@10.234.17.38:5060 SIP/2.0
Via: SIP/2.0/UDP 10.234.24.10;branch=z9hG4bK449fea706cd4d228c98ec92d3d8cfd32;received=10.234.24.10:5060
Call-ID: 01cbcee445a522cbd645fd32f0d0ff0d@10.234.24.10
CSeq: 125137642 ACK
From: "IT System En" <sip:3172@10.234.24.10;user=phone>;tag=abaa173d720c63b72b43af3506275da5
To: <sip:3015@10.234.17.38;user=phone>;tag=638708234241521418
Contact: sip:3172@10.234.24.10
User-Agent: OmniPCX Enterprise R10.0 j1.410.45
Max-Forwards: 70
Content-Length: 0


2013-08-21 12:57:37.002052
BYE sip:3015@10.234.17.38:5060 SIP/2.0
Via: SIP/2.0/UDP 10.234.24.10;branch=z9hG4bK55880f04f84c1278bafc74cc9edd3bd0;received=10.234.24.10:5060
Call-ID: 01cbcee445a522cbd645fd32f0d0ff0d@10.234.24.10
CSeq: 125137643 BYE
From: <sip:3172@10.234.24.10;user=phone>;tag=abaa173d720c63b72b43af3506275da5
To: <sip:3015@10.234.17.38;user=phone>;tag=638708234241521418
User-Agent: OmniPCX Enterprise R10.0 j1.410.45
Supported: replaces,timer,path,100rel
Max-Forwards: 70
Content-Length: 0


2013-08-21 12:57:37.002584
SIP/2.0 200 OK
Via: SIP/2.0/UDP 10.234.24.10;branch=z9hG4bK55880f04f84c1278bafc74cc9edd3bd0
Call-ID: 01cbcee445a522cbd645fd32f0d0ff0d@10.234.24.10
CSeq: 125137643 BYE
From: <sip:3172@10.234.24.10;user=phone>;tag=abaa173d720c63b72b43af3506275da5
To: <sip:3015@10.234.17.38;user=phone>;tag=638708234241521418
User-Agent: Alcatel-Lucent 8460 ACS 8.5.0b6114
Allow: ACK,BYE,CANCEL,INFO,REFER,MESSAGE,INVITE,NOTIFY
Content-Length: 0


------------------------------------------------
2013-08-21 13:02:38.109026
INVITE sip:3015@10.234.17.38;user=phone SIP/2.0
Via: SIP/2.0/UDP 10.234.24.10;branch=z9hG4bKdadcec9009ac1df231e0333ab424e931;received=10.234.24.10:5060
Call-ID: 57feaa39ca9a61e046fdb3c35895b49c@10.234.24.10
CSeq: 980551382 INVITE
From: "Zaim Moutaz" <sip:3531@10.234.24.10;user=phone>;tag=9eeefee6bb96c51af137a0404c17bbff
To: <sip:3015@10.234.17.38;user=phone>
Contact: <sip:3531@10.234.24.10;transport=UDP>
User-Agent: OmniPCX Enterprise R10.0 j1.410.45
Accept-Language: en
Allow: INVITE, ACK, CANCEL, BYE, PRACK, NOTIFY, REFER, SUBSCRIBE, OPTIONS, UPDATE, INFO
Supported: histinfo,replaces,timer,path
Session-Expires: 1800;refresher=uac
Min-SE: 900
P-Alcatel-CSBU: categparty=internal;call_condition=localdirect
Max-Forwards: 70
Content-Length: 265
Content-type: application/sdp

v=0
o=OXE 1377075648 1377075648 IN IP4 10.234.24.10
s=abs
c=IN IP4 10.234.25.15
t=0 0
m=audio 32514 RTP/AVP 8 4 97
a=sendrecv
a=rtpmap:8 PCMA/8000
a=ptime:20
a=maxptime:30
a=rtpmap:4 G723/8000
a=ptime:30
a=maxptime:30
a=rtpmap:97 telephone-event/8000

2013-08-21 13:02:38.109577
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 10.234.24.10;branch=z9hG4bKdadcec9009ac1df231e0333ab424e931
Call-ID: 57feaa39ca9a61e046fdb3c35895b49c@10.234.24.10
CSeq: 980551382 INVITE
From: "Zaim Moutaz" <sip:3531@10.234.24.10;user=phone>;tag=9eeefee6bb96c51af137a0404c17bbff
To: <sip:3015@10.234.17.38;user=phone>
Contact: <sip:3015@10.234.17.38:5060>
User-Agent: Alcatel-Lucent 8460 ACS 8.5.0b6114
Allow: ACK,BYE,CANCEL,INFO,REFER,MESSAGE,INVITE,NOTIFY
Accept-Language: en
Content-Length: 0


2013-08-21 13:02:38.110014
SIP/2.0 200 OK
Via: SIP/2.0/UDP 10.234.24.10;branch=z9hG4bKdadcec9009ac1df231e0333ab424e931
Call-ID: 57feaa39ca9a61e046fdb3c35895b49c@10.234.24.10
CSeq: 980551382 INVITE
From: "Zaim Moutaz" <sip:3531@10.234.24.10;user=phone>;tag=9eeefee6bb96c51af137a0404c17bbff
To: <sip:3015@10.234.17.38;user=phone>;tag=638708234241521431
Contact: <sip:3015@10.234.17.38:5060>
User-Agent: Alcatel-Lucent 8460 ACS 8.5.0b6114
Allow: ACK,BYE,CANCEL,INFO,REFER,MESSAGE,INVITE,NOTIFY
Session-Expires: 1800;refresher=uac
Supported: timer
Accept-Language: en
Content-Length: 218
Content-type: application/sdp

v=0
o=edial_ivr 638708234241521431 241521433 IN IP4 10.234.17.38
s=phone-call
c=IN IP4 10.234.17.38
t=0 0
m=audio 12000 RTP/AVP 8 0 101
a=rtpmap:8 PCMA/8000/1
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15

2013-08-21 13:02:38.117023
ACK sip:3015@10.234.17.38:5060 SIP/2.0
Via: SIP/2.0/UDP 10.234.24.10;branch=z9hG4bKae69b08445a4c664c2bddeab202df29d;received=10.234.24.10:5060
Call-ID: 57feaa39ca9a61e046fdb3c35895b49c@10.234.24.10
CSeq: 980551382 ACK
From: "Zaim Moutaz" <sip:3531@10.234.24.10;user=phone>;tag=9eeefee6bb96c51af137a0404c17bbff
To: <sip:3015@10.234.17.38;user=phone>;tag=638708234241521431
Contact: sip:3531@10.234.24.10
User-Agent: OmniPCX Enterprise R10.0 j1.410.45
Max-Forwards: 70
Content-Length: 0


2013-08-21 13:02:40.109958
BYE sip:3015@10.234.17.38:5060 SIP/2.0
Via: SIP/2.0/UDP 10.234.24.10;branch=z9hG4bK9a39976875b91995a8f7c0f6565edd7d;received=10.234.24.10:5060
Call-ID: 57feaa39ca9a61e046fdb3c35895b49c@10.234.24.10
CSeq: 980551383 BYE
From: <sip:3531@10.234.24.10;user=phone>;tag=9eeefee6bb96c51af137a0404c17bbff
To: <sip:3015@10.234.17.38;user=phone>;tag=638708234241521431
User-Agent: OmniPCX Enterprise R10.0 j1.410.45
Supported: replaces,timer,path,100rel
Max-Forwards: 70
Content-Length: 0


2013-08-21 13:02:40.110570
SIP/2.0 200 OK
Via: SIP/2.0/UDP 10.234.24.10;branch=z9hG4bK9a39976875b91995a8f7c0f6565edd7d
Call-ID: 57feaa39ca9a61e046fdb3c35895b49c@10.234.24.10
CSeq: 980551383 BYE
From: <sip:3531@10.234.24.10;user=phone>;tag=9eeefee6bb96c51af137a0404c17bbff
To: <sip:3015@10.234.17.38;user=phone>;tag=638708234241521431
User-Agent: Alcatel-Lucent 8460 ACS 8.5.0b6114
Allow: ACK,BYE,CANCEL,INFO,REFER,MESSAGE,INVITE,NOTIFY
Content-Length: 0

User avatar
alex
Senior Member
Posts: 1328
Joined: 06 Jul 2004 07:27
Location: Russia
Contact:

Re: 4068 or 4028 couldn't call conference center

Post by alex » 29 Aug 2013 03:22

Yep, the traces are identical.
The only clue IMHO these lines:
Sam2009 wrote: 2013-08-21 12:57:36.006592
ACK sip:3015@10.234.17.38:5060 SIP/2.0

2013-08-21 12:57:37.002052
BYE sip:3015@10.234.17.38:5060 SIP/2.0
"BYE" is sent by OXE immediately after an "ACK".
So run SIP traces on OXE.
If it looks like a duck, swims like a duck, and quacks like a duck, then it probably is a duck.

Sam2009
Member
Posts: 149
Joined: 14 Jan 2009 02:25

Re: 4068 or 4028 couldn't call conference center

Post by Sam2009 » 08 Sep 2013 06:38

Hi alex
thanks for your support
i run SIP trace on OXE , but get same traces for two case.
please note:
for same user "3531" and set physical phone "IP Touch 4018" : the call is OK when Set type is 4008 or 4018 , but when I modify set type to 4028 or 4038 or 4068 the call will release immediately!!

kindly find attached log files

Sam2009
Member
Posts: 149
Joined: 14 Jan 2009 02:25

Re: 4068 or 4028 couldn't call conference center

Post by Sam2009 » 08 Sep 2013 06:58

Set type 4028.rtf
Set type 4018.rtf
You do not have the required permissions to view the files attached to this post.

User avatar
alex
Senior Member
Posts: 1328
Joined: 06 Jul 2004 07:27
Location: Russia
Contact:

Re: 4068 or 4028 couldn't call conference center

Post by alex » 25 Sep 2013 03:45

I checked the traces.
No idea why OXE terminates the call.
Try with patch 60?
If it looks like a duck, swims like a duck, and quacks like a duck, then it probably is a duck.

Post Reply

Return to “My Teamwork (ex-eDial)”