SIP/2.0 503 Service Unavailable

Unanswered Question
Sep 29th, 2009
User Badges:

Hi


I'm trying to set-up a click to dial service using JTAPI, I don't know where this problem is coming from as I'm new to CUCM can anyone tell me what the problem might be? Here's the error I got from the servlet log:


SIP/2.0 503 Service Unavailable

Date: Wed, 30 Sep 2009 19:59:36 GMT

Warning: 399 "Unable to find a device handler for the request received on port 5060 from 10.36.134.137"

From: Click-to-Dial<sip:[email protected]:5060>;tag=1

Content-Length: 0

To: <sip:[email protected]:5060>;tag=1181960151

Contact: <sip:[email protected]:5060;transport=tcp>

Call-ID: [email protected]

Via: SIP/2.0/TCP 10.36.134.137:5060

CSeq: 1 REFER


I'd appreciate any help.


Cheers

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (16 ratings)
Loading.
Matthieu BORSUK Thu, 06/02/2016 - 06:08
User Badges:

Hi,


For information, i had the same error because the domain on the invite was not configured in the Call Manager / Entreprise Parameters > Organization Top Level Domain & Cluster Fully Qualified Domain Name


If it can help you

Best regards

Matthieu

Ritesh Desai Tue, 09/27/2016 - 07:42
User Badges:

Hi folks,

Am facing the same issue. Unable to trace the root cause. Can someone help to trace the problem.

Am having contact center environment where Inbound calls to Agents coming from PSTN are getting into RESERVED state on Cisco Finesse desktop. After tracing, found SIP 503, Service Unavailable on CUCM and VG logs. Also, I see error "Unable to find a device handler for the request received on port 8317 from 192.168.4.12 (CVP)" on CUCM Logs.

My lab environment contains ICM Sprawler, CVP, Finesse and VG with 1E1 interface.

On ICM, call hits and remains in Queue to SG Node. Call doesnot move from Success or failure node.

Attached CUCM and ICM logs. VG Config attached reference.




Ritesh Desai Tue, 09/27/2016 - 09:25
User Badges:

Thanks for taking above too read. Issue is been resolved. In contact center scenario, SIP trunk between CVP and CUCM was missing.


regards,

Ritesh Desai.

Antoine Thiebault Tue, 03/14/2017 - 08:50
User Badges:

Hi,


I had the same issue as you.

error 503 with warning like this :

Warning: 399 Server name "Unable to find a device handler for the request received on port 



The issue come from on my gateway i have "server-group"  with  IP of sub pair.

But on my CUCM SIP trunkl, i have DEVICE POOL with other SUB pair for manage call of this trink.


When i update server-group with right ip adress. every wsorking good !!!


Nicholas Matthews Wed, 09/30/2009 - 05:21
User Badges:
  • Red, 2250 points or more

This occurs when the source IP address that is sending the SIP INVITE does not exist as a SIP trunk in CUCM. You may have never created it, or the IP address may not be the one that is in use. Check bind commands for gateways, etc.



-nick

paul.omahony Wed, 09/30/2009 - 23:12
User Badges:

Hi nick,


Thanks for the advice I set up a SIP trunk for my source ip and I got one phone to ring, when I send the click to dial request.

However I'm trying to get one phone to ring the other phone but I've had no luck so far. Is that still a SIP trunk issue?




Nicholas Matthews Thu, 10/01/2009 - 04:31
User Badges:
  • Red, 2250 points or more

It could be a calling search space / partition issue - it doesn't sound like a SIP trunk issue.



-nick

crush5454 Tue, 06/11/2013 - 15:13
User Badges:

This was exactly my issue. I have dual SIP gateways in an HSRP group connected to a third party IVR. When the IVR sends a refer message to move a call from queue to an available agent the CUBE invites the CUCM via the SIP trunk. I had the trunk configured with the VIP address instead of the actual box address of the active router. So I was receiving the same error message.


Based on Nicholas' message above I decided to add the actual active router and standby to the SIP trunk CUCM side, and now the error is resolved. Great job Nick!


Jonathan

Ahamed Razzan Wed, 02/17/2016 - 01:35
User Badges:

I had this issue and your solution worked for me. I have missed one subscribers IP on SIP trunk.

Thank you.

csco11391130 Wed, 10/07/2009 - 14:06
User Badges:

Just in media gateway i did in


voice service voip

sip

bind all source-interface Loopback0


where the loopback0 had the ip source of trunk.


with debug ccsip message


you can watch the ip local of sip trunk, and the dial-peer you put the ip remote

robloeber Thu, 04/26/2012 - 20:02
User Badges:

This is awesome and helped me fix an issue I was having.


thanks!

toormehdi Wed, 08/03/2011 - 15:13
User Badges:

You can experience this problem if the only IP of CCM you are pointing to in the SIP dialpeer is not the primary CCM in the call manager group for the device pool you have applied to the SIP trunk.


Ensure that either the CCM you are pointing the dialpeer  to is primary in the CCM group or you have multiple dial-peers with different preference as per the CCM group on the other side.


Please rate the post

monaydi01 Sat, 01/18/2014 - 07:38
User Badges:

Hello friends, I have a problem that I have long time unable to solve.

My problem is that all outgoing calls go right from the Cisco CallManager, but the starters never come.


I have a SIP Trunk contracted with a company of you tell me that this is all right but not from the CUCM.


They tell me that to them reaches them the following error from my CUCM.


Got SIP response 503 "Service Unavailable" back from

82.158.145.110:5060



I have been monitoring my CUCM and my log get this data.


16:36:56.668701 IP CUCM-PUBS.LUNPAT.sip > sts2.globaltel.es.sip: SIP, length: 385

16:37:16.528479 IP CUCM-PUBS.LUNPAT.sip > sts2.globaltel.es.39418: . ack 4221 win 301

16:37:16.528580 IP CUCM-PUBS.LUNPAT.sip > sts2.globaltel.es.39418: . ack 4221 win 301

16:37:16.530151 IP CUCM-PUBS.LUNPAT.sip > sts2.globaltel.es.39418: P 3272:3762(490) ack 4221 win 301

16:37:16.530243 IP CUCM-PUBS.LUNPAT.sip > sts2.globaltel.es.39418: P 3272:3762(490) ack 4221 win 301

16:37:42.366311 IP CUCM-PUBS.LUNPAT.sip > v1.globaltel.es.sip: SIP, length: 374

16:37:42.366466 IP CUCM-PUBS.LUNPAT.sip > v1.globaltel.es.sip: SIP, length: 374

16:37:42.366637 IP CUCM-PUBS.LUNPAT.sip > sts2.globaltel.es.sip: SIP, length: 376

16:37:42.366711 IP CUCM-PUBS.LUNPAT.sip > sts2.globaltel.es.sip: SIP, length: 376

16:37:42.366841 IP CUCM-PUBS.LUNPAT.sip > vcolt900.voz.com.sip: SIP, length: 373

16:37:42.366924 IP CUCM-PUBS.LUNPAT.sip > vcolt900.voz.com.sip: SIP, length: 373

16:37:42.372169 IP CUCM-PUBS.LUNPAT.sip > sts2.globaltel.es.sip: SIP, length: 384

16:37:42.372255 IP CUCM-PUBS.LUNPAT.sip > sts2.globaltel.es.sip: SIP, length: 384

16:37:42.375964 IP CUCM-PUBS.LUNPAT.sip > v1.globaltel.es.sip: SIP, length: 370

16:37:42.376073 IP CUCM-PUBS.LUNPAT.sip > v1.globaltel.es.sip: SIP, length: 370

16:37:42.875039 IP CUCM-PUBS.LUNPAT.sip > sts2.globaltel.es.sip: SIP, length: 376

16:37:42.875161 IP CUCM-PUBS.LUNPAT.sip > sts2.globaltel.es.sip: SIP, length: 376

16:37:42.891305 IP CUCM-PUBS.LUNPAT.sip > sts2.globaltel.es.sip: SIP, length: 384

16:37:42.891421 IP CUCM-PUBS.LUNPAT.sip > sts2.globaltel.es.sip: SIP, length: 384

16:37:43.879764 IP CUCM-PUBS.LUNPAT.sip > sts2.globaltel.es.sip: SIP, length: 376

16:37:43.879900 IP CUCM-PUBS.LUNPAT.sip > sts2.globaltel.es.sip: SIP, length: 376

16:37:43.905105 IP CUCM-PUBS.LUNPAT.sip > sts2.globaltel.es.sip: SIP, length: 384

16:37:43.905215 IP CUCM-PUBS.LUNPAT.sip > sts2.globaltel.es.sip: SIP, length: 384

16:37:45.895631 IP CUCM-PUBS.LUNPAT.sip > sts2.globaltel.es.sip: SIP, length: 376

16:37:45.895746 IP CUCM-PUBS.LUNPAT.sip > sts2.globaltel.es.sip: SIP, length: 376

16:37:45.919616 IP CUCM-PUBS.LUNPAT.sip > sts2.globaltel.es.sip: SIP, length: 384


A greeting and thank you very much before hand.


[email protected]

Actions

This Discussion