Help with outgoing caller ID number...
hwittenb:
Slicemaster,
If you are only using the OBi for one voip provider, CallWithUs, based on what you have reported you could setup CallWithUs on SP1 to register without putting the number in the URI field. Then in the SP2 configuration field setup CallWithUs to not register and put the number in the URI field as you reported. Make your outgoing calls with SP2. CallWithUs allows unregistered calling.
Curious about what is going on with this interesting finding, looking at a WireShark packet trace, it looks like when you put a number in the url field of the SP2 (or SP1) configuration, the OBi sends that number in the Sip INVITE in the From: and Remote Party ID: fields of the Sip INVITE. Hence it follows that the number could show as the caller id on an outgoing call if the voip provider allows it which you say that CWU does for outgoing calls.
Edit: If you make a call with a Gateway (VGx) provider and you have a number in the URL field of SPx provider the OBi's outgoing Sip INVITE will put that URL number in the Contact: field of the Sip Invite but not in the Remote Party-ID: field. If you wish the number to show in the Remote Party-ID field it looks like you need to have it in the SP1 or SP2 configurations. As you reported the problem is the voip provider is rejecting the number if it shows up in a Register request.
I believe the X_SpoofCallerID setting only works on "bridged" calls where it picks up the incoming caller id.
slicemaster:
tried what stewart reccomended and it didn't work... however I did find out that according to call with us, it has to do with what Remote-Party-ID gets sent out.... how can I override this setting on the obi110? I think if I can do that everything will work...
as a side note, I thought about doing the sp1 and sp2 thing, and I'm sure that would work....just not sure if its the right way of going about it is all but if worst comes to worst, i'll set it up that way...
RonR:
Quote from: Stewart on January 08, 2012, 08:06:18 am
{(<**1:>(Msp1)):sp1} to {(<**1:>(Msp1)):12121234567>sp1}
I don't believe {(<**1:>(Msp1)):12121234567>sp1} is a valid OutboundCallRoute rule syntax.
I think what you were looking for is:
{(<**1:>(Msp1)):sp1(12341234567>$2)}
For this to have any channce of working, you must dial **1 + number.
Stewart:
RonR is correct about my invalid syntax (though the replacement has a typo).
To use the primary line, could you replace {(Mpli):pli} with {(Mpli):pli(12121234567>$2)} ?
If you need two slots, instead of burning SP2, you should be able to use a VGx, with ui=12121234567 .
If you don't have a DID with them, instead of registering with CWU at all, you could send IPKall directly to your OBi, using a dynamic DNS name if needed, and a port forward. However, unless implemented some other way, incoming calls would not have simring, voicemail, etc.
RonR:
Quote from: Stewart on January 08, 2012, 11:05:23 am
RonR is correct about my invalid syntax (though the replacement has a typo).
Missing close paren added.
Quote from: Stewart on January 08, 2012, 11:05:23 am
To use the primary line, could you replace {(Mpli):pli} with {(Mpli):pli(12121234567>$2)} ?
This isn't a particularly good idea in that if you ever decide to change the PrimaryLine, you have to go back and edit the OutboundCallRoute.
Navigation
[0] Message Index
[#] Next page
[*] Previous page