- Joined
- Feb 17, 2017
- Messages
- 3
- Reaction score
- 0
Hi there,
I have 3CX Pro v15 and a Beronet SIP gateway that interfaces with our local, beloved, state-owned and only supplier of telecommunications, PSTN company X....
I'm trying to get Inbound CID rules working, either on trunk level or extension (I really don't mind which), however because of the ISDN > SIP conversion my CID (or OAD) gets converted into the following example:
"0821234567" <sip:[email protected]>. As you can see, though my extension shows 0821234567 is the incoming call, it appears to me that the CID which 3CX recognizes for the rules matching is 10000 (the SIP gateway). Thus all incoming calls are seen as coming from 10000 and not the "number" part.
I'm making the following assumptions (though I stand to be corrected):
"0821234567" is the From : Display Name part.
<sip:[email protected]> used for CID matching.
I tried changing my Inbound Parameters under the Trunk's Settings but I can't seem to get my CID's to work.
And when I build CID rules, if I use *1234567 or 0821234567 or even as broad as *4567, it ignores the rule. If I use * it obviously routes everything, and if I use 10000 it also routes everything (hence my assumptions).
I have no prior experience with 3CX so please assist with suggestions if you can? I need to somehow make 3CX see the "number" part as the CID rather than the <sip:[email protected]> part.
I work for a non-profit in a very rural area. To get a 3CX partner out here to troubleshoot this would probably cost the organisation the equavalent to my whole month's salary. I'd prefer to resolve this internally...
All assistance would be greatly appreciated.
Very respectfully yours,
CM
I have 3CX Pro v15 and a Beronet SIP gateway that interfaces with our local, beloved, state-owned and only supplier of telecommunications, PSTN company X....
I'm trying to get Inbound CID rules working, either on trunk level or extension (I really don't mind which), however because of the ISDN > SIP conversion my CID (or OAD) gets converted into the following example:
"0821234567" <sip:[email protected]>. As you can see, though my extension shows 0821234567 is the incoming call, it appears to me that the CID which 3CX recognizes for the rules matching is 10000 (the SIP gateway). Thus all incoming calls are seen as coming from 10000 and not the "number" part.
I'm making the following assumptions (though I stand to be corrected):
"0821234567" is the From : Display Name part.
<sip:[email protected]> used for CID matching.
I tried changing my Inbound Parameters under the Trunk's Settings but I can't seem to get my CID's to work.
And when I build CID rules, if I use *1234567 or 0821234567 or even as broad as *4567, it ignores the rule. If I use * it obviously routes everything, and if I use 10000 it also routes everything (hence my assumptions).
I have no prior experience with 3CX so please assist with suggestions if you can? I need to somehow make 3CX see the "number" part as the CID rather than the <sip:[email protected]> part.
I work for a non-profit in a very rural area. To get a 3CX partner out here to troubleshoot this would probably cost the organisation the equavalent to my whole month's salary. I'd prefer to resolve this internally...
All assistance would be greatly appreciated.
Very respectfully yours,
CM