Voice Issues 5

[BrianCosta]

Hi ...

I have IPO 11.1.2.4, I face strange problems with this.

if the user picks up a call, sometimes can't hear each other.
if the user has a call, and has a 2nd call, put the first call to hold, and picks up the second one, the parties can not hear each other.

this case suddenly and randomly occurs.

Here is an example of this:

12:02:36 47045100mS SIP Tx: TCP 192.168.0.6:5060 -> 192.168.3.129:12528
ACK sip:188@192.168.3.129:12528;transport=tcp SIP/2.0
v: SIP/2.0/TCP 192.168.0.6:5060;rport;branch=z9hG4bK7d1fcde3523fbcbf07ebb6e8266dd6a2
f: <sip:CCMSInterface@192.168.0.6>;tag=d585cb43de41804a
t: <sip:188@jett.local>;tag=647d1ba3-6fc7715d6u6p72535po2v551m4w4l_F188
i: 1_647d1ba31a5a6748d3mu3x5z1c6t5r2u4i6d50_I188
CSeq: 510 ACK
Max-Forwards: 70
User-Agent: IP Office 11.1.2.4.0 build 18
l: 0

12:02:36 47045777mS CMTARGET: c0a800061c002226 5.30.1 1726 Q931 Trunk:5 CHAN=6: PrimeForHGTarget: CC Book Tickets setorig=0 recall=0 resetExtnVars 0 catchcount=0
12:02:36 47045777mS CMTARGET: c0a800061c002226 5.30.1 1726 Q931 Trunk:5 CHAN=6: AddHGTarget CC Book Tickets (depth=0) allowq=0 type=CMNTypeDefault
12:02:36 47045777mS CMTARGET: c0a800061c002226 5.30.1 1726 Q931 Trunk:5 CHAN=6: OV visable. VM NOT visable:Group VM off GNOD
12:02:36 47045778mS CMTARGET: c0a800061c002226 5.30.1 1726 Q931 Trunk:5 CHAN=6: FindNextInServiceHgInHgIncludedList: No Alternative!
12:02:36 47045778mS CMTARGET: c0a800061c002226 5.30.1 1726 Q931 Trunk:5 CHAN=6: PrimeForHGTarget: CC Book Tickets setorig=0 recall=0 resetExtnVars 1 catchcount=0
12:02:36 47045778mS CMTARGET: c0a800061c002226 5.30.1 1726 Q931 Trunk:5 CHAN=6: AddHGTarget CC Book Tickets (depth=1) allowq=0 type=CMNTypeDefault
12:02:36 47045778mS CMTARGET: c0a800061c002226 5.30.1 1726 Q931 Trunk:5 CHAN=6: AddHGTargetRingRotary(Rotary) CC Book Tickets ring_attempt_count 0 index 6
12:02:36 47045778mS CMTARGET: c0a800061c002226 5.30.1 1726 Q931 Trunk:5 CHAN=6: ADD USER: Naser Hafez Al depth=2 disallow_cw=1 dnd=0 real_call=1 group_call=1 type(CMNTypeDefault) incl(0x0) excpt(0x3c), allow_redir(1) remote=00000000 simult 1 (0) r_
lic=T
12:02:36 47045778mS CMTARGET: c0a800061c002226 5.30.1 1726 Q931 Trunk:5 CHAN=6: CC Book Tickets: Not using 242: DND
12:02:36 47045779mS CMTARGET: c0a800061c002226 5.30.1 1726 Q931 Trunk:5 CHAN=6: ADD USER: Firas Basem Ghn depth=2 disallow_cw=1 dnd=0 real_call=1 group_call=1 type(CMNTypeDefault) incl(0x0) excpt(0x3c), allow_redir(1) remote=00000000 simult 1 (0) r
_lic=T
12:02:36 47045779mS CMTARGET: NULL: ADD PRIMARY
12:02:36 47045779mS CMTARGET: TryLoggedOutTargeting for user Firas Basem Ghn Failed Normal
12:02:36 47045779mS CMTARGET: c0a800061c002226 5.30.1 1726 Q931 Trunk:5 CHAN=6: CC Book Tickets: Not using 244: DND
12:02:36 47045779mS CMTARGET: c0a800061c002226 5.30.1 1726 Q931 Trunk:5 CHAN=6: CC Book Tickets: Not using 245: Non Tapi User not logged in And FwdU Off
12:02:36 47045779mS CMTARGET: c0a800061c002226 5.30.1 1726 Q931 Trunk:5 CHAN=6: CC Book Tickets: Not using 246: DND
12:02:36 47045779mS CMTARGET: c0a800061c002226 5.30.1 1726 Q931 Trunk:5 CHAN=6: CC Book Tickets: Not using 247: DND
12:02:36 47045780mS CMTARGET: c0a800061c002226 5.30.1 1726 Q931 Trunk:5 CHAN=6: CC Book Tickets: Not using 249: Non Tapi User not logged in And FwdU Off
12:02:36 47045780mS CMTARGET: c0a800061c002226 5.30.1 1726 Q931 Trunk:5 CHAN=6: CC Book Tickets: Not using 250: Non Tapi User not logged in And FwdU Off
12:02:36 47045780mS CMTARGET: c0a800061c002226 5.30.1 1726 Q931 Trunk:5 CHAN=6: CC Book Tickets: Not using 235: DND
12:02:36 47045780mS CMTARGET: c0a800061c002226 5.30.1 1726 Q931 Trunk:5 CHAN=6: CC Book Tickets: Not using 236: DND
12:02:36 47045780mS CMTARGET: c0a800061c002226 5.30.1 1726 Q931 Trunk:5 CHAN=6: CC Book Tickets: Not using 237: Non Tapi User not logged in And FwdU Off
12:02:36 47045780mS CMTARGET: c0a800061c002226 5.30.1 1726 Q931 Trunk:5 CHAN=6: ADD USER: Areej Basheer A depth=2 disallow_cw=1 dnd=0 real_call=1 group_call=1 type(CMNTypeDefault) incl(0x0) excpt(0x3c), allow_redir(1) remote=00000000 simult 2 (0) r
_lic=T
12:02:36 47045781mS CMTARGET: c0a800061c002226 5.30.1 1726 Q931 Trunk:5 CHAN=6: ADD USER: Islam Malek Abu depth=2 disallow_cw=1 dnd=0 real_call=1 group_call=1 type(CMNTypeDefault) incl(0x0) excpt(0x3c), allow_redir(1) remote=00000000 simult 2 (0) r
_lic=T
12:02:36 47045781mS CMTARGET: c0a800061c002226 5.30.1 1726 Q931 Trunk:5 CHAN=6: ADD USER: Nisreen Mubarek depth=2 disallow_cw=1 dnd=0 real_call=1 group_call=1 type(CMNTypeDefault) incl(0x0) excpt(0x3c), allow_redir(1) remote=00000000 simult 1 (0) r
_lic=T
12:02:36 47045781mS CMTARGET: c0a800061c002226 5.30.1 1726 Q931 Trunk:5 CHAN=6: OV visable. VM NOT visable:Group VM off GNOD
12:02:36 47045781mS CMTARGET: c0a800061c002226 5.30.1 1726 Q931 Trunk:5 CHAN=6: FindNextInServiceHgInHgIncludedList: No Alternative!
12:02:36 47045782mS CMTARGET: c0a800061c002226 5.30.1 1726 Q931 Trunk:5 CHAN=6: ADD HG CC Book Tickets Complete search - no targets found
12:02:37 47046080mS SIP Rx: TCP 192.168.3.82:60533 -> 192.168.0.6:5060
SIP/2.0 200 OK
From: <sip:CCMSInterface@192.168.0.6>;tag=1916ecc42c504081
To: <sip:122@jett.local>;tag=647d1b42-61e1b1e326226n3e12645e5a2h603c2u_F122
Call-ID: 1_647d1b42-15238f9d415n6f5d3s2v1np3t3r4f1o_I122
CSeq: 509 INVITE
Via: SIP/2.0/TCP 192.168.0.6:5060;branch=z9hG4bK780af5f13ba0a62b5bf9f1f42aa82d46
Supported: 100rel,eventlist,feature-ref,replaces,tdialog,vnd.avaya.stimulus-ipo
Allow: INVITE,ACK,BYE,CANCEL,SUBSCRIBE,NOTIFY,MESSAGE,REFER,INFO,PRACK,PUBLISH,UPDATE
User-Agent: Avaya J139 IP Phone 4.0.10.3.2 c81feae11fb3
Contact: <sip:122@192.168.3.82:60533;transport=tcp>
Content-Type: application/sdp
Content-Length: 159

v=0
o=sip:122@192.168.3.82 1 42 IN IP4 192.168.3.82
s=sip:122@192.168.3.82
c=IN IP4 192.168.3.82
b=TIAS:1920000
t=0 0
m=audio 0 RTP/AVP 8
b=TIAS:64000
12:02:37 47046084mS SIP Tx: TCP 192.168.0.6:5060 -> 192.168.3.82:60533
ACK sip:122@192.168.3.82:60533;transport=tcp SIP/2.0
v: SIP/2.0/TCP 192.168.0.6:5060;rport;branch=z9hG4bKda0fef550129e451205d9773eade6a0b
f: <sip:CCMSInterface@192.168.0.6>;tag=1916ecc42c504081
t: <sip:122@jett.local>;tag=647d1b42-61e1b1e326226n3e12645e5a2h603c2u_F122
i: 1_647d1b42-15238f9d415n6f5d3s2v1np3t3r4f1o_I122
CSeq: 509 ACK
Max-Forwards: 70
User-Agent: IP Office 11.1.2.4.0 build 18
l: 0


Accept: application/simple-message-summary
Content-Length: 0

I think the issues in this :

m=audio 0 RTP/AVP 8

because of the success calls.
12:02:53 47062429mS SIP Tx: TCP 192.168.0.6:5060 -> 192.168.0.3:49946
INVITE sip:239@192.168.0.213;transport=tcp SIP/2.0
Via: SIP/2.0/TCP 192.168.0.6:5060;rport;branch=z9hG4bKcbdf64b99f3116e5959639498fb76245
From: <sip:0780095880@jett.local>;tag=d06cd8dce99772e0
To: <sip:239@jett.local;transport=tcp>
Call-ID: 201e378b183312fca18713c1a7f0a475
CSeq: 25076172 INVITE
Contact: <sip:0780095880@192.168.0.6:5060;transport=tcp>
Max-Forwards: 70
Allow: INVITE,ACK,CANCEL,OPTIONS,BYE,INFO,REFER,NOTIFY,SUBSCRIBE,REGISTER,PUBLISH,UPDATE
Supported: timer,100rel
Min-SE: 180
Session-Expires: 180;refresher=uac
User-Agent: IP Office 11.1.2.4.0 build 18
P-Asserted-Identity: "0780095880>CC Book Tickets" <sip:0780095880@192.168.0.6:5060>
Content-Type: application/sdp
Content-Length: 295

v=0
o=UserA 2629668364 79131436 IN IP4 192.168.0.6
s=Session SDP
c=IN IP4 192.168.0.6
t=0 0
m=audio 46760 RTP/AVP 8 0 18 4 101
a=rtpmap:8 PCMA/8000
a=rtpmap:0 PCMU/8000
a=rtpmap:18 G729/8000
a=fmtp:18 annexb=no
a=rtpmap:4 G723/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15

m=audio 46760 RTP/AVP 8 0 18 4 101

How to Solve this?

 

[BrianCosta]

@BFG9K:

We have a ticket now with them but with no result.

I see that this tek-tips community has more experience than Avaya engineers.

The problem is that the voice returns when we put the call on Hold and off it.

Is there a bright spot to start with?

I will share the Wireshark trace and sys monitor trace

Here is the scenario:

Extension 177 Call Extension 123
Extension 122 Pickup the Call Using Pickup button programming on the phone
User 177 Not Hear User 122
User 122 Hear 177

Phone 177 is J139
Phone 123 is J159
Phone 122 is J139

Start time of call is 14:43
End time of call is 14:45

Below is the Link of drive sharing Wireshark trace

https://drive.google.com/file/d/1wD2GJF-hs9Qbm9AzOz4n4_4-tgSwp6_O/view?usp=sharing

 

[vfotineas]

Hello,

We have the similar issue in 2 customers. We have open 2 SR to Avaya and we still wait....

 

[BrianCosta]

@vfotineas:

Like me, don't tell me Priyanka handle it.

if you have any idea or solution from them, please share it here.

 

[IPOTS]

Cannot unzip the pcap file.

 

[vfotineas]

@BrianCosta,

No Priyanka does not handle them. Afroz handles the one ( the 3rd engineer in this SR ) & Vishnuraj the other.
If we have any suggestion or solution I will share it.

 

[IPOTS]

What network segments are 177, 123, 122 assigned too? The network topology.

In the typical situation is that you can be heard, but you cannot hear the audio coming in the opposite direction. Explanation: The probable cause of your issue is a codec mismatch or a port issue with your NAT device. This is typically a NAT/Firewall issue. The NAT/Firewall is blocking the inbound audio stream.

 

[vfotineas]

Hello,

The update from one of our SR is that :
Avaya has a lot of sites facing the same issue and the engineers are planning to escalate to product house once they have the logs from those sites.
He suggests to upgrade the firmware of the phones ( J series ) and bring the IPO to latest 11.1.3 .
We will upgrade them and I will inform you about the results.

 

[chriscon]

I have the same issue with one customer and i have upgrade to 11.1.3 and the problem is not solved.

 

[BrianCosta]

@vfotineas: is there any news ???

 

[vfotineas]

@BrianCosta I am sorry but I do not have any news yet...

 

[Abdalla Ghazy]

@BrianCosta
i need to have a conversation with you About Avaya ACCS Hardware Deployment As I have an issue with it
contact me please at abdallah.ghazy@sinatecheg.com or (+20)1282666457

 

[BrianCosta]

@vfotineas :

Have you any updates?

I have this reply from Priyanka, and I think they don't know what is happening

they investigated the call traces between extensions 177 and 122, they need a Sysmon trace file covered with the issue scenario of the call between 177 and 122 via call pickup.
One more request Can you provide us the Sip call ID of the mentioned issue scenario?

Avaya Playing with us on this, and they don't know really whats happening.


Thanks

 

[vfotineas]

@BrianCosta,

We do not have any update. We have this issue in two different systems.
They asked for monitor traces, tcpdummp files and wireshark traces from the telephone...
I am sure that they do not know really whats happening....

 

[vfotineas]

The new update is that the Higher team of Avaya wants to check the call flow from VMPro to user. So I share them the VMPro database file. mdb .
I do not understand this as we have the issue at all of kind of calls ( internals & externals) ...

 

[IPOTS]

Stall tactic. It updates the case notes.

 

[chriscon]

Hi all,

It seems that the issue is only on J100 series phones as H323 phones are not having this issue.
I have upgraded the J100 phones to the latest 4.1.1 two days now and customer didn't make any complains yet.

 

[IamaSherpa]

I had this issue more than 1 year ago on J100 as SIP, viceversa if swiched to H.323 no problems at all, opened a SR to Avaya they provided a private buld to patch which solved.

 

[vfotineas]

Hi IamaSherpa,

What version has your IPO when you had the issue?
best regards,

 

[BrianCosta]

Hi ...

This is the last Update from Pryanka,

Regarding the intermittent one-way speech issues, we do have a new firmware fix for the Jseries phones, however it is currently only tested and validated against the CM platform.

This means in its present form it is not supported on IP office. The good news is that it is in the process of compatibility testing with IP Office to make sure it does resolve the one-way speech issues and to verify it does not cause any other impact to the IP office.

Hence, we are advising that this firmware is unable to be used with IP Office for now and the T4 team will update us when it will be supported by IP Office.

Tier 4 will advise on the compatibility testing completion date and the fix will be provided in the future IP Office software service pack.

We will update you whenever we receive the new service pack software fix from the development team in the near future.

As you will be aware that the support team manager(Nirav) is copied in for awareness of this ongoing issue.

Thanks

 

[BrianCosta]

@IamaSherpa :

Can you share this ???