GB number plan 3.1.30.

Originally posted: 2013-Oct-03.
More than two years ago, I informed Cisco that various pieces of documentation detailing the GB number plan were inaccurate, incomplete, and out of date.
The majority of the published data seemed to be from some time back between 2003 and 2006, but with a substantial number of additional errors and inaccuracies and certainly not up to date.
It took the best part of a year to get the documentation amended and then more than a year for the software to be updated, viz.: dp-ffr.3-1-30.GB.cop.sgn
The new file can be found at:
http://software.cisco.com/download/release.html?mdfid=278719042&softwareid=282074292&release=3.1.30-GB&os=Linux
Visit the above page, mouseover the details there, then look for the 'flat pattern file' link in the popup box, specifically:
http://www.cisco.com/web/software/282074292/105507/GBNP.txt
For the first time in more than a decade, the GB number plan functions correctly.
There are several (mostly minor) issues remaining and these will be detailed in several posts following this one.
The files below also track the changes (except for item 4).

The page at
http://software.cisco.com/download/release.html?mdfid=278719042&softwareid=282074292&release=3.1.30-GB&os=Linux
should link to the README file at
http://www.cisco.com/web/software/282074292/105507/dp-ffr-3-1-30_GBNP_Readme.txt
but the link is missing.
The same error was made when 3.1.29 was released.
Section 1 of the README mentions CSCuc48084 and links to a post within
https://supportforums.cisco.com/thread/2171992.
It should now also mention CSCug82402 and CSCuh62857 and link to
https://supportforums.cisco.com/thread/2214042
as that thread contains the details of what version 3.1.30 fixes.
The README links to
http://software.cisco.com/download/release.html?mdfid=278719042&catid=278875240&softwareid=282074292&os=Linux&release=3.1.4-IT&relind=AVAILABLE&rellifecycle=&reltype=latest
for software download. That's version 3.1.4 for ITALY not version 3.1.30 for the UK.
The same error was made when 3.1.28 and 3.1.29 were released.
The README file links to
http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/idp/504_423/deploy/dpdg.html
but that documentation (especially the GBNP dialplan details at
http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/idp/504_423/deploy/dpDlPlns.html#wp1042320
) is full of errors.
The newer version, with less errors, is here
http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/idp/911/deploy/dpDlPlns.html#wp1042716
It was corrected more than a year ago.
The same error was made when 3.1.28 and 3.1.29 were released.
In section 4 of the README, defect CSCuc48084 should also be mentioned in the list.
Cisco's legendary lack of attention to detail continues.

Similar Messages

How to switch Skype number from 3-month plan to an...

A friend initially subscribed to 3-months Skype number plan. Now she would like to change to 1-year subscription. However, there does not seem to be any option to do this. The initial 3 months just passed and an automatic charge appeared on her payment card. There does not seem to be any "modify" subscription option (not even a "cancel" subscription option). There is no Skype/Microsoft support readily available. This is very bad experience for her and it seems to be rather common issue. I am actually surprised by this and have expected more from Skype/Microsoft. Any ideas about how to change the subscription?

Hi, PetrVeprek, and welcome to the Community,
As strange as this sounds, the short-term Skype Number contract needs to be cancelled. When the subscription ends, the Skype Number is held in reserve for a period of 90 days, during which timeframe the number can be renewed for an annual term.
If all else fails, please contact Skype customer service for further assistance. I would report to Customer Service that the renewal e-mails were not received - after checking that the account's registered e-mail address is correct! You would not believe the number of enquiries I read where a Skype account's registered e-mail address has fallen into disuse, not updated, and therefore resulting in no communications received from Skype.
Regards,
Elaine
Was your question answered? Please click on the Accept as a Solution link so everyone can quickly find what works! Like a post or want to say, "Thank You" - ?? Click on the Kudos button!
Trustworthy information: Brian Krebs: 3 Basic Rules for Online Safety and Consumer Reports: Guide to Internet Security Online Safety Tip: Change your passwords often!

Query on open planned orders details with process order GR details

Dear Experts,
I need to create a query in SQ01 where the requirement is as given below,
Query output should display the open planned orders (Planned orders which is not converted to process order details) details for a material like Planned order number, Planned order quantity, Start date, Finish date and also the details of the list of process orders created for the same material with its details like PO qty, GR qty, Basic start date, Finish date, Actual finish date, BOM Component material codes, component quantity.
But i tried creating this query by joing the tables PLAF+ AFPO+AUFK+ AFKO+RESB . My input parameter will be the Material Number for which Planned order and Process orders are being created.
But i am unable to generate the output when i create a query by joining these tables
Is it possible to obtain the output for open planned order details and process order details in a single query ?
I am failing in my repeated attempts
Please provide your suggestions for developing this query
Regards,
J.Balakrishnan

Dear Bala,
as alternative , for use a query report and not a custom abap report, you can try to read data from MRP tables MDKP and MDTB . In these one tables you can find both elements (planned order and production orders) for to start to research all details that you need.
You can also use MDTB-DELKZ to filter only planned order (PA) and Production order (FE).
With the number order you can read the RESB table in order to define components details.
With this table would you the advantage to have always the opened orders.
If the following table are empty you should make a little customizing modification so that once MRP run will write them.
Give me feedback if i have been useful for you.
Daniele

Display Extension Number Instead of Switchboard Number

Hi,
We are using CUCM system in one of our branch office, we want to display extension number instead of switchboard number when we call external. But the telecom company said the dial information we send is "Unknown", need to be changed to "National Effective"... The voice gateway is C2951 and it's configured by vendor before; I can't find any configuration related to that, or maybe there wasn't any. Can someone help with this? Thanks.

Make sure the phones have external phone number mask and under route pattern you have Use Calling Party's External Phone Number Mask - checked. Then follow the below to set the called party number plan:
If its a MGCP gateway then under the route pattern>called party transfomrations> set the called party number type to local/national/international depending for the respective route pattern.
Review: http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/admin/8_5_1/ccmcfg/bccm-851-cm/b03cldpt.html#wp1350852
If its H323/SIP you can use translation rules. Review the below document:
http://www.cisco.com/c/en/us/support/docs/voice/call-routing-dial-plans/61083-voice-transla-rules.html#type_plan
-Terry
Please rate all helpful posts

Planning Mode in MRP

Hi Gurus,
Can any one throw light on Planning Mode in MRP run?
I basically what to know the difference and impact of this on MRP run?
I have basically done this keeping all other parameters same, but go same reult for planning mode 1, 2, 3.
a) Scenario 1 - I have changed the MRP controller in material master.
After MRP run with 1, 2 and 3 - Observation is planned order number is changed and it has new MRP controller.
b) Scenario 2 -I have changed the BOM of header material and added a new child item.
After MRP run with 1, 2 and 3 - Observation is planned order number remains the same and in all 3 cases picks the new BOM.
What the difference then?
Can anyone if have document made pl share it with me.
Thanks in advance,
Srini

Planning Mode 1
Planning mode 1 is if you have only set the planning file entries (net change planning indicator and net change planning horizon indicator) in the planning file for a material (see Planning Run Type).
In the planning run in planning mode 1 the system reactivates the existing planning data, that is, procurement proposals that are not firmed remain on the database and are only then adapted, if the dates and quantities do not suit the new planning situation. The system only re-explodes the BOM for adjusted procurement proposals. System performance is thus improved.
Example of changes that cause planning mode 1 to be set:
Changes in date and quantity
Requirement changes
Changes in the lot-sizing procedure or MRP type
Planning Mode 2
Planning mode 2 is if a material has planning file entries and the Re-explode BOM indicator is also set in the planning file.
In the planning run in planning mode 2, the system re-explodes the BOMs for all existing procurement proposals that are not firmed and also for those, for which the dates and quantities do not have to be adjusted.
Example of changes that cause planning mode 2 to be set:
Changes to the material BOM
Changes to the sales order BOM
Changes to the phantom assembly BOM
Changes to references assigned within BOM
Changes to material classification
Change of production version in material master or planned order
Change or conversion of BOM explosion number
Planning Mode 3
Planning mode 3 is if a material has planning file entries and the Reset order proposals indicator is also set in the planning file.
In planning mode 3 existing procurement proposals that are not firmed are completely deleted from the database and recreated. The system then re-explodes the BOMs.
Example of changes that cause planning mode 3 to be set:
In-house production time
Planned delivery time
Scheduling margin key
MRP controller
Regards,
Ajay Nikte

Inspection lot number ranges skipping

My inspection lot number ranges are skipping, those are std number ranges like 01 origin, 04 origin etc, what could be the reason for that.
Inspn lots are getting generated and I took UD also. But certain numbers in the range got skipped.
Eg:- Incoming inspn lot 010000000041 then it comes 010000000045
Lot numbers 01/42, 01/43, 01/44 does not exist in sytem.
Please suggest a way out
Thanks
Vineeth
Edited by: vineeth varghese on Jul 18, 2008 11:31 AM

Craig,
But expert suggestion says, not to switch off buffer thru SNRO as it may affect fuctionality as you said early in this discussion.
But I believe, this is to be relooked by SAP as number range skipping is not good (My case its skipping 5-7 numbers at a time). But I am not convinced with the reply from SAP also.
Anyway thanks to you craig for your advice.
SAP Note on this matter for reference of all. Thanks
================================
Note: 62077
Summary
Symptom
Gaps (jumps) occur when allocating internal numbers.
The status of the number range interval does not match the number that was last assigned.
The number assignment does not reflect the insert sequence.
IMPORTANT: Read Notes 504875 and 678501.
Other terms
Document number, number range, number range object, buffering, current number level, trip number assignment, number interval, CO document, CO actual posting, inspection lot, material document, physical inventory document, production order number, planned order number, process order number, maintenance order number
FB01, VF01, KO88, KE21, KE11, FD01, FK01, XK01, XDN1, MB01, MB0A, MB11, MB1A, MB1B, MB1C, MB31, KANK, KB11, KB13, KB14, KB41, KB43, KB44, KB21, KB23, KB24, KB31, KB33, KB34, KB51, KB53, KB54, PR01, PR02, PR03, PR04, PR05, XD01, VD01, MK01, SNUM, SM56, SNRO, VL01, VL02, CO01, CO40, CO41, VA01, MR1M, MIRO
Reason and Prerequisites
A large number of number range objects are buffered. When the system buffers a number range object, it does not update numbers individually in the database but reserves a preset group of numbers (depending on the number range object) in the database the first time a number is requested, and makes these numbers available to the application server in question. The following numbers can then be taken directly from the application server buffer. New numbers are not used in the database until the application server buffer has been used up.
The effects described under "Symptom" are a direct consequence of this:
If an application server is shut down, the numbers that are left in the buffer (that is, that are not yet assigned) are lost. As a result, there are gaps in the number assignment.
The status of the number range interval reflects the next free number that has not yet been transferred to an application server for intermediate buffering. The current number level therefore does not display the number of the "next" object.
The current number level (for each server) can be displayed using Transaction SM56. Call transaction SM56 and choose the menu 'Goto' -> 'Entries'. In the dialog box, enter the client, the affected number range object (for example, RK_BELEG) and possibly the required subobject (corresponds to the controlling area for the object RK_BELEG).
If you use several application servers, the numerical sequence will not reflect the (chronological) insert sequence because the numbers are buffered separately on the individual hosts.
Buffering the number range objects has a positive effect on performance, because the system no longer has to access the database (number range table NRIV) for each posting. Furthermore, a serialization of this table (database locking) is prevented to a large extent so that posting procedures can be carried out in parallel.
Solution
Since number range buffering does not cause any expressly assured qualities to be lost, no correction is required.
If you still require continuous allocation, you can deactivate the number range buffering specifically for individual objects.
Proceed as follows:
- Start Transaction SNRO and enter the affected object.
- Choose 'Change'.
- Deactivate buffering: Choose 'Edit' -> 'Set Up Buffering' -> 'No Buffering'.
- If you want to change the buffer size only, enter the corresponding value in the field 'No. of numbers in buffer'.
- Save the changes.
Please note that this change is a modification. The modification is overwritten as soon as the affected number range object is redelivered - in other words, you must check the change manually each time you import a release.
In particular, read Note 678501, bearing in mind that changing the buffering type - if not explicitly recommended by SAP - constitutes a modification. For other possible solutions, refer to the following notes:
179224, 599157 and 840901.
For the the following number range objects, gaps may cause users to have doubts since they are 'expecting' a sequential numbering:
Area CO:
- RK_BELEG   (CO Document)
CAUTION: Note that the problems described in Notes 20965 and 29030 may occur if you deactivate buffering.
- COPA_IST (Document number in actual posting)
- COPA_PLAN (Document number in planned posting)
- COPA_OBJ   (Profitability segment number)
Area FI:
- DEBITOR    (Customer master data)
- KREDITOR   (Vendor master data)
Area HR:
- RP_REINR (Trip numbers)
Area PM, PP, PS
- AUFTRAG    (Order number, production, process, maintenance order, network number)
- QMEL_NR    (Number range - message)
Area MM:
- MATBELEG   (Material documents)
- MATERIALNR (Material master)
Area QM:
- QLOSE      (Inspection lots in QM)
- QMEL_NR    (Number range - message)
- QMERK      (Confirmation number)
- QMERKMALE (Master inspection characteristics in QSS)
- QMERKRUECK (Confirmation number of an inspection characteristic in QM results processing)
- QMETHODEN (Inspection methods in QM)
- ROUTING_Q (Number ranges for inspection plans)
- QCONTROLCH (Quality control chart)
Area Workflow:
- EDIDOC     (IDocs)
Number range buffering can be activated or deactivated at any time.
Number range objects that have to be continuous due to legal specifications (for example, RF_BELEG, RV_BELEG), or due to a corresponding application logic must not be buffered using the buffering type 'Main memory buffering'. See also Notes 37844 (for RF_BELEG) and 23835 (for RV_BELEG).
Header Data
Release Status: Released for Customer
Released on: 10.07.2007 12:57:00
Priority: Recommendations/additional info
Category: Consulting
Primary Component: BC-SRV-NUM Number Range Management
Secondary Components: CA-GTF General Application Functions
BC-SRV-ASF-UOM Unit Management
CO Controlling
CO-OM-CCA Cost Center Accounting
CO-OM-CCA-A Master Data
CO-PA Profitability Analysis
FI Financial Accounting
FI-AP Accounts Payable
FI-AR Accounts Receivable
FI-GL General Ledger Accounting
FI-TV Business Trip Management
LO-MD-MM Material Master
MM Materials Management
MM-IM Inventory Management
MM-IM-PI Physical Inventory
PM Plant Maintenance
PP Production Planning and Control
QM Quality Management
QM-PT Quality Planning
QM-QN Quality Notifications
Edited by: viny on Jul 23, 2008 9:18 AM

Missing orders in SAP-Gap in number assignment

Hi All,
We are facing a situation where there is a gap in assignment of order numbers. We do not have any trace of any failed updates in ST22,SM13 etc. Does this mean that we missed only a "number" and not an order? Is there any other transactions that can give some information on this? Do we have any documentation from SAP that talks of a similar isssue?

<b>This is report I used for FI = RFBNUM00</b>
<b>FYI</b>
OSS note # 62077
Symptom
Gaps (jumps) occur when allocating internal numbers.
The status of the number range does not match the number last assigned.
The number assignment does not match the insert sequence.
Additional key words
Document number, Number range, Number range object, Buffering, Current number level, Trip number assignment, Number interval, CO document, CO actual posting, Inspection lot, Material document, Physical inventory document, Production order number, Planned order number, Process order number, Maintenance order number
FB01 VF01 KO88 KE21 KE11 FD01 FK01 XK01 XDN1 MB01 MB0A MB11 MB1A MB1B MB1C MB31 KANK KB11 KB13 KB14 KB41 KB43 KB44 KB21 KB23 KB24 KB31 KB33 KB34 KB51 KB53 KB54 PR01 PR02 PR03 PR04 PR05 XD01 VD01 MK01 SNUM SM56 SNRO VL01 VL02 CO01 CO40 CO41 VA01 MR1M MIRO
Cause and prerequisites
A large number of number range objects are buffered. When buffering a number range object, numbers are not updated individually in the database, rather, the first time a number is requested, a preset group of numbers are reserved in the database (depending on the number range object) numbers and these are made available to the application server in question. The following numbers can then be taken directly from the application server buffer. If the application server buffer is exhausted, new numbers are generated in the database.
The effects described under "Symptom" then result:
If an application server is shut down, the numbers that were left in the buffer (that is, that are not yet assigned) are lost. As a result, there are gaps in the number assignment.
The status of the number range interval reflects the next free number that was not yet transferred to an application server for intermediate buffering. The current number level does not therefore display the number of the "next" object.
The current number level (per server) can be displayed with Transaction SM56. Start Transaction SM56 and branch into the menu 'Goto' -> 'Entries'. In the dialog box, enter the client, the affected number range object (for example, RK_BELEG) and possibly the required subobject (corresponds to the controlling area for the object RK_BELEG).
If several application servers are used, the chronological insert sequence is not determined by the numerical sequence on the individual hosts, due to the separate buffering on the various servers.
Buffering the number range objects has a positive effect on the performance as no database access (on the number range table NRIV) is required for every posting. Furthermore, a serialization of this table (database blocking) is prevented to a large extent so that posting procedures can be carried out in parallel.
Solution
As the number range buffering does not lose any guaranteed attributes, a correction is not required.
If you still require a continuous allocation, you can deactivate the number range buffering deliberately for individual objects.
Proceed as follows:
- Start transaction SNRO and enter the affected object
- Press the 'Change' pushbutton
- Deactivate buffering: Menu 'Edit' -> 'Set buffering' -> 'No   buffering'
- If you only want to change the buffer size, please enter the   corresponding value in the field 'No. of numbers in buffer'
- Save the changes
Please note that this change is a modification. The modification is overwritten as soon as the affected number range object is redelivered - that is, you must check the change manually after every import of a maintenance level.
For the the following number range objects, gaps may cause user insecurity as a sequential numbering is 'expected':
Area CO:
- RK_BELEG   (CO Document)
Caution: Note that the problems described in notes 20965 and 29030 can occur if you deactivate the buffering.
- COPA_IST   (Document number during actual posting)
- COPA_PLAN (Document number with planned posting)
- COPA_OBJ   (Business segment number)
Area FI:
- DEBITOR    (Customer master data)
- KREDITOR   (Vendor master record data)
Area HR:
- RP_REINR   (Trip numbers)
Area PM, PP, PS
- AUFTRAG    (Order number, Production, Process, Maintenance order
number, network number.)
- QMEL_NR    (Number range message)
Area MM:
- MATBELEG   (Material documents)
- MATERIALNR (Material master)
Area QM:
- QLOSE      (Inspection lots in QM)
- QMEL_NR    (Number range message)
- QMERK      (Completion confirmation number)
- QMERKMALE (Master inspection characteristics in QSS)
- QMERKRUECK (Completion confirmation number of an inspection
             characteristic in QM results processing)
- QMETHODEN (Inspection methods in QM)
- ROUTING_Q (Number ranges for inspection plans)
- QCONTROLCH (Control chart)
Area Workflow:
- EDIDOC     (IDocs)
Number range buffering can be activated or deactivated at any time.
Number range objects that must be continuous due to legal specifications (for example RF_BELEG, RV_BELEG), or due to a corresponding application logic must not be buffered with the buffering type 'Main memory buffering'. Please see also notes 37844 (for RF_BELEG) and 23835 (for RV_BELEG).
Source code corrections
Thanks
SK

Skype Number wants me to buy credit

There's no real support here oin any language. If there is, they've hid the connection very well. They only get to you if you post a public complaint. AND I AM POSTING A PUBLIC COMPLAINT.!!
I have a subscription. I have a skype phone number plan thing. I npay money every month yet every time i try to call anyone, skype wants me to by credit. They want my friends to by credit to caqll me. No matter what kind of plan you get, they demand more and more credit!!! Go with majic jack and be done with it.
I was in the focus groups on skype when it began and they haqve been working deligently on how to nickle and dime you to death as their only mission in business.
Post transferred to Features: Skype Number message board;
subject/title edited accordingly.

Hi, David_Guilmette,
Please allow me to clarify this one important detail:
A Skype Number is a fixed line number subscription which has only one purpose: to permit you to receive calls on Skype from people who do not use Skype; they call you using this fixed line number.
A Skype Number does not support outbound calling in any way. You would indeed need a Buy Skype credit or a Skype subscription in order to cover the costs of outbound calls.
You mention that you have a subscription; please do check that the number you are attempting to call is covered by your subscription. In other words, you would be asked to cover the costs of the call you are trying to place using Skype Credit if that number is not included in the subscription you have.
Regards,
Elaine
Was your question answered? Please click on the Accept as a Solution link so everyone can quickly find what works! Like a post or want to say, "Thank You" - ?? Click on the Kudos button!
Trustworthy information: Brian Krebs: 3 Basic Rules for Online Safety and Consumer Reports: Guide to Internet Security Online Safety Tip: Change your passwords often!

Planning for 3shift production

hi,
my client doing planning in legacy system for 3 shift production.he makes plan two days before for a day production.
planning sheet contains shift detail,time interval for prodn, material number,planned qty.
Eg,
1st shift- 7.00am to 10.00am- 'X'material- 20 qty
            -10.00am to 12.00pm- 'Y' material - 3 qty
            - 12.00pm to 3.00 pm - 'Z' material - 5 qty..
2nd shift - 3.00pm to 6.00pm -'A' material - 10 qty
               6.00pm to 7.00 pm - 'B' material - 2 qty
              7.00pm to 11.00pm - 'X' material - 26 qty
3rd shift-...................................................
my question:
           i want to map this in sap. and i want to create planned order with scheduling time through MRP.
can u tell me the possiblities.
thanks in advance

Hi prakash
You can try this. Do shift definition and shift sequence with group. And Assign this group to you work center in capapcity tab view. From this the available capacity can be calculated as per the definition and sequence.
You can do scheduling by Distribution rule, Distribution function and Distribution key. The distribution function will say whether the loading of an work center is discrete or contineous. And how much % of work to be loaded to work center after how much % work.
This will have to be done more eloborative. I have given just an idea.
Finally you have to assign this Distribution key to your work center. And the scheduling will happen as per the key.
Regards
J . Saravan

SAP Message No-KL 294 Network Activity with invalid Internal Number

Hi,
I am getting System Error:NETWORK ACTIVITY WITH INVALID INTERNAL NUMBER" while doing MIGO.
I have checked network activity assigned to PO is exist but this shows some internal Number "Plan no.f.oper." which does not exist.
Please let me know how should i solve this error.
thanks
Sunil

Hi Sunil.
Did you get any response from SAP?
I have as similar or maybe the same problem.
And I found out:
When I create the purchase request out of the Project-Builder (CJ20n) - SAP seems to lose the entry of the field 'AUFPL' in the table 'EBKN'.
In these rare cases (this problem is only in about 2-3 % of our purchase requests) the network elements still exist - so they are not deleted or something like that.
I created a routine, in which I read the entry of 'AUFPL' with the corresponding network number out of table 'EBKN' as key, to correct these wrong purchase requests.
But I didn't find the reason for the problem, yet.
Every advice would be great,.
Best regards,
Marc

Numbering Plan ISDN Luxembourg

Dear,
We have a challenge using a variable length numbering plan in Luxembourg, they use a range of 6 digits +2 digits you choose yourself freely.
So for example if you have a range +35 2 111 111XX, the first digits are fixed and behind those you can freely choose.
The provider cuts the first part (6 digits) and you only get the last 2 on your E1 for incomming calls.
This is ok, we have configured this to work with Translation Patterns, but we have one challenge with outgoing calls
With the outgoing calls we only get the first digits to the receiver, so only +35 2 111 111 but not the last 2 digits, and if the party attempts to do a redial the voicegateway gets an error.
Cause i = 0x809C - Invalid number format (incomplete number)
Does anyone have any experience with these variable number plans, maybe in luxembourg.

If i am guessing this problem correctly then this what happening...
When you receive an inbound call from Telco you only get called number as XX and calling number as +35 2 333 222. Now when you make an outbound call (redial) you only able to dialing +35 2 333 222 without the last two digits and the gateway gives an invalid number format error.
To resolve this first you need to ask Telco to send correct calling number i.e. including last two digits , so that you can redial in correct format.
If my guessing it wrong , can you please explain it with example numbers and call flow.
Rate all the helpful post.
Thanks
Manish

Number transfer to preorder?

I placed my preorder last night (opened a new plan/2 year contract). My order confirmation has assigned me a new phone number. I currently have a verizon number/plan through my parents share/family plan. Will I be able to void the new number that was assigned to the contract and replace it with my existing number??

summerdp,
I am glad you were able to place your pre-order. In regards to transferring your telephone number and replacing it with the new number that was assigned to you, I do apologize as this would not be possible. If the line under your parents plan is out of contract you can just disconnect the line. There is also the option if you would like to have the number that is on your parents plan on your new account that you opened you can process an assumption of liability to bring the number over to your new account. http://vz.to/1qUXaek This will allow you to have your current number on your own account but you will still be responsible for the new line that was opened during the pre-order process.
LindseyT_VZW
Follow us on Twitter @VZWSupport

CME number stripping for outgoing calls

Hello all, I hafe a problem with CME for outgoing calls to the PSTN. Internalnumbers are 3 digits long. Numbers from PSTN are 7 digits long. Incvommin calls working fine. Outgoing calls are working also, but the first 4 digist from the nummer are twice in the calling number on the reciver side. Is there any workaround to fix this? Any suggestion are wellcom.
PS. Sitting in germany!

Hi Mehmet,
I know there are better ways to do this. Thank you for your suggestion. I will change to translation rules.
I have other problems probably you can help me. I have a translation-rule for incoming calls to show the leading 0's.
voice translation-rule 11
rule 1 /\(^.*\)/ /0\1/ type national national
rule 2 /\(^.*\)/ /00\1/ type international international
voice translation-profile 0prefix
translate called 11
dial-peer voice 3 pots
translation-profile incoming 0prefix
If I test the rule all working fine, but in real the rule dos not work.
test voice translation-rule 11 1243 type international
Matched with rule 2
Original number: 1243 Translated number: 001243
Original number type: international Translated number type: international
Original number plan: none Translated number plan: none
test voice translation-rule 11 1243 type nat
Matched with rule 1
Original number: 1243 Translated number: 01243
Original number type: national Translated number type: national
Original number plan: none Translated number plan: none
I am not sure I have a problem with the IOS.
Greetings
Rene

Anyone have exp with 6 digit closed dial plan

Hi we are doing a CM deployment in North Asia that must be provisioned to at least eventialy include South East Asia, Australia and South Asia and possibly the rest of the planet. I have been trying to work this in to a 5 digit closed numbering plan and it is bloody difficult (they might have around 5000 staff in Asia Pacific by the end of 2008). The only solution I have come with is to go with a 6 digit number plan instead, though I am reluctant as 6 digits seems exsessive for an extn. Does anyone else have experience with 6 digits ? Is/was it a problem for users is it worth doing ?

One recommandation is to use site codes, and keep 4 digit within a site, and use for example 3 digit site codes or whatever makes sense based on number of sites. This week people won't get frustratd with dialing a lot of digits when calling someone within the same building.
Chris

Migrating E&M immediate start from 2821 VGW to AS5350XM but problems with signalling

Hi,
We currently have 2821 VGW platforms running E&M Immediate start. The T1s go into the DACS and the IP interface connects to the SIP server with a simple number plan.
So, when a T1 DS0 signals, the VGW talks to the SIP server, the SIP server does a database lookup and talks back to the VGW and passes the connection details.
However we are now migrating to the AS5350XM platform and replicating the config from the 2821 to the AS5350XM is causing signalling issues.
Here is a sample of the existing 2821 config:
voice rtp send-recv
voice service pots
voice service voip
sip
bind control source-interface GigabitEthernet0/0
bind media source-interface GigabitEthernet0/0
rel1xx disable
min-se 1700
voice class codec 1
codec preference 1 g711ulaw
codec preference 2 g729r8
controller T1 1/0
ds0-group 0 timeslots 1 type e&m-immediate-start
ds0-group 1 timeslots 2 type e&m-immediate-start
ds0-group 2 timeslots 3 type e&m-immediate-start
voice-port 1/0:0
define Tx-bits idle 1111
define Tx-bits seize 0000
define Rx-bits idle 1111
define Rx-bits seize 0000
timeouts wait-release 1
connection plar 1000
voice-port 1/0:1
define Tx-bits idle 1111
define Tx-bits seize 0000
define Rx-bits idle 1111
define Rx-bits seize 0000
timeouts wait-release 1
connection plar 1001
voice-port 1/0:2
define Tx-bits idle 1111
define Tx-bits seize 0000
define Rx-bits idle 1111
define Rx-bits seize 0000
timeouts wait-release 1
connection plar 1002
dial-peer voice 1000 pots
destination-pattern 1000
port 1/0:0
dial-peer voice 1001 pots
destination-pattern 1001
port 1/0:1
dial-peer voice 1002 pots
destination-pattern 1002
port 1/0:2
dial-peer voice 1 voip
preference 1
destination-pattern .T
session protocol sipv2
session target ipv4:192.168.150.2:5060
session transport udp
voice-class codec 1
voice-class sip options-keepalive retry 1
sip-ua
retry invite 2
timers trying 150
sip-server ipv4:192.168.150.2:5060
Here is the same on on the AS5350xm:
voice rtp send-recv
voice service pots
voice service voip
sip
bind control source-interface GigabitEthernet0/0
bind media source-interface GigabitEthernet0/0
rel1xx disable
min-se 1700 session-expires 1700
voice class codec 1
codec preference 1 g711ulaw
codec preference 2 g729r8
controller T1 3/0:1
framing ESF
ds0-group 0 timeslots 1 type e&m-immediate-start
ds0-group 1 timeslots 2 type e&m-immediate-start
ds0-group 2 timeslots 3 type e&m-immediate-start
cas-custom 0
define-abcd loop-open 1 1 1 1
define-abcd loop-closure 0 0 0 0
cas-custom 1
define-abcd loop-open 1 1 1 1
define-abcd loop-closure 0 0 0 0
cas-custom 2
define-abcd loop-open 1 1 1 1
define-abcd loop-closure 0 0 0 0
voice-port 3/0:1:0
timeouts wait-release 1
connection plar 1000
voice-port 3/0:1:1
timeouts wait-release 1
connection plar 1001
voice-port 3/0:1:2
timeouts wait-release 1
connection plar 1002
dial-peer voice 1000 pots
destination-pattern 1000
port 3/0:1:0
dial-peer voice 1001 pots
destination-pattern 1001
port 3/0:1:1
dial-peer voice 1002 pots
destination-pattern 1002
port 3/0:1:2
dial-peer voice 1 voip
preference 1
destination-pattern .T
session protocol sipv2
session target ipv4:192.168.150.2:5060
session transport udp
voice-class codec 1
voice-class sip options-keepalive retry 1
sip-ua
retry invite 2
timers trying 150
sip-server ipv4:192.168.150.2:5060
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
What I did notice was the following:
1) When defining loop open and loop closed custom bit configuration is different....on the 2821 you do it on the voice port. On the AS5350, it is not supported on the voice port but appears to be configurable via the T1 controller. I'm not sure if the AS5350 needs any further E&M signalling configuration as the problem lies in the signalling....the AS5350 when the line is cleared down appears to start ringing it again and not following the signalling pattern.
2) When doing a "show voice port" on the AS5350XM does not show E&M signalling, whereas it does on the 2821:
AS5350XM:
5350VGW#sh voice port
DS0 Group 3/0:1:0 - 3/0:1:0
Type of VoicePort is CAS
Operation State is DORMANT
Administrative State is UP
No Interface Down Failure
Description is not set
Noise Regeneration is enabled
Non Linear Processing is enabled
Non Linear Mute is disabled
Non Linear Threshold is -21 dB
Music On Hold Threshold is Set to -38 dBm
In Gain is Set to 0 dB
Out Attenuation is Set to 0 dB
Echo Cancellation is enabled
Echo Cancellation NLP mute is disabled
Echo Cancellation NLP threshold is -21 dB
Echo Cancel Coverage is set to 128 ms
Echo Cancel worst case ERL is set to 6 dB
Playout-delay Mode is set to adaptive
Playout-delay Nominal is set to 60 ms
Playout-delay Maximum is set to 1000 ms
Playout-delay Minimum mode is set to default, value 40 ms
Playout-delay Fax is set to 300 ms
Connection Mode is plar
Connection Number is 1000
Initial Time Out is set to 15 s
Interdigit Time Out is set to 10 s
Call Disconnect Time Out is set to 60 s
Ringing Time Out is set to 180 s
Wait Release Time Out is set to 1 s
Spe country is not configured
Region Tone is set for US
Station name None, Station number None
Translation profile (Incoming):
Translation profile (Outgoing):
lpcor (Incoming):
lpcor (Outgoing):
DS0 channel specific status info:
                                      IN      OUT
PORT            CH SIG-TYPE    OPER STATUS   STATUS    TIP     RING
=============== == ============ ==== ======   ======    ===     ====
2821:
2821VGW#sh voice port
recEive and transMit Slot is 0, Subslot is 0, Sub-unit is 0, Port is 0
Type of VoicePort is E&M
Operation State is DORMANT
Administrative State is UP
No Interface Down Failure
Description is not set
Noise Regeneration is enabled
Non Linear Processing is enabled
Non Linear Mute is disabled
Non Linear Threshold is -21 dB
Music On Hold Threshold is Set to -38 dBm
In Gain is Set to 0 dB
Out Attenuation is Set to 0 dB
Echo Cancellation is enabled
Echo Cancellation NLP mute is disabled
Echo Cancellation NLP threshold is -21 dB
Echo Cancel Coverage is set to 128 ms
Echo Cancel worst case ERL is set to 6 dB
Playout-delay Mode is set to adaptive
Playout-delay Nominal is set to 60 ms
Playout-delay Maximum is set to 1000 ms
Playout-delay Minimum mode is set to default, value 40 ms
Playout-delay Fax is set to 300 ms
Connection Mode is plar
Connection Number is 1000
Initial Time Out is set to 15 s
Interdigit Time Out is set to 10 s
Call Disconnect Time Out is set to 60 s
Ringing Time Out is set to 180 s
Wait Release Time Out is set to 1 s
Companding Type is u-law
Rx A bit no conditioning set
Rx B bit no conditioning set
Rx C bit no conditioning set
Rx D bit no conditioning set
Tx A bit no conditioning set
Tx B bit no conditioning set
Tx C bit no conditioning set
Tx D bit no conditioning set
Rx Seize ABCD bits = 0000 Custom pattern
Rx Idle ABCD bits = 1111 Custom pattern
Tx Seize ABCD bits = 0000 Custom pattern
Tx Idle ABCD bits = 1111 Custom pattern
Ignored Rx ABCD bits = BCD
Region Tone is set for US
Analog Info Follows:
Currently processing none
Maintenance Mode Set to None (not in mtc mode)
Number of signaling protocol errors are 0
Station name None, Station number None
Translation profile (Incoming):
Translation profile (Outgoing):
lpcor (Incoming):
lpcor (Outgoing):
Voice card specific Info Follows:
Operation Type is 2-wire
E&M Type is 1
Signal Type is immediate
Dial Out Type is dtmf
In Seizure is inactive
Out Seizure is inactive
Digit Duration Timing is set to 100 ms
InterDigit Duration Timing is set to 100 ms
Pulse Rate Timing is set to 10 pulses/second
InterDigit Pulse Duration Timing is set to 750 ms
Clear Wait Duration Timing is set to 400 ms
Wink Wait Duration Timing is set to 200 ms
Wait Wink Duration Timing is set to 550 ms
Wink Duration Timing is set to 200 ms
Minimum received Wink Duration Timing is set to 140 ms
Maximun received Wink Duration Timing is set to 290 ms
Minimum seizure Timing is set to 50 ms
Delay Start Timing is set to 300 ms
Delay Duration Timing is set to 2000 ms
Dial Pulse Min. Delay is set to 140 ms
Percent Break of Pulse is 60 percent
Auto Cut-through is disabled
Dialout Delay is 300 ms
Hookflash-in Timing is set to 480 ms
Hookflash-out Timing is set to 400 ms
DS0 channel specific status info:
                                      IN      OUT
PORT            CH SIG-TYPE    OPER STATUS   STATUS    TIP     RING
=============== == ============ ==== ======   ======    ===     ====
0/0/0:0          01 e&m-imd     dorm idle     idle
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
Can anyone advise if further configuration is required on the AS5350XM in order to pass the E&M signalling correctly ?

Well for me the forms were ok to open with 11g, just had to correct differences and recompile to run.
That there script is a ton of help!..well you forgot to mention the Output_File parameter, but I could find that myself now that I knew what to look at. Now if I could also set it not to produce .err files when everything went fine and to set the output names so that the old compiled forms get overwritten..
the SRW.* calls turned out to be things used in Reports, so it was hopeless to compile in forms..but also not needed
as for ENABLE_ITEM and DISABLE_ITEM I found these to use as their definitions in a library, that proved sufficient.
procedure enable_item
( p_menuName in varchar2
, p_menuItemName in varchar2
) is
v_menuItem menuitem;
begin
v_menuItem := find_menu_item(p_menuName||'.'||
p_menuItemName);
if (not id_null(v_menuItem))
and (get_menu_item_property(v_menuItem,visible) = 'TRUE')
then
set_menu_item_property(v_menuItem, enabled, property_true);
end if;
end;
procedure disable_item
( p_menuName in varchar2
, p_menuItemName in varchar2
) is
v_menuItem menuitem;
begin
v_menuItem := find_menu_item(p_menuName||'.'||
p_menuItemName);
if (not id_null(v_menuItem))
and (get_menu_item_property(v_menuItem,visible) = 'TRUE')
then
set_menu_item_property(v_menuItem, enabled, property_false);
end if;
end;Some forms still playing with me, but the compilation issues there don't seem to be connected with this topic..and now I got issues with reports >.< but that requires a topic elsewhere. Thanks all!

GB number plan 3.1.30.

Similar Messages

Maybe you are looking for