Search results for query: *

We use "SEND" if someone is away from their desk or when they leave for the day...calls will skip them and go to the next available person.

Update - it works now - it was getting to the right combination of #s. Note line # 2 - Here's my new setup: INCOMING CALL HANDLING TREATMENT Service/ Called Called Del Insert Per Call Night Feature Len Number...

That is a trace on the trunk group...that is the London switch and they have to dial 0207038 (7038 is their "exchange"). The actual extension is 6687. I ran a trace on the same trunk group while they called an assigned extension and that call went through.

This is a different switch that what I mentioned above. 12:48:17 dial 902070386687# route:ARS 12:48:17 term trunk-group 1 cid 0x19 12:48:17 dial 902070386687# route:ARS 12:48:17 route-pattern 1 preference 1 cid 0x19 12:48:17 seize trunk-group 1 member 30 cid 0x19...

No dice. Same response. I ran a trace and see that the switch is denying it - denial event 1166 - unassigned number.

6133 is the exchange in that location (Shanghai)...not an extension.

Still not working. Our current setup has the main # bridged on a phone of a receptionist and the office administrator. Would it make sense to create a VDN routing to one or the other and not have it bridged? How would that make a difference than the current setup?

It is set to attd; however, they do not have "attendants"...they have just plain old 6400 phones w/the main # bridged on them...or routing to them. I saw the incoming call handling treatment...and noticed in one location it is set up as this: public-ntwrk 8 61378187 all 8187...

We have 3 small locations (all w/out consoles-using 6400 series phones & expansion modules) and all 3 are international...when we call an unassigned # in those offices, we are getting different things-London will get dead air and Shanghai will hear a recording from the local provider that # is...

One other note-ours is an Enterprise setup. Yes, the remote site has it's own trunk group set up in their partition. Users at each site can call their own operator by dialing "0". I have a hunt group for each site for Night service (set up in each partition) that points to that site's...

Yes. We have a similar setup where an S8300 is an LSP off of the main site w/an S8710. The S8300 is site 4 and the primary local is site 1 - create a tenant for your secondary site and set all of the users and console w/that tenant #. The S8300 was recently given a console to aid w/crisis...

Tenant partitioning. Are you using that?

Figured it out! I needed to add the area code in the cell # field...now it works.

change circuit-packs - remove it from the list

That is already done.

EC500 is it set up in my location on CM 2.2 and it works except for when I call into the office, caller ID still shows my cell #. In a location using CM 3.1.1, a person w/EC500 can call from his cell, it shows his office # on the recipient's display. I'm not sure if I'm missing something or if...

Thanks to all! I have also heard that the patch does not fix the problem.

PS - Automatic Exclusion under COS is set to "y"...so maybe he does not turn it on...been a long time since I set it up.

I added it to one of his buttons. You should have it as an option I would imagine.

Exclusion button. I have it on someone here and he presses that when he does not want his secretary to pick up on the call.