[Вопросы] при звонке абоненту пишут,что неверный формат номера,удаляла номер,не помогает
 |
avatar.png (139.34 KB, Downloads: 0)
2020-09-21 03:37:31 Upload
XR007
Номер абонента правильный(префикс, код страны)?
Xiaomi Comm APP
Получайте новости о Mi продукции и MIUI
Рекомендации
* Рекомендуется загружать изображения для обложки с разрешением 720*312
Изменения необратимы после отправки
Cookies Preference Center
We use cookies on this website. To learn in detail about how we use cookies, please read our full Cookies Notice. To reject all non-essential cookies simply click «Save and Close» below. To accept or reject cookies by category please simply click on the tabs to the left. You can revisit and change your settings at any time. read more
These cookies are necessary for the website to function and cannot be switched off in our systems. They are usually only set in response to actions made by you which amount to a request for services such as setting your privacy preferences, logging in or filling in formsYou can set your browser to block or alert you about these cookies, but some parts of thesite will not then work. These cookies do not store any personally identifiable information.
These cookies are necessary for the website to function and cannot be switched off in our systems. They are usually only set in response to actions made by you which amount to a request for services such as setting your privacy preferences, logging in or filling in formsYou can set your browser to block or alert you about these cookies, but some parts of thesite will not then work. These cookies do not store any personally identifiable information.
These cookies are necessary for the website to function and cannot be switched off in our systems. They are usually only set in response to actions made by you which amount to a request for services such as setting your privacy preferences, logging in or filling in formsYou can set your browser to block or alert you about these cookies, but some parts of thesite will not then work. These cookies do not store any personally identifiable information.
Invalid number format что делать
Не проходят звонки на номера 01-09
Не проходят звонки на номера 01-09
Сообщение Valpur » Чт 11 дек 2008, 14:39
Добрый день! Проблема. Имеется запись в ARS таблице:
ARS DIGIT ANALYSIS TABLE
Location: all Percent Full: 11
Dialed Total Route Call Node ANI
String Min Max Pattern Type Num Reqd
0 2 3 5 locl n
Pattern Number: 5 Pattern Name:
Grp FRL NPA Pfx Hop Toll No. Inserted DCS/ IXC
No Mrk Lmt List Del Digits QSIG
Dgts Intw
1: 17 1 861 n user
861 n user
Суть в том, что звонки на номера 065 069 081 проходят нормально:
13:33:26 tone-receiver 01A0205 cid 0x284
13:33:26 active station 2405 cid 0x284
13:33:30 dial 90 route:ARS
13:33:30 term trunk-group 17 cid 0x284
13:33:30 dial 9065 route:ARS
13:33:30 route-pattern 5 preference 1 cid 0x284
13:33:30 seize trunk-group 17 member 10 cid 0x284
13:33:30 Setup digits 861065
13:33:30 Calling Number & Name 8612792405 NO-CPName
13:33:31 Proceed trunk-group 17 member 10 cid 0x284
13:33:31 Alert trunk-group 17 member 10 cid 0x284
13:33:32 idle trunk-group 17 member 10 cid 0x284
13:33:33 idle station 2405 cid 0x284
а номера с длиной номера 2 нет. Вот трейс звонка на номер 03:
17:37:21 tone-receiver 01A0205 cid 0x28a
17:37:21 active station 2405 cid 0x28a
17:37:25 dial 90 route:ARS
17:37:25 term trunk-group 17 cid 0x28a
17:37:36 dial 903# route:ARS
17:37:36 route-pattern 5 preference 1 cid 0x28a
17:37:36 seize trunk-group 17 member 30 cid 0x28a
17:37:36 Setup digits 86103
17:37:36 Calling Number & Name 8612792405 NO-CPName
17:37:36 denial event 1186: Invalid number format D1=0x7e D2=0x31c
17:37:36 idle trunk-group 17 member 30 cid 0x28a
17:37:39 idle station 2405 cid 0x28a
ругается на неверный формат, хотя все верно.
Сообщение 13-ый » Пт 12 дек 2008, 10:51
Сообщение Valpur » Пт 12 дек 2008, 12:20
Сообщение 13-ый » Пт 12 дек 2008, 12:31
таки вам лениво прочесть документацию.
взято из Maintenance Alarms for Avaya Communication Manager 3.1, Media Gateways and Servers.
вот что написано в разделе траблешутинг про данную ошибку:
Troubleshooting
● Check the Cause Value Information Element (LOC). See Location Codes on page 138.
● Check Communication Manager administration (network generated the Cause Value).
— Dial-plan/Location: The home NPA is administered incorrectly, causing incorrect code
conversion.
— IXC: The IXC matching pattern is administered incorrectly or not at all on the dial-plan,
causing incorrect IXC manipulation.
— AAR/ARS digit conversion: The wrong digit string substitution is being made. The call is
being routed into the wrong network and over the wrong route pattern. Further
conversion is needed but the dial string is restricted from further conversion.
— AAR/ARS digit analysis: Call type is incorrect for the call being made specifying the
wrong type of number and/or number plan information, or it is preventing code
conversion from taking place. Call is being routed to the incorrect route pattern where the
incorrect digit manipulation and/or code conversion is taking place.
— ARS toll analysis: Toll/no toll classification is incorrect, causing incorrect code conversion
at the route pattern.
— Route pattern: Incorrect NPA is causing incorrect code conversion. If the Prefix mark
field has the wrong value, incorrect code conversion takes place. Toll list in combination
with prefix mark is causing incorrect code conversion to take place. The wrong number of
digits are deleted, or failed to strip IXC digits or international code digits. Inserted the
wrong digits IXC forcing the call to the wrong inter-exchange carrier, or stripped out a
user dialed IXC code. The incorrect service or feature is specified for the call being made
on a CBC trunk group preference. The Number format was changed to a format incorrect
for the call type.
● Check administration (Communication Manager generated the Cause Value).
— Trunk group: Incoming call handling table might cause Communication Manager to
delete or insert the wrong digits or number of digits to match the dial-plan.
Invalid number format что делать
I ran across and interesting error message I haven’t seen yet, and was wondering if anybody else had experienced the same thing. When the customer calls out to most countries (Japan, Korea, Singapore, France, etc) the calls connect just fine. In the ISDN debugs, I see the plan being set as Unknown and same for the number type.
When the dial the UK however, the call is rejected and I see the below output in debug. Interestingly enough, I see the type in this case is set by CallManager as International. I thought this was just a local telco issue, but we re-routed the International calls through a few other offices and had the same results.
So I guess my question is, why would CCM be specificially setting the type to International just for the UK? Is it possible to adjust this somewhere in CCM or do I have to adjust it on the Voice Gateway?
CCM version is 4.1.3es111 and this is an H.323 gateway.
CallManager be s*Nov 16 11:53:30.109 CST: ISDN Se0/1/0:23 Q931: pak_private_number:
Invalid type/plan 0x2 0x1 may be overriden; sw-type 13
*Nov 16 11:53:30.109 CST: ISDN Se0/1/0:23 Q931: Applying typeplan for
sw-type 0xD is 0x1 0x1, Called num 01144207437XXXX
Bearer Capability i = 0x8090A2
Transfer Capability = Speech
Transfer Mode = Circuit
Transfer Rate = 64 kbit/s
Channel ID i = 0xA98381
Exclusive, Channel 1
Calling Party Number i = 0x2181, ‘206555XXXX’
Called Party Number i = 0x91, ‘01144207437XXXX’
*Nov 16 11:53:30.229 CST: ISDN Se0/1/0:23 Q931: RX Labels:
SQL date conversion results to «invalid number format model parameter.»
I have to select some data from Oracle 11g database, but I can’t seem to figure out why following select query is failing:
The query is failing with following error message:
My input for the variables fromDate and toDate are just date strings such as 20111010 etc. I have tried also more specific time (same format as in the table), but that doesn’t seem to be the problem..
In the database the CREATE_TIME column is TIMESTAMP(6) type, and for example one sample is 2011/12/19 08:04:42
Any ideas why this is error pops up?
2 Answers 2
Root Cause:
You are converting a NUMBER to STRING, assuming it to be DATE. 20111010 is not a DATE, it is a NUMBER. Also, ‘20111010’ is not a DATE, it is a STRING. They are completely different.
Error:
Coming to your query:
You are unnecessarily complicating the conversion and formatting.
The TIMESTAMP datatype is an extension on the DATE datatype. In addition to the datetime elements of the DATE datatype, the TIMESTAMP datatype holds fractions of a second to a precision between 0 and 9 decimal places, the default being 6.
In the database the CREATE_TIME column is TIMESTAMP(6) type, and for example one sample is 2011/12/19 08:04:42
Since you are dealing with TIMESTAMP you could use TO_TIMESTAMP.
While doing a DATE/TIMESTAMP arithmetic, you should leave the data type as it is and not convert it into string. You need to useTO_CHAR only for display.
Modify your filter predicate as:
Above, :fromDate and :toDate should be a string and not a number.
Or, use TO_CHAR to first convert the number into string:
Invalid number format что делать
Подключил E1, настроил на ccm4.2 route Group и route list, назначил номер на ip телефон с помощью translate pattern. Сейчас мне могут звонить из города на мой телефон, а я в город не могу.
вот что показывает циска:
Может причина в том, что показывается мой внутрений 4-х значный номер и как это исправить?
| 1. «проблема с исходящими звонками на e1» | + / – | |
Сообщение от dae  (ok) on 13-Янв-10, 17:40 | ||
| Высказать мнение | Ответить | Правка | Наверх | Cообщить модератору | ||
 | ||
| 2. «проблема с исходящими звонками на e1» | + / – | |
| Сообщение от kolotov (ok) on 13-Янв-10, 17:55 | ||
| Эту проблему я решил, надо было в pattern указать маску телефоного номера. | ||
| Высказать мнение | Ответить | Правка | Наверх | Cообщить модератору | ||
| 3. «проблема с исходящими звонками на e1» | + / – | |
Сообщение от vlakas  (ok) on 13-Янв-10, 17:59 | ||
| Если дело в ваших четырехзначных внутренних номера, то решить это можно с помощью правил трансляции. Напр: voice translation-rule 1 В исходящем dial-peer или в конфигурации порта указываем: translation-profile outgoing Outbound  Привет, друзья! Сегодня мы с вами поговорим о замечательной  Привет, дорогие дети! Сегодня я хочу рассказать вам  Дорогие дети, сегодня мы поговорим о загадочной поговорке «  Привет, дорогие дети! Сегодня мы поговорим о забавной | ||