Topic: chan_sccp on SAIL

[Franco]

Hi,
Has anyone adventured in adding chan_sccp to Sail?
I was reading this thread and since I have a 7960 with the SARK logo I'm thinking on try it.

[SARK devs]

Hello Franco

You would have to create the Skinny hooks yourself...

First you would need to define chan_sccp (using the references you mentioned).

Then you would need to create a custom app (with a span of both) to dial your sccp phone...
Lets say the phone is at ext 5000 then you would need a dial something like

exten=>5000,1,dial(sccp/5000)

That should get you going.  Let us know how you get on.

Kind Regards

S
 

[Franco]

Ok, got this working!
So far it seems a lot better than SIP, as I can use some sort of BLF on side keys of the phone, direct dial, directory, etc.

Code: [Select]

v4*CLI> sccp show version
Skinny Client Control Protocol (SCCP). Release: TRUNK - 1365 (built by 'root' on '2010-03-13 17:07:17 UTC')
v4*CLI> sccp show devices
v4*CLI>
NAME                                     ADDRESS              MAC              Reg. State
======================================== ==================== ================ ==========
7156                                         172.16.0.161         SEP00179592DA9E  OK       
v4*CLI>

The only caveat so far, working with sail, is that anytime I need to edit/add/remove any extension, the system will wipe off all of my files in the tftpboot. Even thou I still have another cisco phone working with SIP.

[SARK devs]

Hi Franco,

The tftp mechanism is tied quite tightly to the SIP phones.  However, you should be able to create a provisioning file for your new phone by using the descriptor object.  It will be a little clunky but it should work...  Go to  ip devices panel and  click "New Device".  From the drop down choose "Descriptor".  A descriptor is a custom file type that can be anything you want.  So now - name it EXACTLY as the phone will wish to find it on the tftp server - e.g. SEP{macaddress}, or whatever the SCCP phone looks for.   OK, now you can load anything you like into the file window (Cisco proprietary or XML based provisioning) and SAIL will manage it for you.  Click commit and you are done.  You will need to create one file for each phone but it should work fine.  SAIL also modifies the DHCP server to serve Option 150 - which is the Cisco equivalent of DHCP 66, so your phone should be able to find the file automatically from boot up.

Kind Regards

S     

[Franco]

Now why didn't I think of it?
 

Thanks a lot S, that did it.