Attendant console issue

[jacob83]

Hi there,

I have customer that has 2 sites (A,B) both have CS1kE linked together by SIP trunks,
A site has the 9 access ( MOC lines ).
B site taking the 9 from site A.


Suddenly, when site B dials 9 , it's automatically going to attendant console of site A !!!!

the SIP traces showing that the call is being rejected by site A!!!

B still can call A by extentions and vice versa

only 9 now is not accessible from site B

I'm expecting that something has been done in attendant console that cause this because at that customer no body even knows how to login to the system.
But I don't know exactly what that could be done in the attendant console to do this routing???

if anybody has a comment, please HELP

Regards,
Jacob

 

[bignose21]

Attendant console will be picking up the call in the Intercept data in the customer data block. The problem is not that the problem is that your SIP call is rejected. Why is it rejected:

Do you see the call coming in at Site A on the DCH Monitor?

If not what are you getting on the SIP? Where is it failing in the following process?

Site B --------Invite----------> NRS
Site B <----302 Temp move------- NRS
Site B ---------ACK------------> NRS
Site B --------Invite----------> Site A

If you did see the setup coming into Site A and it was rejected from there what was the message going out of A on the DCH MON

 

[Schill13]

Trunk Group Busy Key activated on Console?

 

[jacob83]

Thanks bignose21 and Schill13,

-of course that SIP traces I've token from site A, which means the call is coming to A and rejected there,

-Trunk Group Busy is not activated

**However, after twisting my brain and wasting my time for 2 days,
I decided to do a system reboot for site A , bingo ... it worked fine after that.
I'm always doing this for the systems when unreasonable issues just come up whitout clue

Best Regards,
Jacob