09-29-2009 09:45 PM - edited 03-15-2019 05:09 AM
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:2003@10.36.134.137:5060>;tag=1
Content-Length: 0
To: <sip:2003@10.36.134.124:5060>;tag=1181960151
Contact: <sip:2003@10.36.134.124:5060;transport=tcp>
Call-ID: 1254223590633-0006@10.36.134.137
Via: SIP/2.0/TCP 10.36.134.137:5060
CSeq: 1 REFER
I'd appreciate any help.
Cheers
08-16-2013 07:36 PM
Check
Run On All Active Unified CM Nodes
On the SIP Trunk...
10-18-2018 07:23 AM
12-22-2019 05:21 AM
that solved my issue too,many thanks
01-18-2014 07:38 AM
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
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.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide