Recent content by JSilverberg

Correct, it prompts for (and performs) a reboot at the end of the process.

Thanks, but as per my posts, that's exactly how I changed the IP.

This is how I did the IP change - but *somewhere* in the system it is still remembered, as the web interface reports the old IP, but the server is clearly listening on the new IP. In addition, like I said, the icmp replied on the NEW IP are coming back from *both* interfaces (internal and wan)...

I'm running into an issue with my teleworker server. I had to re-IP my network, and the teleworker IP had to be changed. I changed it via the ssh interface (is there any way to get to a command line??) and the box seems thoroughly confused. On one hand, it will respond to pings on the new IP...

Looking closer at the situation, the D-Channel (for SOME reason) goes down, and once it comes up it flaps until I restart the system. It did this for 6 hours straight it would appear before the system was restarted and the issue cleared. What could lead to this behaviour?

New to the 3300 (coming from a BCM, ugh) and I have an odd issue... twice in the past two weeks my D-channel flapped, and when it comes back up calls still ring busy to those trunks (from outside in). I've tried "returning to service" the trunk lines with no success, but a restart of the system...

Seems to work fine to another line, in fact it's working just fine today. Tomorrow will be another story... any other thoughts?

I just tried this, but with no luck. I'm not sure I understand the concept of using a wildcard for a destination code. I created a new one called 6A, and the user type 69<phone number) to get out (which works when dialed from a set). But still a disconnect once forwarded.

If I use destination code 7, which forces it off the same PRI as it came in on, doesn't seem to change the situation...

Not sure if this is relevent, butis'an i2050 phone...

Or do you mean F78, a pause?

I'm not sure what you mean here... what is the "A" exactly, a pause? The system won't accept A as part of the forwarding number...? Or am I misunderstanding you? Thanks for the assist!!

In addition - it works SOMETIMES. I just can't quite figure out the pattern as to when it works vs. when it doesn't. I don't have any other complaints about this feature, and I've got over 130 users on the system...

I have it set up as a destination code (9) which uses route 003, which points to PRI-A... any other thoughts?

I've got a BCM400 with 2 PRI trunks. When a particular user tries to forward his DN to his cell phone, which IS allowed, it rings once (maybe, sometimes not at all) and rings fast-busy. Below is a trace of the PRI itself, and I can't determine why this would drop th call. Any thoughts? Help! :)...