[cisco-voip] 190[12679] number question

Mon Oct 5 21:12:09 EDT 2009

Figured it out.

The issue/weirdness that I was experiencing was that without any RF’s matching 1900 to block and everything was being allowed the call for a 1900 number was still being dropped/blocked.

DNA was also showing it not being matched to any 0.@ pattern which was even weirder for me.

I was looking at the problem the wrong way. I thought the call-manager had a system setting that blocked numbers beginning with 1900.

The actual issue is that 1900 XXX XXX doesn’t actually match anything in the AUNP. This was actually due to the AUNP Dial Plan version, the version installed didn’t have 1900’s as a number recognised.

So if I was to create a pattern manually that matches 01900XXXXXX it would then match.

I have since downloaded the latest AUNP Dial Plan and tested it on the LAB box and it works now.

So in summary  I had 2 issues. I couldn’t block 1901 and 1902 numbers. And 1900 numbers were being dropped for no apparent reason.

So the first issue was due to the Premium-Access filter not being applied and then not applied to the correct Partition. And the second issue was due to an older version of DP for AUNP which didn’t recognise 1900 as a number pattern. This is then fixed by upgrading to the latest DP version.

Thanks everyone for all your help too. Very much appreciated.

Regards

Karen Cheng
Network Engineer - ICT
Thiess Business Services

Thiess Pty Ltd
179 Grey Street | South Bank QLD 4101
T +61 7 3002 9807
F +61 7 3002 9829
M 0437 549 439
www.thiess.com.au<http://www.thiess.com.au/>

From: Dana Tong (AU) [mailto:Dana.Tong at didata.com.au]
Sent: Monday, 5 October 2009 6:44 PM
To: Karen Cheng
Subject: RE: [cisco-voip] 190[12679] number question

Did you check DNA? It will tell you why it is allowed.

From: Karen Cheng [mailto:kcheng at thiess.com.au]
Sent: Monday, 5 October 2009 6:28 PM
To: Dana Tong (AU)
Subject: Re: [cisco-voip] 190[12679] number question

Thanks Dana,

I ended up figuring out I had applied it to the wrong CSS. Only thing I don't understand is why 1900 numbers are being blocked without any configuration needing to be done. Couldn't find anything in service parameters or enterprise parameters.

Ahh well.
Thanks heaps though.
Karen Cheng - Blackberry

________________________________
From: Dana Tong (AU)
To: Karen Cheng
Sent: Mon Oct 05 18:04:23 2009
Subject: RE: [cisco-voip] 190[12679] number question
Hey Karen,

Check out the PDF attached.

You should be able to create a route filter for premium that says “Premium Access Exists AND Premium Subscriber Exists”.

Then create a new route pattern 0.@ with the route filter applied and BLOCK the pattern.

Cheers
Dana

From: cisco-voip-bounces at puck.nether.net [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Karen Cheng
Sent: Monday, 5 October 2009 4:47 PM
To: Mathew Miller
Cc: cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] 190[12679] number question

Thanks Matthew,

I did find the problem with the 1902 and 1901 numbers. It was the result of being applied to the wrong level.

Still got the weird thing with 1900 number calls. Technically without any restrictions set on CSS it should allow 1900 numbers through. But from what I can see it seems to block it by default.

Also I noticed that since version 5 the Premium-Access matches 190[12679] while previous versions match 19X

More curiosity now then needing to do anything with it. I might log a TAC case and see what comes back.

Thanks heaps for your help.

Karen Cheng
Network Engineer - ICT
Thiess Business Services

Thiess Pty Ltd
179 Grey Street | South Bank QLD 4101
T +61 7 3002 9807
F +61 7 3002 9829
M 0437 549 439
www.thiess.com.au<http://www.thiess.com.au/>

From: Mathew Miller [mailto:miller.mathew at gmail.com]
Sent: Monday, 5 October 2009 3:54 PM
To: Karen Cheng
Cc: cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] 190[12679] number question

Is it failing to block just in DNA or is it failing when you actually dial in from a phone? Have you recently installed the numbering plan?

What does your CSS look like? What patterns you have in it beside 0.@ with the route filer?

On Oct 5, 2009, at 12:49 AM, Karen Cheng wrote:

Thanks Matthew,

But that is what I have been trying.

I’ve tried:
•         Premium Access

And then tested and it didn’t work so I tried
•         Premium Access AND Premium Subscriber
And then tested and still no go

I’m wondering whether there is something special I need to do or if I am missing something.

For some reason 1900 numbers are blocked but not 1901 or 1902.

Karen Cheng
Network Engineer - ICT
Thiess Business Services

Thiess Pty Ltd
179 Grey Street | South Bank QLD 4101
T +61 7 3002 9807
F +61 7 3002 9829
M 0437 549 439
www.thiess.com.au<http://www.thiess.com.au/>

______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email
______________________________________________________________________

_____________________________________________________________________
IMPORTANT - This email and any attachments may be confidential and privileged. If received in error, please contact Thiess and delete all copies. You may not rely on advice and documents received by email unless confirmed by a signed Thiess letter. This restriction on reliance will not apply to the extent that the above email communication is between parties to a contract and is authorised under that contract. Before opening or using attachments, check them for viruses and defects. Thiess' liability is limited to resupplying any affected attachments.

******************************************************************************

- NOTICE FROM DIMENSION DATA AUSTRALIA

This message is confidential, and may contain proprietary or legally privileged information. If you have received this email in error, please notify the sender and delete it immediately.

Internet communications are not secure. You should scan this message and any attachments for viruses. Under no circumstances do we accept liability for any loss or damage which may result from your receipt of this message or any attachments.

******************************************************************************

______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email
______________________________________________________________________

_____________________________________________________________________
IMPORTANT - This email and any attachments may be confidential and privileged. If received in error, please contact Thiess and delete all copies. You may not rely on advice and documents received by email unless confirmed by a signed Thiess letter. This restriction on reliance will not apply to the extent that the above email communication is between parties to a contract and is authorised under that contract. Before opening or using attachments, check them for viruses and defects. Thiess' liability is limited to resupplying any affected attachments.

______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email
______________________________________________________________________

_____________________________________________________________________
IMPORTANT - This email and any attachments may be confidential and privileged.  If received in error, please contact Thiess and delete all copies.  You may not rely on advice and documents received by email unless confirmed by a signed Thiess letter.  This restriction on reliance will not apply to the extent that the above email communication is between parties to a contract and is authorised under that contract.  Before opening or using attachments, check them for viruses and defects.  Thiess' liability is limited to resupplying any affected attachments.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20091006/b594bc2f/attachment.html>