SIP Server issues

Voice & Telephony
1

Hi Everyone,
I’m new in the forum, as well as with the SIP Server. I’m facing an 8.0 installation, with a NLB, but something doesn’t work correctly, since I can’t route the call to the logged agent.
In the SIP Server logs I can see a lot of these messages, for each of the Voice Treatment Port configured.

15:31:20.959:(1) CGSIPListener[420]: Exception on listen socket
15:31:20.985:(1) Sending [420,UDP] 395 bytes to 172.26.0.121:5061 >>>>>
OPTIONS sip:TREATMENT1@SRVGSIPN1:5061 SIP/2.0
From: sip:TREATMENT1@10.192.80.41:5060;tag=4E226CEA-F551-4198-AE3F-6127AA4D4116-601815
To: sip:TREATMENT1@10.192.80.41:5060
Call-ID: 0A00E18C-64B0-4271-8763-9C24EDD384B4-601781@10.192.80.41
CSeq: 1295361065 OPTIONS
Content-Length: 0
Via: SIP/2.0/UDP 10.192.80.41:5060;branch=z9hG4bK5F37E6D0-7483-426D-BF48-7EC45F026853
Max-Forwards: 0

Can someone suggest anything?
Thanks

2

Hi,
do you proper configure the NLB port control script for enable and disable port available depend of primary/backup sip-services status ?

WBR

2 Likes
3

The Windows NLB solution works fine e.g. you configure a Virtual IP Address (VIP) and configure everything to use this VIP on port 5060. You need to configure alarms and alarm reactions to control the NLB status via a .bat file. I would recommend controlling NLB status at a host rather than a port level.

4

Hi callouj,

The messages you see in SIP Server log are related to active out-of-service check functionality - SIP Server sends in configured period OPTIONS message to Stream Manager and expects response in configured timeout. If the response isn’t received then particular instance of Stream Manager is put out of service = won’t be used by SIP Server when looking for media service.

Please post here log showing routing attempt if you have troubles with routing calls to the agents.

R.

1 Like