|
|
Joined: Feb 2006
Posts: 17
Member
|
OP
Member
Joined: Feb 2006
Posts: 17 |
Hi,
I have a situation where dialing a certain number causes the IP phones to display call barred from time to time, not every call. As far as I am aware this is not a Mitel barring issue as the Mitel display phones display Access Denied if this is the case.
It looks like it's only a certain number, 0861xxxxxx that causes this. Another 0861 number does not have the same problem. I ran a CCS trace and the call seems to disconnect. However I am unable to interpret the CCS trace disconnect reason code. Usually during a normal call clearing its outputs a '30' but in this case it's an 'A'
I have a 3300 CXI running the latest release of software with a quad BRI. Also the problem does not appear to be trunk specific. It might a few times on a certain trunk and then not work another few times and then work again and so on.
I will paste the CCS trace. Maybe someone can shed some light on this.
Thanks in Advance.
|
|
|
Visit Atcom to get started with your new business VoIP phone system ASAP
Turn up is quick, painless, and can often be done same day.
Let us show you how to do VoIP right, resulting in crystal clear call quality and easy-to-use features that make everyone happy!
Proudly serving Canada from coast to coast.
|
|
|
Joined: Feb 2006
Posts: 17
Member
|
OP
Member
Joined: Feb 2006
Posts: 17 |
herewith the CCS trace. sorry about the misleading topic. It's something else I want to ask..
16:30:59 RO1 DPN 1B ISRM_I ;10;*1#*50*4007#*100*MEGAN*1# 16:30:59 RO1 DPN 1B SSRM_I *58*CW*vX`g@@@@@BAaY`#0861 16:30:59 RI1 DPN 7 NIM *51*3# 16:30:59 RO1 DPN 2 SSRM_I 5 16:30:59 RO1 DPN 2 SSRM_I 8 16:31:00 RO1 DPN 2 SSRM_I 5 16:31:00 RO1 DPN 2 SSRM_I 8 16:31:00 RO1 DPN 2 SSRM_I 5 16:31:01 RO1 DPN 2 SSRM_I 2 16:31:02 RI1 DPN F CRM/CIM ;A;*166*1 2 3 4#
|
|
|
|
Joined: Sep 2005
Posts: 2,049
Member
|
Member
Joined: Sep 2005
Posts: 2,049 |
The A after CRM/CIM; means the originator of the call is the one that received the "call barred" in the display . I have been working a similar issue on a Mitel sx2000 with 4 pri ckts . Intermittenly callers dialing 9xxx-xxx-xxxx would receive "call barred" in their display . Sometimes it would procees on the same trunk number sometimes it would fail on the same trunk number . I came in early yesterday and reloaded all the software back into the NSU cabinet . The problems has not reoccured in over 24 hours . So you might want to try reloadin software back onto the bri circuit cards . It's a point to start at anyway . Hope this helps .
Let It Be , I live in a Yellow Submarine . SCCE
|
|
|
|
Joined: Sep 2005
Posts: 2,049
Member
|
Member
Joined: Sep 2005
Posts: 2,049 |
I was searching our Remedy database for "call barred" troubles called into our helpdesk . One I found was getting "call barred" when one toll free number was being dialed . Turned out to be something being transmited to our D channel on the PRI from the 800 provider . Once they corrected their problem we no longer where "barred" from dialing that number . This happened with every call to that one 800 number . We could place analog trunk calls to that 800 number without failing .
Let It Be , I live in a Yellow Submarine . SCCE
|
|
|
|
Joined: Feb 2006
Posts: 17
Member
|
OP
Member
Joined: Feb 2006
Posts: 17 |
If I understand you correct you are suggesting just reloading the software on the BRI, in other words something similar to a reboot? The system has an embedded BRI unit. I know there is a command to reload software to PRI cards and NSU's but is there on to reload software on the BRI?
|
|
|
|
Joined: Feb 2006
Posts: 17
Member
|
OP
Member
Joined: Feb 2006
Posts: 17 |
When you mentioned A means that the originator received the call Barred message, who initiated it?
Thanks
|
|
|
|
Joined: Sep 2005
Posts: 2,049
Member
|
Member
Joined: Sep 2005
Posts: 2,049 |
It was sent by the bri channel to the call processor and the callprocessor sent a call barred message to the ip set ext 4007 . crm= clear request message cim= clear indication message a=send unable to compelte message "call barred" to originator . ssrm_i= send supplemental request message = incomplete .
Does not really tell us much . That's why if we run ccs trace we email them to mitel tech support for interputation . They can get their software guru's to look at them .
Let It Be , I live in a Yellow Submarine . SCCE
|
|
|
Forums84
Topics94,284
Posts638,771
Members49,765
|
Most Online5,661 May 23rd, 2018
|
|
0 members (),
147
guests, and
383
robots. |
Key:
Admin,
Global Mod,
Mod
|
|
|
|
|