Search results for query: *

Duaneness we tried 0 without the 'attd' definition and it didn't seem to change the issue, I'm not sure how making it an extension would make difference. We did get our provider to change the translation of the DID from 0023 to 2323 and now everything is operating normally so there is something...

Thanks for the tip, there was a 0 defined in AAR and I removed it but it didn't help. I went and checked system-parameters and found AAR/ARS is disabled for incoming DID calls so the AAR digit conversion wasn't even enabled. Please keep the ideas coming! :)

Thanks, but when I tried removing attd from the digit 0 in the dialplan it did not fix the problem as I expected it to. Also, I tried changing digit 0 in the dialplan to misc and it also did not fix the problem So it appears that dialplan digit 0 is not the culprit in this problem.

Here is some more information as we've been testing after hours... I went into dialplan this evening and removed the attd assignment from the 0 digit, it did not fix the issue to my hypothesis of the dialplan somehow interferring was not correct. Something else is translating 0023 to send to 0

Another note, went into sys-param feat and re-directed intercept from attd to 5702 which is an announcement and it did not re-direct DID 0023 to the announcment.

Except that there is no IC when this occurs and on a couple of occasions I have tested on DID's within our DID block that have no VDN or station associated with it, immediately it shows up at the attendant with an IC suffix as configured. When calling the 0023 DID there is no IC suffix at the...

Here is one that works time data 17:38:42 Calling party trunk-group 1 member 69 cid 0x2cb 17:38:42 Calling Number & Name 9183446084 NO-CPName 17:38:42 active trunk-group 1 member 69 cid 0x2cb 17:38:42 dial 5146 17:38:42 ring station 5146 cid 0x2cb 17:38:48...

Another note, I went into cha dialplan and tried to change 0 from attd to blank or extension and the system would not accept the change, it's like something has 0 locked as the attendant function no matter what. I've got a call into our telco service provider to see how hard it would be to...

Here is the trace time data 16:48:40 Calling party trunk-group 1 member 65 cid 0x15a 16:48:40 Calling Number & Name 9183446084 NO-CPName 16:48:40 active trunk-group 1 member 65 cid 0x15a 16:48:40 dial 0 16:48:40 ring attendant-group 1 cid 0x15a 16:48:48...

Thanks, but but as I stated previously it does not appear to provide that information, I've watched it several times as I've called in and it doesn't seem to provide that information.

It's not being intercepted, there is no IC indication at the attendant's console (verified by dialing an undefined DID and it produce the IC indicator), also when running a trace it clearly shows it's dial 0 and transferring to the attendant. That's what makes me think some how the dialplan is...

I've already done the trunk-id and verified the trunk-group is correct, and the incoming casll handling treatment is correct. It's like either the DID information is not correct or the dialplan is overriding the incoming call handling treatment. Is there any way to run a trace command that...

Ok some more notes, I tried changing the translation on another one of our incoming call treatment lines and it did change so I know it is working. Is there any kind of trace function that will actually display the DID digits coming from the CO on our PRI?

I have tried the incoming call handling treatment and it doesn't seem to resolve the issue. Is there some setting in trunk-group settings that needs to be turned on to enable the incoming call handling treatment translation? I tried: tie 4 0023 4 5100 (incoming 4, 0023, del 4, replace with...

Some more notes, this is a G3 V9 system, I've been playing around with list trace tac and I can see the call coming in and what it shows is dial 0 and then calling attd I keep wondering if our dial numbering plan may be interferring somehow but I'm going to try turning off the attendant for 0...

Is there anyway to view or log the DID information coming into the system via the D channel on the PRI? Or is there some way to view the call route information / log within the switch?

Extension is invalid due to dialplan Which per the dialplan 0 is the attd

We have a DID coming into our system via PRI that we cannot seem to figure out how it is working and we all seem to be stumped. Basically the last four of the DID is 0023 and I have confirmed on several occasions with the service provider that they are in fact sending 0023. When you go to the...

Ok, I found our vectors and was able to setup a vdn/vector combination so I think I'm in good shape now! :)

I'm sorry, I'm not seeing how to add a secondary user to a mailbox. Also, how would I forward the calls off-net?