Quote from: giqcass on March 26, 2013, 02:51:57 PM
I used this technique myself but the caller ID of the person calling did not show up. Instead it shows the CID of SP1.
Gigcass,
Passing the original caller id is a problem all to itself. The CID of SP1 showed up because the SP1 voip provider more than likely has a policy to control the outgoing call caller id.
There is an ITSP setting, X_SpoofCallerID, which sets the incoming call's caller id on the bridged outgoing call but this often causes authentication problems with your outgoing (SP1) voip provider and the call is rejected.
One way around this problem is to use a voip provider that accepts incoming sip uri calls and then forward this incoming pstn line call to your sip uri at the voip provider. At the voip provider account level you then setup automatic forwarding to your desired number. With X_SpoofCallerID set you should be able to pass the incoming call's caller id.
Voip.ms, Anveo, CallCentric and others can be configured to accept incoming sip uri calls.
Another way around this problem is to use a voip provider that allows you to setup a static numerical ip address for authentication. Most users though do not have a static numerical ip address.