Looks like layer 2/3 needs checking. A capture at your internet egress point could be useful Try telnet from the router to the sip itsp IP:port to check. ... View more

Thought it was going out via ADSL int? Can you do a trace? You need to capture the traffic and confirm you're receiving replies. It's especially important if you're natting. Post back once you captured the replies from itsp. It's impossible to help without that info and your previous captures don't show any received sip. Debug ccsip messages Good luck ... View more

Ok seems there a few things going on here and confusing the result.    1. Firstly, by default your "ephone-dn" will all try to register against the SIP registrar. To fix this, go into each ephone-dn and add " no-reg primary" after the ephone "number xxxx". This will stop your list of internal extensions trying to register against the ITSP and failing.    2. You don't really need "voice register dn 1". To make things simpler you can remove this until you have registration working and put it back later if you feel you need it.    3. Dont really need this either" voice register pool 1 id mac 0013.C4AA.CF8B type 7960 number 1 dn 1 username 1057300 password xxxx   4. For the sip-ua config, I have a 2900 so the config is slightly different. Try this for the 2800:   sip-ua credentials username 1057300 password [sip pass] realm telecube.com.au authentication username 1057300 password [sip pass] realm telecube.com.au registrar ipv4:103.93.71.35 expires 60 sip-server ipv4:103.93.71.35 retry invite 2 retry register 2   Then, run the "debug ccsip messages" and make sure you're actually getting responses back. I don't see any replies at all in any of your captures. What firewall do you have? Can you turn on SIP ALG because it's needed to rewrite the 192.168.5.1 IP address into the WAN IP within the SIP packet. The ITSP might be trying to speak to 192.168.5.1 and this might be why you;re not seeing any reply traffic because ALG is off.  ... View more

Hi,  Something is up with your captures as it's incomplete. I only see one reply from the ITSP there, however it may have the missing info we need. Try this config and then run the captures again:   ** just add your SIP registration password. I've added the username and the realm **   sip-ua credentials username 1057300 password [sip pass] realm telecube.com.au registrar 1 ipv4:103.93.71.35 expires 60 refresh-ratio 20 auth-realm telecube.com.au Post back soon. ... View more

Pls run the debug, attempt registration and then capture all the SIP packets and post back.  ... View more

It's good you are able to capture the registration packet. You need to capture the response from the ITSP as it will give the reason for the rejection.    Run:  debug ccsip messages    and then configure sip-ua with the "registrar 1 ........" config so that it triggers registration after you enable the debug. Post back, I'll have a look :)     ... View more

run this command and reply with the output:   show sip register status ... View more

Is this for a lab? Give this a go:   [sip registration username] = the username you use for sip registration [sip pass] = the password for sip registration [sip domain.com] = the sip realm for registration. If you dont have it, you can try without or put in something dummy and then take a debug to see what the ITSP is sending.  sip.itsp.com = your ITSP registration url   sip-ua credentials username [sip registration username] password [sip pass] realm [sip domain.com] registrar 2 dns:sip.itsp.com expires 60 refresh-ratio 20 auth-realm [sip domain.com]   Then you can check with: show sip register status ... View more

Normally, the voice gateway registers with the ITSP. In your case, the gateway is also the phone system = CUCME. So you would register the phone to CUCME and simulteneously register CUCME to the ITSP. This is the normal way of doing things. Then you have the ability to add more phones on the LAN without changing the CUCME <-> ITSP config. ... View more

I think it is possible. I saw a write up somewhere about someone doing this with a 9971 phone direct to the ITSP.    The Cisco phone gets it's configuration and firmware from TFTP. I suggest that you research the boot up process of a Cisco IP phone (SIP) because it will give you the information you need to achieve what you're looking to do. But basically, the phone gets powered up, it attempts to get DHCP IP and the DHCP server provides a TFTP server within the DHCP OFFER. Once the phone has that info, it requests a specific file from the TFTP server which is its config file. You will need to create this file and save on the TFTP server. ... View more

I disagree with you on the cucm 12 upgrade complexity. I found it pretty straight forward. Yes licensing has changed but IMO it's more simple in 12. To get to 12, you just export the license request from PLM and send it to the Cisco licensing team to convert your licenses and add them to your cisco.com smart account. Then you upgrade CUCM. When you log in to CUCM you then use the gui to register the CUCM pub with the smart account and the licenses are sync. Not really much more to it than that.  Must of course read the upgrade guide. There is not much thorough info there about the licenses, it doesnt tell your exactly what to do. So to save any confusion on my part I just emailed the licensing team with my intent and the license request file.  ... View more