Search results for query: *

You should be able to affect transmit volume on your paging trunk with 14-01-02.

If you mean deny an extension from making any outside calls, you could set its COS (20-06) to a class that has 20-08-02, Trunk Outgoing Calls, set to '0' . But I would beware of denying emergency calls.

I'm not familiar with UK dialing, but in my tests, to get your stated desire of +441482xxxxxx, you could set 84-14-13 to Mode 1 and 21-17 to 1482xxxxxx. Mode 1 prepends the Calling party number with +44 AND the dialed number with +44. I don't have any settings in 84-39 (all zeroes). In my tests...

I have tracked a very similar problem on an SV8100, which was caused by unused CO lines in the 8100. A normal call on an active line with Caller ID would actually trigger an adjacently unused CO line to erroneously 'detect' ringing, ring once and default to static. There are 2 ways to fix this...

If you haven't got it working yet, what kind of trunks do you have? It could be ringing into a ring group, so a quick check in 22-04 may shed some light. Let us know how it goes.

If your router UDP timeout is 180, and you have 10-23-05 (Keep Alive...) enabled for all 10 digits, 84-14-18 at 60, and 84-14-19 at 5, UDP timeout should not be the culprit. This should send an OPTIONS request every 60 seconds as a Keep-Alive and keep the port open. A packet capture would be...

By the way, what do you see (on your LCD) or hear when you try to call out and it fails? Are these sites linked in any way (CCIS, Netlink,?)?

What was the result of your router bypass (first post)? Have you tried disabling SIP ALG (or sip-helper) in the firewall? Any chance you could do a packet capture (via WebPro) with just the SIP Trunking filter enabled when you're having outbound failures?

You could turn off the CO forwarding, set trunks to 'Behind PBX' in 14-04, DIL them (22-02 and 22-07)to a virtual (to ring at all answering positions) and set 24-09-06 to No-answer forward to the boss's cell number (no access code). That way you can define your own no-answer timing. CO lines...

Oops. Looks like the minimum is 60. You may have to change the UDP timeout in the router.

Have you tried 84-14-18 in an attempt to keep the UDP port open? Might be worth a try. I'd try a setting of 21 seconds or so.

Basically, it goes like this. When a call comes in via DID, the block number defined in 7600 (for the DID digits-to-Block Number) is searched for in Command 7626. If that DID needs to be screened, the block number will have an entry of 0,1 or 2, in 7626, defining which Development table should...

CoralTech I think you're onto it. I can't think of any other way for the call to end up in a user's VM. The Unscreened transfer is the way to go.

You could turn on digit conversion in 1-1-21 (assuming your trunks are DID in 3-91) and translate your 4 digits to any extension number in 1-1-22.

If it also fails, you might run a packet capture in WebPro with only the SIP Trunk filter enabled.

BTW, what version of SV9100 is this and is it a CP10 or CP20?

It wouldn't mess anything up, but with 14-01-24 not enabled the system would use the CPN defined in 21-19 or 21-17, or the default Comwave CPN. So CPN is not likely the problem. I'm assuming you're using All-Calls forwarding. What happens to the call if you use Busy/No Answer forwarding instead?

14-01-24 may have a bearing on this. If enabled, does Comcast allow random CPN's?

You might verify that 14-01-13 is enabled for all SIP trunks.

What kind of connection is the 3rd party voicemail? Extension or trunk?