Please be advised, the GuideMe Wizard is no longer available on the Small Business Support Community. For search capability please use the community search field to find content related to Cisco Small Business documents, videos, and discussions.
-- the box sets the calling name to be 01234567890 as well.
Is there any way to turn that off, and have the SPA just not present a calling name at all?
If not, no bother! I'm just trying to get my box to behave a little more like BT with regards to caller ID presentation -- they don't ever send a reason for no calling *name*, but if the calling number is withheld or unavailable they will set the calling name to Withheld or Unavailable -- and set a reason for no calling number.
Message was edited by: Martin Thorpe -- hopefully removed the auto-'email address' tagging! (Argh, no, it didn't. Bodged a different way.)
Thanks for the thoughtful presentation of your SIP headers, that definitely helps me in my lab setting. I see the same thing too, when I'm using an Asterisk server. I believe it is the expected behavior of this ATA to handle a FROM field with no string of text identifying caller ID, to just display the string of numbers in the sip URI. What I'm interested in, is, what does your entire SIP packet look like? Are we using a Contact field?
But, again, I believe it is expected behavior and I do not believe there is a setting to allow the ATA that, in the event of no string of text being available in the FROM field, to "failover" to display "Unknown" or something like that, unless the product management team has any ideas.
That's from a slightly patched Asterisk server, which doesn't put a calling name in if it's blank -- by default if you didn't set a calling name, Asterisk will also set the calling name from the calling number and you'd get this instead:
I've done product management myself so I know one customer asking for it to work a little differently (as opposed to it doing something wrong!) isn't going to make a change -- that's no problem at all. If it were to be changed, I'd rather the ATA didn't generate a calling name field in the CLID spill at all, rather than 'Unknown'. But hey, that's just my opinion!
For the avoidance of doubt, the ATA is always generating the calling *number* field in the CLID spill correctly.
Welcome and thanks for visiting the Small Business Community Newsletter. This is our first of what we will make a monthly newsletter where you will be provided information on New products and trends, What’s ...
Hello @All ,
I am Bhuvi Chopra, a product manager on the Cisco Business (formerly SBTG) Team.
Cisco Business is excited to offer its San Jose customers a unique opportunity to join us at Cisco headquarters for a design thinki...
Join us on Thursday, November 14 at 10:00 am PT to learn more about how Cisco is empowering small business. From connectivity to cloud applications, networking plays a crucial role in every business journey. Cisco Business offers simple-to-deploy, fl...
Join us on Thursday, November 14 at 10:00 am PT to learn more about how Cisco is empowering small business. From connectivity to cloud applications, networking plays a crucial role in every business journey. Cisco Business offers simple-to-deploy, f...
Cisco helps you grow your business and your network reliably. Introducing the new Catalyst 1000 series switches that provide your small business network with flexibility, simplicity, scalability and security for deployments of up to 250 users. Read ...