« Back to Technical Questions

App cannot register

Combination View Flat View Tree View
Threads [ Previous | Next ]
toggle
Test application fails to register, apparently because it sens instead of "CME_provider" in SIP Contact:  header.
Router configuration is exactly as per documentation
Application:
           
 
pCfg = new CMEProviderConfig("config.txt");
 
CMEProvider p = ProviderManager.getProvider(pCfg,"CME_provider");       
 
if (p == null) {
           
 
System.out.println(">>>>>Sample code: ++++++ provider is null ++++");
            System.exit(0);
            return;
        }        
        p.addListener(new CMEProviderListenerImpl());
        if (p.start()) {
            System.out.println(">>>>>Sample code: ++++++ provider started successfully ++++++ ");
} else {
            System.out.println(">>>>>Sample code: ++++++ provider is not started ++++++ ");
        }
 
SIP trace:
Dec 13 01:17:11.553: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
REGISTER sip:192.168.1.50:0;transport=tcp SIP/2.0
Via: SIP/2.0/TCP 192.168.1.101:5060;branch=z9hG4bKmyUGazcgSmhJtvEQ.1G.Wg~~0
Max-Forwards: 70
To: <sip:sampleapp@192.168.1.50>
From: <sip:sampleapp@192.168.1.50>;tag=dsb401b205
Call-ID: 13553614271871@192.168.1.50
CSeq: 1 REGISTER
Content-Length: 0 Contact: <sip:null@192.168.1.101:5060;transport=tcp>;expires=120    <<<< SHOULD BE sip:CME_provider X-cisco-session-server: sampleapp
 
 
Dec 13 01:17:11.553: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 100 Trying
Via: SIP/2.0/TCP 192.168.1.101:5060;branch=z9hG4bKmyUGazcgSmhJtvEQ.1G.Wg~~0
From: <sip:sampleapp@192.168.1.50>;tag=dsb401b205
To: <sip:sampleapp@192.168.1.50>
Date: Thu, 13 Dec 2012 01:17:11 GMT
Call-ID: 13553614271871@192.168.1.50
Server: Cisco-SIPGateway/IOS-12.x
CSeq: 1 REGISTER
Content-Length: 0
 
 
Dec 13 01:17:11.557: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 400 Bad Request - 'Malformed/Missing URL'
Via: SIP/2.0/TCP 192.168.1.101:5060;branch=z9hG4bKmyUGazcgSmhJtvEQ.1G.Wg~~0
From: <sip:sampleapp@192.168.1.50>;tag=dsb401b205
To: <sip:sampleapp@192.168.1.50>;tag=9030EC-233C
Date: Thu, 13 Dec 2012 01:17:11 GMT
Call-ID: 13553614271871@192.168.1.50
Server: Cisco-SIPGateway/IOS-12.x
CSeq: 1 REGISTER
Content-Length: 0
 
Why the Contact: header is not being set as per command in bold ?

RE: App cannot register
Answer
12/13/12 9:56 PM as a reply to Paolo Bevilacqua.
Any idea? I've managed to run the cisco Sample application and it behaves exactly the same.
SIP phones registers OK, so I know basic config is correct.
I've tried to enable various debuga but none revelas anything.    

RE: App cannot register
Answer
12/14/12 4:59 AM as a reply to Paolo Bevilacqua.
Hi Paolo,
 
please collect logs by enabling below debugs.
debug ccsip message
debug cti all
 
Thanks,
Raghavendra

RE: App cannot register
Answer
12/14/12 11:11 AM as a reply to Raghavendra Gutty Veeranagappa.
As indicated above:
 
debug ccsip message is shown in first post.
 
debug cti output does not produce any output.

RE: App cannot register
Answer
12/17/12 12:43 AM as a reply to Paolo Bevilacqua.
I've configured another CME, this one with 9.1, for testing.
Same identical results, no matter what i try I get always:  
 
SIP/2.0 400 Bad Request - 'Malformed/Missing URL'  

RE: App cannot register
Answer
12/17/12 6:23 AM as a reply to Paolo Bevilacqua.
Hi Paolo,
 
i am not sure why your getting 400 bad request, please use our sample code(UCXSI Sample codes and Readme 1.0.1) mentioned in documentation section. please follow the steps given in the readme document to configure and run the sample.
 
Thanks,
Raghavendra

RE: App cannot register
Answer
12/17/12 9:49 AM as a reply to Raghavendra Gutty Veeranagappa.
 
This is the problem: I'm using Cisco sample code, and the routers are configured exactly as per document.

RE: App cannot register
Answer
12/18/12 7:14 AM as a reply to Paolo Bevilacqua.
Hi Paolo,
please check below configs are configured in router.
Configuration on CME Router
! Defining XML Transport Parameters
ip http server
ixi transport http
  response size 64
  no shutdown
  request outstanding 1
  request timeout 60
! Defining XML Application Parameters
ixi application cme
  no shutdown 
! Defining Authentication for XML Access
telephony-service
  xml user cisco password cisco 15
! Session Server configuration
voice register session-server  1
  keepalive 60
  register-id OCT_CME
  cti-aware
!
voice service voip
   no cti shutdown 
   sip
      registrar server expires max 120 min 60
       !
       voice register global
         mode cme 
       ! Ephone-dn: Sample Configuration
       ephone-dn  1
          number 5001
          cti watch   
       !
       ephone-dn  2  dual-line
          number 5002
          cti watch   
          transfer-mode blind 
       !
       ephone-dn  3  dual-line
           number 5003
           cti watch
Thanks,
Raghavendra

RE: App cannot register
Answer
12/18/12 10:25 AM as a reply to Raghavendra Gutty Veeranagappa.
As indicated above already:  
My router configuration is identical to the examples given.  
Yet, sample application fails in registering a provider and I cannot move on with my development. 

RE: App cannot register
Answer
12/18/12 10:35 AM as a reply to Paolo Bevilacqua.
which IOS version your using.
Thanks,
Raghavendra

RE: App cannot register
Answer
12/18/12 11:38 AM as a reply to Raghavendra Gutty Veeranagappa.
Above I have indicated already two CME versions I have tested with identical results:
One is 15.1(4)M5, the other 15.2(3)T

RE: App cannot register
Answer
12/23/12 3:52 PM as a reply to Raghavendra Gutty Veeranagappa.
Raghavendra Gutty Veeranagappa:
which IOS version your using.
Thanks,
Raghavendra

Can someone post a complied .jar for the sample app? I want to find out where from this problem is originating.
 
 

Paolo:
It looks like your port is set wrong: REGISTER sip:192.168.1.50:0;transport=tcp SIP/2.0
I have been playing with this tonight, and CME seems VERY sensitive to what you have in your headers/request lines.

Daniel Placek:
Paolo:
It looks like your port is set wrong: REGISTER sip:192.168.1.50:0;transport=tcp SIP/2.0
I have been playing with this tonight, and CME seems VERY sensitive to what you have in your headers/request lines.

You are correct. I have fixed the configuration file, and now the application registers succesfully. I still have a long way before getting someting useful out of all this.