Ring Group Prioritized Hunt Strategy - Destination If No Answer Does Not Work, Call Loops Back To Top of List

[itjungle]

There's an issue with a ring group which has ring strategy set to prioritized hunt.

The issue is that the incoming call never reaches destination if no answer, which in this case is a voicemail box of extension 950.

The ring group has a ring time of 15 seconds and two members: 105 and 108

When a call is placed:

• 105 rings for 15 seconds (OK),
• then 108 rings for 5 seconds (OK),
• then 105 rings again for 15 seconds (WTF),
• then 108 rings again for 15 seconds (WTF),
• and back and forth until the call disconnects due to SIP trunk timeout limit

The call never reaches the destination if no answer.

If I change the ring strategy to Ring All, then both 105 and 108 ring for 15 seconds, then the call is transfered to voicemail of 950 (OK).

Here are the activity logs from 3CX while this issue is occurring:

23/02/2021 08:40:09 - Leg L:9302.4[VMail:999] is terminated: Cause: BYE from local
23/02/2021 08:40:09 - [CM503008]: Call(C:9302): Call is terminated
23/02/2021 08:40:09 - Leg L:9302.1[Line:10001<<61298******] is terminated: Cause: CANCEL from ***.***.**.**:5060
23/02/2021 08:40:09 - Leg L:9302.3[Extn:108] is terminated: Cause: 487 Request Cancelled/INVITE from 127.0.0.1:5080
23/02/2021 08:40:09 - [CM503003]: Call(C:9302): Call to <sip:108@*******.3cx.com.au:0> has failed; Cause: 487 Request Cancelled/INVITE from 127.0.0.1:5080
23/02/2021 08:40:09 - [CM503025]: Call(C:9302): Calling T:VMail:999@[Dev:sip:[email protected]:5483;rinstance=293b4afdbdbfedce] for L:9302.1[Line:10001<<61298******]
23/02/2021 08:40:09 - [CM503005]: Call(C:9302): Forwarding: T:VMail:999@[Dev:sip:[email protected]:5483;rinstance=293b4afdbdbfedce]
23/02/2021 08:40:09 - L:9302.1[Line:10001<<61298******] forwards call from HuntGrp:800 to VMail:999 based on rule
23/02/2021 08:40:09 - [Flow] Target endpoint for 900 is VMail:999
23/02/2021 08:40:09 - L:9302.1[Line:10001<<61298******] failed to reach HuntGrp:800, reason No Answer
23/02/2021 08:39:54 - [CM505001]: Endpoint Extn:108: Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [Yealink SIP-T40G 76.84.0.95 ************] PBX contact: [sip:[email protected]:5060]
23/02/2021 08:39:54 - [CM503002]: Call(C:9302): Alerting Extn:108 by contact <sip:[email protected]:5060/UDP>
23/02/2021 08:39:54 - Leg L:9302.2[Extn:105] is terminated: Cause: 487 Request Cancelled/INVITE from 127.0.0.1:5080
23/02/2021 08:39:54 - [CM503003]: Call(C:9302): Call to <sip:105@*******.3cx.com.au:0> has failed; Cause: 487 Request Cancelled/INVITE from 127.0.0.1:5080
23/02/2021 08:39:54 - [CM503025]: Call(C:9302): Calling T:HuntGrp:800@[Dev:sip:[email protected]:5060] for L:9302.1[Line:10001<<61298******]
23/02/2021 08:39:50 - Currently active calls - 1: [9302]
23/02/2021 08:39:39 - [CM505001]: Endpoint Extn:105: Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [Yealink SIP-T46S 66.85.0.5 ************] PBX contact: [sip:[email protected]:5060]
23/02/2021 08:39:39 - [CM503002]: Call(C:9302): Alerting Extn:105 by contact <sip:[email protected]:5060/UDP>
23/02/2021 08:39:39 - [CM503025]: Call(C:9302): Calling T:HuntGrp:800@[Dev:sip:[email protected]:5060] for L:9302.1[Line:10001<<61298******]
23/02/2021 08:39:39 - [CM503027]: Call(C:9302): From: Line:10001<<61298****** ("61298******" <sip:61298******@*******.3cx.com.au:5060>) to T:HuntGrp:800@[Dev:sip:[email protected]:5060]
23/02/2021 08:39:39 - [CM503004]: Call(C:9302): Route 2: from L:9302.1[Line:10001<<61298******] to T:HuntGrp:800@[Dev:sip:[email protected]:5060]
23/02/2021 08:39:39 - [Flow] Target endpoint for 108 is Extn:108
23/02/2021 08:39:39 - [CM503027]: Call(C:9302): From: Line:10001<<61298****** ("61298******" <sip:61298******@*******.3cx.com.au:5060>) to T:HuntGrp:800@[Dev:sip:[email protected]:5060]
23/02/2021 08:39:39 - [CM503004]: Call(C:9302): Route 1: from L:9302.1[Line:10001<<61298******] to T:HuntGrp:800@[Dev:sip:[email protected]:5060]
23/02/2021 08:39:39 - [Flow] Target endpoint for 105 is Extn:105
23/02/2021 08:39:39 - [Flow] Call(C:9302): has built target endpoint: HuntGrp:800 for call from L:9302.1[Line:10001<<61298******]
23/02/2021 08:39:39 - [Flow] Target endpoint for 800 is HuntGrp:800
23/02/2021 08:39:39 - [CM503010]: Call(C:9302): Making route(s) from Line:10001<<61298****** to <sip:[email protected]:5060/UDP>
23/02/2021 08:39:39 - [CM505003]: Provider:[Breeze Connect] Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [] PBX contact: [sip:fezmx55@***.***.***.79:5060]
23/02/2021 08:39:39 - [CM500002]: Call(C:9302): Info on incoming INVITE from Line:10001<<61298******:

Invite-IN Recv Req INVITE from ***.***.**.**:5060 tid=bcd166adc3f0ca06168f483cf62e5681 Call-ID=4ea2c3e6-eff9-1239-528b-d0946663ccb3:

INVITE sip:[email protected]:5060;rinstance=9406a3e2866c92f1 SIP/2.0

Via: SIP/2.0/UDP ***.***.**.**:5060;branch=z9hG4bK-524287-1---bcd166adc3f0ca06168f483cf62e5681;rport=5060

Via: SIP/2.0/UDP 103.142.32.42:5071;rport=5071;branch=z9hG4bK-jzuykodpcpdvjxzk

Max-Forwards: 69

Record-Route: <sip:***.***.**.**;lr;ep;pinhole=UDP:3.106.146.79:5060>

Contact: sip:103.142.32.42:5071

To: <sip:[email protected]>

From: 61298****** <sip:61298******@voice.breezeconnect.com.au>;tag=azjbj4swqhcpwxdn.o

Call-ID: 4ea2c3e6-eff9-1239-528b-d0946663ccb3

CSeq: 331 INVITE

Expires: 300

Allow: INVITE, ACK, BYE, CANCEL, INFO, SUBSCRIBE, NOTIFY, REFER, MESSAGE, OPTIONS, UPDATE

Content-Disposition: session

Content-Type: application/sdp

User-Agent: PortaSIP

P-Asserted-Identity: 61298****** <sip:61298******@voice.breezeconnect.com.au>

Remote-Party-ID: 61298****** <sip:61298******@voice.breezeconnect.com.au>;party=calling

cisco-GUID: 334691823-2713881685-2105664948-375972031

h323-conf-id: 334691823-2713881685-2105664948-375972031

Content-Length: 293



v=0

o=PortaSIP 3242210083173299463 1 IN IP4 103.142.32.42

s=FreeSWITCH

t=0 0

m=audio 47254 RTP/AVP 8 18 0 101 13

c=IN IP4 103.26.174.7

a=rtpmap:8 PCMA/8000

a=rtpmap:18 G729/8000

a=rtpmap:0 PCMU/8000

a=rtpmap:101 telephone-event/8000

a=fmtp:101 0-16

a=rtpmap:13 CN/8000

a=ptime:20

23/02/2021 08:39:39 - [CM503001]: Call(C:9302): Incoming call from Line:10001<<61298****** to <sip:[email protected]:5060>
23/02/2021 08:39:39 - Line limit check: Current # of calls for line Lc:10001(@Breeze Connect[<sip:[email protected]:0/UDP>]) is 1; limit is 10
23/02/2021 08:39:39 - [CM503012]: Inbound office hours rule (unnamed) for 10001 forwards to DN:800
23/02/2021 08:39:39 - [Flow] Looking for inbound target: called=61298949133; caller="61298******" <sip:61298******@:0>

Kind Regards,

 

[VasilisV_3CX]

Hello @itjungle,

From the log you sent (note: I've removed the MAC addresses of the phones for security best practice), it shows that when the Ring Group is called, 105 rings for 15 seconds at 08:39:39 and 15 seconds later it follows the logic of the prioritised hunt and calls 108 for 15 seconds at 08:39:54, before it forwards to voicemail as you've intended at 08:40:09.

I've recreated this and it follows the same logic without a problem. I've not been able to see the 105 >> 108 >> 105 >> 108 etc that you mentioned in your post from the activity log provided. Can you capture activity log when it pendulums between 105 and 108 until the SIP trunk times out?

 

[itjungle]

Hello @itjungle,

Hello, thanks for your reply.

I have attached a captured dump file and the full activity log from 3CX for this issue.

 

[VasilisV_3CX]

Hi @itjungle,

We've reviewed the log files you've sent, and can verify that there are in fact multiple calls coming in one after the other. What you're perceiving as a loop seems to be additional calls coming through from your provider.



Notice also that after 30 seconds, your provider sends a cancel message meaning that while you intend the call to go voicemail, it never reaches voicemail. We suggest changing the time out to 10 seconds so that there is time to reach the voicemail.