Angie (and Paolo),
Is that external call being place from a telco SIP trunk, or through a SIP gateway, or...(something else)?
I cannot replicate that behavior on my Organization, which has all the DIDs entered as a range. However, I am calling from another PBX (IC server) using a SIP line between the two. I just get a fast-busy when calling an unassigned DID, no message that the call cannot be completed, and the call shows up once on my Interactions page.
On your screenshot, Angie, I see it alternating between two different "Remote" names...perhaps that external provider has redundant paths to PureCloud, and keeps flipping between them automatically for x-number of retries when one path fails? (Although it doesn't consistently alternate between the two).
I'd enable the
Protocol Capture on the external trunk (under Diagnostic) for a short bit, reproduce the symptom, and then download/look at the resulting Wireshark log to see what SIP signalling is coming in associated with that call.
------------------------------
George Ganahl
Principal Program Manager
Genesys
------------------------------
Original Message:
Sent: 09-25-2018 10:18
From: Paolo Galan
Subject: Add DID one by one, or ranges - possible Issue
What we did, is unassigned a number and call it. And like you, we saw that inbound attempt to the unassigned number on the interaction list.
This is what we are referring to as a behavior that is expected.
I'll work with PS again and investigate the part where it retries. But share to us what Care has advised.
------------------------------
Paolo Galan
Global Digital Team, Customer Success
Genesys - Employees
------------------------------
Original Message:
Sent: 09-25-2018 10:04
From: Angelia Harper
Subject: Add DID one by one, or ranges - possible Issue
Okay, so if they have the DIDs in Ranges, and a call is placed to one of those unassigned DIDs it calls the system over an over for 1 second? My concern is that I have never seen this in any of our other orgs and can't reproduce it, but in this org. I have a Support case opened for this because it does not seem like that is logical behavior, each call is a different Conversation ID and only one call was placed to the system. Kind of a strange "expected behavior". I appreciate you looking at it though.
------------------------------
Angelia Harper
Avtex
Original Message:
Sent: 09-25-2018 09:56
From: Paolo Galan
Subject: Add DID one by one, or ranges - possible Issue
Hello Angelia,
I have worked with PS on this and this seems to be an expected behavior for PureCloud interaction report.
------------------------------
Paolo Galan
Global Digital Team, Customer Success
Genesys - Employees