TRY THIS pass inbound caller ID to pstn extension?

[bobkoure]

I have a PSTN phone (mobile) set as an extension.
I did this by creating a custom extension and using the dial string Local/NXXXXXXXXX@outbound-allroutes (where NXXXXXXXXX is the PSTN DID.

Is there any way to pass the inbound caller ID off to a vitelity trunk so that it will "spoof" that caller ID and I can see who's calling me when my cellphone rings?
I'd like to do this using the dial plan, if I can (mostly so I can backup / restore and not have to remember to key in codes).

[posted a list of all the things I've tried here, decided that it would just muddy the waters a bit so deleted. I have tried to make this work without asking for help]

Thanks!

 

[rossiv]

If Vitelity allows for custom CID, then it is fine. Post call logs so we can see what's going on.

 

[bobkoure]

Glad to post call logs, but they might not be necessary as I seem to have things fixed - with one question: If/when I enable other trunks, what's the best way to specify that that particular extension go through Vitelity (or other trunk that accepts a custom CID)?
Should I just create another outbound route with the DIDs for those extensions, put it higher in the list than the general NANP outbound? Or os there some way to specify in that Local/NXXXXXXXXX@outbound-allroutes? I think I've seen mention of being able to specify a Google Voice trunk with Local/42NXXXXXXXXX@outbound-allroutes. Is there one for Vitelity, or was that just because GV is using a different protocol?

BTW, what's the best way to post call logs? Simple list? CSV?

[edit]
Forgot to mention: fixed things by simply deleting the extension and custom outbound route I'd created, put trunk back the way it was, then simply created an extension with that dial string above - no other options. Beats me what I'd actually done wrong.
[/edit]

 

[rossiv]

Just for future reference, any logs should be posted in full (with the exception of information like phone numbers, secrets, etc.) inside code tags, much like you did with the edit tags. Just replace the word edit with code.

Just create another Outbound Route with the specific extension number(s) mentioned in the appropriate field(s) and put it above the NANP outbound.

 

[Jeff Schade]

Just for future reference, any logs should be posted in full (with the exception of information like phone numbers, secrets, etc.) inside code tags, much like you did with the edit tags. Just replace the word edit with code.

Just create another Outbound Route with the specific extension number(s) mentioned in the appropriate field(s) and put it above the NANP outbound.

You can also use the "Extension Routes" module and set the allowed outbound routes in the extension settings. In this case, uncheck the "Override Extension" box next to "Route CID" for the outbound route you use. If this route is used for multiple extensions other than forwarding to cell phones, you will want to include a CID value in the box or specify one in each extension.

 

[bobkoure]

I've got it working fine with a custom extension, but, where in FreePBX is the "Extension Routes" module?

 

[Jeff Schade]

I've got it working fine with a custom extension, but, where in FreePBX is the "Extension Routes" module?

It's available from Schmoozecom. Go to Admin --> Module Admin. Under "Repositories" make sure "Commercial" is selected and then select "Check Online." (Err...I think that's how you install it --it's been a while.)

The user guide is here.

 

[bobkoure]

Ah! OK - thanks! I'd thought I'd looked in every nook and cranny on FreePBX (PIAF on a RasPi).