outbound Caller ID not working (comes up private number)

<< < (2/3) > >>

QBZappy:
amenic,

Actually the unit web interface includes 100% of the features while the portal is lacking some basic features, ie call history, and a few other things. If you have physical access to the unit, it might be more convenient to configure it locally. The portal's main claim to fame is to be able to configure an OBi that is far away. A few portal wizards simplify setting up a few other features, however everything can be done locally.

infin8loop:
If the previous suggestions don't work out for you then you might try this.

Go to PHONE port OutboundCallRoute and

if flowroute is on SP1  change:   {(<**1:>(Msp1)):sp1} 
                                     to:   {(<**1:>(Msp1)):sp1(nnnnnnnnnn>$2)}

OR

if flowroute is on SP2  change:   {(<**2:>(Msp2)):sp2} 
                                     to:   {(<**2:>(Msp2)):sp2(nnnnnnnnnn>$2)}


Essentially you will be adding what is in red above to the current string.

In either case replace the nnnnnnnnnn with the 10 digit DID you want to pass as the outgoing caller id number. Your provider may require 11 digits including a leading "1" but try with 10 first. Provider voip.ms accepts 10 digits in this context. I am not familiar with flowroute. I use voip.ms subaccounts which allow a callerid number to be specified at the subaccount level in the voip.ms configuration but doing it there messes up some other things I'm doing. Configuring the callerid number as shown above works well.   

amenic:
Thanks for the great suggestions so far guys but no dice..   Here's the fields as they currently look from the "setup wizard"

Phone OutboundCallRoute:  

{(<411:18003733411>):sp1},{911:sp1},{([1-9]x?*(Mpli)):pp},{**0:aa},{***:aa2},{(<**1:>(Msp1)):sp1(xxxxxxxxxx>$2)},{(<**2:>(Msp2)):sp2},{(<**9:>(Mpp)):pp},{(Mpli):pli}

Where xxxxxxxxxxxx = DID (tried with and without a 1) - fwiw the 411 works.

I ending up first trying infin8loop's suggestion and then trying QBZappy's afterwards when it didn't work.

I also made the CallerIDName field = the 11 digit DID number (after allowing spoofing) and tried simple text and neither is changing anything in terms of how CID appears on the remote phone....

any other suggestions?  What does that ">$2" mean?

QBZappy:
Flowroute FAQ:

How do I set the Caller-ID I wish to transmit?
http://www.flowroute.com/faq/

We transmit Caller-ID based on the presence of one of the following header fields in order of preference: "P-Asserted-Identity", "Remote-Party-ID" or "From:".

Try the following. Under SIP Credentials, try putting your phone number in the URI field in the SIP Credentials. Ex: DID_num@Flowroute_ip:port#

QBZappy:
amenic,

This might be of interest:
   
Help with outgoing caller ID number...
http://www.obitalk.com/forum/index.php?topic=2235.0

Navigation

[0] Message Index

[#] Next page

[*] Previous page