Customer has SIP trunks and they want calls forwarded to a cellphone. When calls are received on the cell it shows the Outbound CID of the system. They want the CID of the incoming caller to show on the cell instead of the business number. The call rings to a VIRTSLI that is NA FWD (1sec external fwd in 2.5.4). The VIRTSLI is then set to NA FWD to the cell in 5.15.6. It forwards correctly and there is 2 way audio but it shows the business number instead of the caller's number. Where can I set the incoming caller ID to show instead of the business number?
Thanks.
I never successfully got this to work.
The problem is with a forward like that the OS is making an outbound call and then setting up a conference call between the incomming and outgoing calls.
There is a setting "received CLI Forward on alias" between this and talking to the sip provider about sending a CLI that isn't on your account, you may be able to get it to work.
With the licensing blasted wide open, you can put 3rd party SIP clients on, if WEVOIP isn't an option, and then add that extension to the ring group? I have an app "Sipnetic" registered to mine, and WEVOIP, both, on my cell. Not sure of your situation, but that is one possible suggestion. Hope you get it sorted!
Erlier was this a classic usecase for the MOBEX feature.
That was also a strength of the OfficeServ products for a long time, unfortunately, SIP trunk / VoIP has broken a lot of Functions.
ISDN was not so cumbersome and error-prone. Above all, it was standardized and not every provider had his own soup
When i right remember the classic MOBEX usecases are only supported on classic ISDN PBX lines (T1/PRI BRI)
The simple Call Forward works also with SIP Trunk, the Carrier musst support the CLIP Overwrite and in the PBX Setting i mean some options define the way for CLIP CallForward.
On SIP Trunk everytime comes issues with ClipNoScreening or othe missing features, it is very strong carrier dependent.
I have 2 german carriers was works very good (QSC, SKC)
You can Try (Linphone) SIP Client, this is a very good Client on IOS / Android / Windows / Linux
Some from my customers use this as (Communicator) and SoftPhone replacement on new Operating Systems Windows 10 / 11
The old Clients have some issues with non exclusive Audio mode, and that is bad in a age from Teams, WebEx, TeamViewer, Netviewer, ..... and thousands of other tools.
Happy Homeoffice )-;
I believe you have to turn EFWD Extension CLI off in 2.6.2 and your SIP trunks must be set up to allow presentation of the callers number.