Does anyone know or recommend a tool to generate PSTN calls on voice gateway with different CID?
Hi, I need to generate calls to PSTN to keep company DIDs used in a monthly basis. I guess I could setup an script to send H.323 or SIP calls to the Cisco Gateway and replacing calling number. I've been looking for on how to do this and would like to hear about if anyone has tried this before.
A Unix script should be able to log into a GW replace DN number in a SIP ephone and later initiate a call from soft SIP client. Of course, still needs to figure out and build a script.
As a different option, could IPCCX 5 script run starting once a month and using several calling numbers.
Just if someones asks, this is not for war dialing or frauds, but to keep DID registered in carrier as used ones as recommended by our account manager. Carrier provided huge amount of free numbers last year and wants to charge for non used ones, so it's cheaper to place some calls a month than paying for unused DID. Hopefully, there is a large chunk we don't use and can return back to them without risking running out of numbers in medium term. Unfortunately, management may require us to return a larger chunk reserved for a company joined ours (that runs Centrex like system but will be migrated to Cisco IPT next year and use the same E1 of main office).
Re: Does anyone know or recommend a tool to generate PSTN calls
Thanks a lot for the tip. I'll prepare a VM with it and see if I can automate by script dialing. By the reports carrier sent, inbound calls do count as used so I'd need to deploy DNs for unused phones and place some calls to them to flag DID as used.
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...
The below trick might come handy when you have to add a new node to a cluster but you don't have or is unsure of the security password for the publisher. This procedure has been around for ages.
1) Login into the CLI of the Publisher.