488 error

[craigreilly]

All phones and PBX on same LAN segment, same building.
199 called 108.
1 ring - then busy signal.
Call right back and it works fine.

I thought 488 was usually due to a Codec error - but since second call worked right away with no changed I am questioning it.

Phones are Grandstream 21xx series.



10/16/2018 1:16:05 PM - Leg L:345.1[Extn:199] is terminated: Cause: BYE from PBX
10/16/2018 1:16:05 PM - Leg L:345.2[Extn:108] is terminated: Cause: 488 Not Acceptable Here/INVITE from 192.168.3.23:5060
10/16/2018 1:16:05 PM - L:345.1[Extn:199] failed to reach Extn:108, reason Not Acceptable HereReason Unknown
10/16/2018 1:16:05 PM - Call to T:Extn:108@[Dev:sip:[email protected]:5060] from L:345.1[Extn:199] failed, cause: Cause: 488 Not Acceptable Here/INVITE from 192.168.3.23:5060
10/16/2018 1:16:05 PM - [CM503003]: Call(C:345): Call to <sip:[email protected]:5060> has failed; Cause: 488 Not Acceptable Here/INVITE from 192.168.3.23:5060
10/16/2018 1:16:02 PM - [CM505001]: Endpoint Extn:108: Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [Grandstream GXP2130 1.0.9.102 000b827648ad] PBX contact: [sip:[email protected]:5060]
10/16/2018 1:16:02 PM - [CM503002]: Call(C:345): Alerting Extn:108 by contact <sip:[email protected]:5060>

 

[HRMNY]

Just need more people to test. I'm sinking over here.

Did you update the firmware like I suggested? I updated the 3 clients using Grandstream phones, and have had no issue.

 

[craigreilly]

That might be your answer - but not an acceptable answer for us. The one on the GS website has had some reports of the same issue when talking to my contacts.

 

[Michael_NZ]

I've got a couple of clients now that are reporting this exact same issue, running GXP2170's across the board.

I will be doing the workaround posted but would be nice to see some official support on this.

 

[Peter D]

We are experiencing the same exact issue. We finally got the 488 error which led us here. We are going to implement the work around to test tomorrow.

3CX v15.5 sp6 + 2170 v1.0.9.102

I am pissed about this big time. We have been chasing our tails on this for weeks. It was a brand new deployment so we couldn't wrap our heads around what was happening. This makes 3CX and Grandstream look really bad.

 

[datapath]

I'm adding to the Peter D response above as we are working on the same issue. The upgrading of the firmware resolved our issue. In our situation it was when an inbound route came into a ring group or a queue, about 25% of the time the first person answering the phone would get a fast busy and the call would continue to ring the other phones in the RG. That call could be answered successfully by any of the other phones. It was not one particular phone and no rhyme or reason to which call it would be.

Sending the call (on the inbound route) directly to a single extension worked 100% of the time. When calls went to the ring group and queue was when the failure would happen.