I second this that Verizon is full of Bull, we have done this with our Nortel CS1k and it works very well.
You just add a Calling Party Privicy activate code.
It works perfectly, BTN will not go out. It shows up as Private to the called party.
It works well with Verizon, have yet to try this on...
I would lean more toward the terminal or device that is connected to it. Like bignose said flow control issue or something odd.
If possible I would leave the qsdi port disconnected for a couple of days. Odds are it wont disable.
Never had a QSDI port go bad unless lightning was involved
I had seen an article as to the effect that MattPatterson wasn't looking aquire the Enterprise unit. Week or so back, I just cant find the link now.
Who-ever, I just hope they keep the CS1K line alive
Go to load 57 and change the FFC feature code of CPP to something that is usable in your dialing range. We match ours to the commonly used code #57
When you user needs to block outgoing Caller id they will Pick up on a line
Dial #57 (if you used that code)
Dial the call normally 9+ Number...
We have just cut over to CUCM 7 and are looking for Call Accouning recommendations. Does any one have Telsoft MegaCall installed and can give it a yea or nea?
Thanks for any insights
I am having the same issue Between a 5.5 CS1000 and 7 Call Manager.
Nortel accepts the call from Cisco But the Callmanager refuses the call from Nortel.
Call manager is set for open credentials, something must be missing in our Callmanager programming or it just doesn't play nice with others?
Not that this is the best answer but removing 30 from the midnight routine will prevent all digital sets from automatically disabling if they arent connected. It isnt good practice to do this just to forward calls to VM.
Using an ACD dn is easy and works quckly, using a phantom is the most...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.