好吧,那是一次有趣的经历,得到了一些有趣的答复,但是大多数人仍然会去TAC,这很有意义,如果第二天没有解决,我也会做同样的事情,但是确实如此,这就是这样。随之而来的是,在某个时候,我确定这个问题只有在呼叫一个特定号码的呼叫的四个响起时才会出现。该数字是在从模拟电路到该PRI的前一天移植的。我的感觉是,也许只是以某种方式转发,但同时通话的数量仍然存在限制。我们联系了电话公司,并试图验证此号码的最终目的。根据他们的说法,这个数字被移动而没有转发。从他们的角度看,这种行为没有理由。仍然存在问题,没有系统的外观,因此我们需要电话公司的帮助。开始与他们进行故障排除,看起来好像在失败的呼叫上,某事并非正确。设置消息是从我们这边断开连接的。 The router was rejecting the calls for some reason. A typical ISDN call flow would look like the following: [img]https://sites.google.com/site/avnerizhar/Home/pri-flow.gif[/img] In our failed calls, the setup and the facility were coming in, but the instead of call proceeding we were getting a ‘disconnect’, with the reason code saying “Invalid call reference value”. That was not making any sense and the router was not supposed to reject the calls. Perhaps the facility-ie messages are causing it, we don’t have to have them, lets disable them I told the phone company guys, but they said it is what allows us to have a calling name under national isdn II signaling. National ISDN??? But my side is set to DMS100, like it was on the old site … Well, that was the problem, once changed it all started to work like it should and we started to see names in the ‘debug isdn q931’. That’s it; it all came back to the basics, hoping to save others from going through the path I did, at least now when I Google it this solution comes up, later …
知识共享 - ISDN SE0/2/1:23 **错误**:L3_BADPEERMSG-第二部分
知识共享 - ISDN SE0/2/1:23 **错误**:L3_BADPEERMSG-第二部分
版权所有©2008 IDG ComRaybet2munications,Inc。