[cisco-voip] Problem with un-assigned DN's

[Hefin James [ahj]]

Yes, the unassigned DNs have a CSS.

Hefin

From: Erick Wellnitz [mailto:ewellnitzvoip at gmail.com]
Sent: 19 March 2012 12:51 PM
To: Hefin James [ahj]
Cc: Lelio Fulgenzi; cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] Problem with un-assigned DN's

Do you have  a CSS on your unassigned DNs?
On Mon, Mar 19, 2012 at 4:32 AM, Hefin James [ahj] <ahj at aber.ac.uk<mailto:ahj at aber.ac.uk>> wrote:
This sounds like the answer to solve the trombone problem, but doesn't explain the cause, active extensions on the call manager should be terminated on the call manager, and not routed to the other PBX.

Thanks,
Hefin

From: Lelio Fulgenzi [mailto:lelio at uoguelph.ca<mailto:lelio at uoguelph.ca>]
Sent: 16 March 2012 3:13 PM
To: Hefin James [ahj]
Cc: cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
Subject: Re: [cisco-voip] Problem with un-assigned DN's

While this may not answer the question, I do have a suggestion which might prevent the situation happening in the future. A Cisco tech once told me, (actually, I had to have him repeat it numerous times since I was new to the whole thing) do not allow a trunk access to DNs/patterns that would route calls back to itself.

So, take your 1XXX route pattern that sends calls to the PBX. Put this in a partition that all phones have access to, i.e. in their CSS. But, do not put the partition that contains this route pattern in the outbound CSS of the gateway of the PBX. This way, if by chance a call gets routed to the PBX, it won't get rerouted back to CallManager. Once we did this, our call handling was much better. We went further to remove wildcard route patterns and use specific route patterns to the PBX.

Does the inactive DN have any forwarding target? If it's active but not assigned, it may be handled differently?

---
Lelio Fulgenzi, B.A.
Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1
(519) 824-4120 x56354 (519) 767-1060 FAX (ANNU)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Cooking with unix is easy. You just sed it and forget it.
                              - LFJ (with apologies to Mr. Popeil)
________________________________
From: "Hefin James [ahj]" <ahj at aber.ac.uk<mailto:ahj at aber.ac.uk>>
To: cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
Sent: Friday, March 16, 2012 10:46:28 AM
Subject: [cisco-voip] Problem with un-assigned DN's

We have a problem that we can't get to the bottom off.
The problem is where unassigned DN's (which have active selected) are falling through and matching a the general rule that we have forwarding to another PABX system (which has the DN marked as being on the CM, which then causes a loop on our ISDN trunk).
Dialled number analyser shows the number hitting the specific route for 1793 under PA-ABER-OWNNET with the alternative match for 1XXX. (Flow copy shown below)

Any pointers as to why it's matching the general route, and not the specific route for the DN?
It's also affecting DN's that are assigned to profiles that are logged off.

Thanks,
Hefin

Results Summary
 Calling Party Information
 Calling Party = 2456
 Partition =
 Device CSS =
 Line CSS = CS-ABER-UK-UNR
 AAR Group Name =
 AAR CSS =
Dialed Digits = 1793
Match Result = RouteThisPattern
Matched Pattern Information
Pattern = 1793
Partition = PA-ABER-OWNNET
Time Schedule =
Called Party Number = 1793
Time Zone = Etc/GMT
Call Classification = OnNet
InterDigit Timeout = NO
Device Override = Disabled
Outside Dial Tone = NO
Call Flow
TranslationPattern :Pattern=
Partition =
Positional Match List = 1793
Calling Party Number = 2456
PreTransform Calling Party Number =
PreTransform Called Party Number =
Calling Party Transformations
External Phone Number Mask = NO
Calling Party Mask =
Prefix =
CallingLineId Presentation =
CallingName Presentation =
Calling Party Number = 2456
ConnectedParty Transformations
ConnectedLineId Presentation =
ConnectedName Presentation =
Called Party Transformations
Called Party Mask =
Discard Digits Instruction =
Prefix =
Called Number =
Directory Number :DN= 1793
Partition = PA-ABER-OWNNET
TypeCFACSSPolicy =
Forwarding Information
Forward All : DN =
VoiceMail = No
CSS = Forward Busy Internal : DN = VoiceMail = No CSS = External : DN = VoiceMail = No CSS = Forward No Answer Internal : DN = VoiceMail = No CSS = External : DN = VoiceMail = No CSS = Forward No Coverage Internal : DN = VoiceMail = No CSS = External : DN = VoiceMail = No CSS = Forward Unregistered Internal : DN = VoiceMail = No CSS = External : DN = VoiceMail = No CSS = CFDF : DN = VoiceMail = No CSS = Pickup Group Number = Device : Type = No Device associated with the DN Alternate Matches Partition :Name= PA-ABER-OWNNET Pattern Pattern = 1XXX Pattern Type = Enterprise CallManager Device Type = AccessDevice PatternPrecedenceLevel = PlDefault PatternRouteClass = RouteClassDefault

_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
https://puck.nether.net/mailman/listinfo/cisco-voip

_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
https://puck.nether.net/mailman/listinfo/cisco-voip

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20120319/4f807e1d/attachment.html>