Unity Connection 10.0 Busy Tone

[simonmossman]

Hi all

I am getting a bust tone into Unity either by user VM or by calling the pilot. I also show a total of 24 ports (12 for pub 12 for sub). However, when I look at the server status in cluster management I see that the port status is showing 14 on the pub and 10 on the sub.??

When I look at the ports themselves it shows that theybare evenly split with 12 each?

Any ideas please?

[Ayodeji Okanlawon]

What type of intergartion is this? sccp or sip? Have you checked your unity connection services? Is the conversation manager running?

[simonmossman]

Hi

Thanks for the reply...I have checked the conversation manager and it shows as started on both servers. I did do a reboot of both servers as we are not yet in a live environment.

The integration is SIP. I could get through to Unity "Welcome " message but not the user mailbox. I checked the config and noticed that the I had two seperate port groups for the same server so I deleted one and added the other 12 ports to the same group but selected the secondary server. I also unchecked the "Register with SIP server" in the ports basic page.

[Ayodeji Okanlawon]

If you are getting to unity connection welcome prompt, then you dont have issues with your ports. What do you get after the welcome prompt? What happens when you press the message button on a subscriber phone?

[simonmossman]

I mentioned that I "did" have the welcome prompt until I made the above mentioned changes. Now I get the busy tone when going through to users voicemail and pressing the messages button on the phone.

[Ayodeji Okanlawon]

Ok. Have you licensed the servers? If you have please go to cucm and use RTMT to download the traces. Attach the traces here. Please include the time of call and calling (ie phone you pressed message button on) and called number ie (unity pilot number)

Atach the traces here

[Ayodeji Okanlawon]

You also need to ensure that under telephone integration you have entered all the ip address of your cucm servers. If a call comes to unity connection from a cucm server that is not entered in its telephony configuration, unity will reject the call

[simonmossman]

Hi Ajodeji

I Have attached the files as requested and the details are as below:

Calling 2002 to 10000 (VM Pilot) at 18:24 to !8:25 / X3 Calls

Calling 2002 to 2001 (Diverted to VM) at 18:25 / X2 Calls

Thanks

[Ayodeji Okanlawon]

Just as I said earlier in my last post, the reason your call is failing is because the cucm ip address you configured on unity connection is propably the ip address of the publisher. Calls originating from the subscriber are been rejected..

Here is the sample trace...

05858279.002 |18:24:45.924 |AppInfo  |SIPTcp - wait_SdlReadRsp: Incoming SIP TCP message from 192.168.119.19 on port 5060 index 124 with 466 bytes:
[104795,NET]
SIP/2.0 503 Service Unavailable
From: "Saraeve" <sip:2002@192.168.119.18>;tag=32929~39d6b021-4938-6515-5ef9-f775cd158b64-61315837
To: <sip:10000@192.168.119.19>
Via: SIP/2.0/TCP 192.168.119.18:5060;branch=z9hG4bK9d2650ed18c
Expires: 180
Call-ID: ad907200-41b1155d-215-1277a8c0@192.168.119.18
CSeq: 101 INVITE
Warning: 399 'Routing failed: socket=192.168.119.19:5060'
Allow: ACK,BYE,CANCEL,INVITE,NOTIFY,OPTIONS,REFER,REGISTER,SUBSCRIBE
Content-Length: 0

The warning 399 is saying I dont have this ip adress and so i cant take the call. Add this ip address to your telephony setup in unity connection and you should be fine.

[simonmossman]

Thanks for going through the log files....I have tried to locate the CUCM servers in the CUC but can only see the AXL servers in the Telephony Integration "Port Group" section and I have not configured these..

What I do not understand is that the phones were able to reach Unity before I deleted the port group then added a new one and assigned them to the secondary server?

[Ayodeji Okanlawon · Accepted solution]

You need to go to telephone integrations>port group>select the port group> then at the top>edit>servers>sip servers>add the subscriber cucm there. Port is 5060 and tls port is 5061

[Gauravdeep Mehtani]

Thanks your answer helped me.

Our Publisher IP was missing which was causing call failure.