With the BCM 6.0, it is normal for it to drop if no CO line is connected to the trunk port. In the case above, the CO lines are connected. Can you confirm the CO is connected to the trunk port on your BCM 6.0?
With the BCM 6.0, it is normal for it to drop if no CO line is connected to the trunk port. In the case above, the CO lines are connected. Can you confirm the CO is connected to the trunk port on your BCM 6.0?
Yes, I have done it that way, which works. But most clients select a line button first then dial the number. This is when the BCM 6.0 issue occurs. I hope they release a patch for this.
Unfortunately, that only works for PRI or SIP trunking. As we are using SIP trunking as well, it works fine.
If I were to dial out via an analog trunk, a 10 digit phone number, with a 1 sec pause between digits, the BCM monitor would show for example 3054. Thats it, though I dialed 3054561234...
I too am having the same problem on my BCM450 6.0. Checked a client's BCM450 5.0, same issue. This problem seems to be on all newer BCM50 and BCM450 running 6.0 with analog trunks. PRI and SIP trunks are okay. I am surprised no one else have seen this. Anyone running BCM 6.0 with analog...
Jephph - Following your suggestion, I telnet into my BCM 200 and could not find the unistim terminal proxy server folder.
I also have the older i2004 phone I am trying to use on the BCM 200 3.6
Can you point me in the right direction?
Thanks,
Andrew
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.