Inbound Routing based on CID doesn't seem to be working 23.04.2020 23:28

Forum: Queues, Digital Receptionist, Faxmail, Voicemail and Ring Groups

If I only have an inbound route that's completely generic then everything works fine and I can route the incoming calls either to extension 100 or ring group 1.

I'd like to selectively route calls from a certain number.

So I now have 2 routes.
In 1 inbound route, I have nothing filled in for either trunk nor Caller ID Number.
In the other inbound route, I have nothing filled in for trunk but I put in the number (2225551234).

Here's my Call Monitor when the both routes exist

code:

Date               Time        Caller ID Number                            Destination       IP               Trunk                         Context  App Duration               Recording 2020-04-23     16:19:32  "NAME OF CALLER" <2225551234>  s/2225551234 44.22.­42.145  inbound22.vitelity.net  ext-did  Goto  00:00:00

Here's the call monitor when there's only the 1st route (matches all calls)

code:

Date               Time        Caller ID Number                         Destination   IP                   Trunk                         Context  App Duration               Recording 2020-04-23  16:17:37  "NAME OF CALLER" <2225551234>  100             44.22.­42.145  inbound22.vitelity.net  ext-local  Dial  00:00:00

It seems that PBXes is correctly matching the caller ID for the call, but instead of routing the call it's just dropping it.

RE: Caller ID when call forwarding 08.03.2018 20:53

Forum: Miscellaneous

Thank you for pointing me to the FAQ. Setting CID in "Outbound Caller ID" wasn't working, either.

I had set up my Vitelity-out trunk the same way it says in question 10 for the provider "Voicetrading". Now "Outbound Caller ID" works, and if I leave that blank, then the caller id from inbound calls is passed out correctly.

Caller ID when call forwarding 08.03.2018 05:05

Forum: Miscellaneous

I want to setup simultaneous ring between one of my extensions and an external number (so easily with a ring group between the SIP extension and a CLASSIC extension). I would like the external number to see the Caller ID passed through from the inbound call.

The problem when the PSTN number number is called, the Caller ID just shows "Unavailable"; ie it's empty.

I'm down to the very simple:
* Inbound route rings Ext 400.
* Ext 400 is a classic extension that rings the PSTN number number.

Same issue. Caller ID doesn't pass through. If I set it to ring a SIP extension, the CID information is present.

I don't think my provider (Vitelity.net) is at fault, since I can set the Outbound CID if I connect my SIP device directly to them instead of pbxes.org and configuring setting a "DOD Number" on the device.

So I'm thinking either PBXes is eating the caller id info and not sending it along OR it's sending the wrong headers to my provider. Anyone know how I can get it to do the right thing?