How do you make OBi110 forward the caller ID too?

<< < (2/3) > >>

QBZappy:
dialtone,

Here is a post by obi-support2 which might help you with your CID issue. Not based on the call forward method you are trying to implement.

Quote from: obi-support2 on March 31, 2011, 03:01:36 pm

OBi passes both, name and number, from the original call, if X_SpoofCallerID is yes.
ITSP however might not take it, and may reject the call all together. That's why
this is option depending on your ITSP.

However, using the SP2(xyz > abc) syntax in an InboundCallRoute, it can only spoof the number; we currently don't have a syntax for spoofing a name this way.

Also, even when we spoof it, the ITSP can selectively take the name or number part as they please and present the call to the final destination.

You have more control if the "ITSP" is a PBX (like Asterisk) for example. I do not expect this option to be very useful for a general commercial ITSP.



http://www.obitalk.com/forum/index.php?topic=530.msg3242#msg3242

RonR:
CallerID spoofing my not work on calls bridged using Call Forward Unconditional.  CallerID spoofing has not been an area many have had great success with, due to unclear/lack of documentation and what appears to be bugs or omissions.

You might try using the SP1 X_InboundCallRoute instead of Call Forward Unconditional:

Voice Services -> SP1 Service -> X_InboundCallRoute : {(xx.)>(xx.):sp2($1>9876)}

Voice Services -> SP1 Service -> CallForwardUnconditionalEnable : (unchecked)

Keep:

Service Providers -> ITSP Profile B -> SIP  -> X_SpoofCallerID : (checked)

RonR:
I'm not an Asterisk expert, but I just had a thought...

It appears you have SP2 registered on Asterisk as an extension (4567).  If that's the case, won't Asterisk simply show all incoming calls as from 4567 and not even be looking for incoming CallerID?  I believe you would need to have SP2 registered as a trunk on Asterisk, in which case CallerID would be passed (if present) to the receiving extension.

dialtone:
Quote from: RonR on July 13, 2011, 09:03:19 pm

CallerID spoofing my not work on calls bridged using Call Forward Unconditional.  CallerID spoofing has not been an area many have had great success with, due to unclear/lack of documentation and what appears to be bugs or omissions.

You might try using the SP1 X_InboundCallRoute instead of Call Forward Unconditional:

Voice Services -> SP1 Service -> X_InboundCallRoute : {(xx.)>(xx.):sp2($1>9876)}

Voice Services -> SP1 Service -> CallForwardUnconditionalEnable : (unchecked)

Keep:

Service Providers -> ITSP Profile B -> SIP  -> X_SpoofCallerID : (checked)



It just will not accept the
Voice Services -> SP1 Service -> X_InboundCallRoute : {(xx.)>(xx.):sp2($1>9876)}
after I hit the Submit button and reboot, it comes back with
Voice Services -> SP1 Service -> X_InboundCallRoute : ph
done it 3 times so far and nothing but "ph".

What am I doing wrong?

RonR:
If you're working on the OBi locally (as opposed to through the OBiTALK Web Portal), you must disable Auto Provisioning:

System Management -> Auto Provisioning -> Auto Provisioning -> Method : Disabled

Navigation

[0] Message Index

[#] Next page

[*] Previous page