- Joined
- Mar 22, 2023
- Messages
- 15
- Reaction score
- 12
I think I found a bug in the latest Beta, not sure how far back it goes.
We have two Sip trunks, one for SMS only, one for Voice only. They both have the same DID's present.
e.g.
I can successfully assign the two identical DID's to separate destinations without any issues.
However when I try to assign the same DID, from both trunks, to the same destination, it instead assigns the voice trunk DID twice.
e.g.
The section to add the DID also glitches in this situation and shows the name(DID Friendly Name) as the name for both entries and when you select the second instance it doesn't change the GUI, but then looks like above in the inbound rules report after you save.
Not sure if this is a bug that's worth resolving, as its a very niche use case, but thought i would post it just in case anyone else is having the same problem.
As a work around i created a queue for the inbound SMS and added only the extension that needs access.
We have two Sip trunks, one for SMS only, one for Voice only. They both have the same DID's present.
e.g.
| Id | Trunk | DID | Name | Destination |
11 | Trunk1 - SMS | 1********05 | SMS only 05 | SMS - 9005 |
9 | Trunk2 - Voice | 1********05 | MAIN | OFFICE - DAY |
I can successfully assign the two identical DID's to separate destinations without any issues.
However when I try to assign the same DID, from both trunks, to the same destination, it instead assigns the voice trunk DID twice.
e.g.
| Id | Trunk | DID | Name | Destination |
23 | Trunk2 - Voice | 1********61 | 61 | Ext *** |
19 | Trunk2 - Voice | 1********61 | 61 | Ext *** |
The section to add the DID also glitches in this situation and shows the name(DID Friendly Name) as the name for both entries and when you select the second instance it doesn't change the GUI, but then looks like above in the inbound rules report after you save.
Not sure if this is a bug that's worth resolving, as its a very niche use case, but thought i would post it just in case anyone else is having the same problem.
As a work around i created a queue for the inbound SMS and added only the extension that needs access.