[prev in list] [next in list] [prev in thread] [next in thread] 

List:       asterisk-dev
Subject:    Re: [Asterisk-Dev] SEPDefault.cnf for 12SP/30VIP Discoveries
From:       "Paul Cadach" <paul () odt ! east ! telecom ! kz>
Date:       2004-04-30 0:23:13
Message-ID: 000601c42e49$54da4ee0$b78313d4 () private3se6v3w
[Download RAW message or body]

Hi,


Mostly SEPDefault.cnf looks like sequence of
<parameter code - 2 bytes> [<parameter value - variable length>]
where <parameter code> in:
<01> <01> - ASCIIZ of DNS name of CCM;
<01> <02> - IP address of CCM (value is 4 bytes, highest octed comes first);
<01> <03> - TCP port of SCCP (value is 4 bytes in intel form, low byte comes first);
<04> <07> - some sort of URL prepended by <00> byte (or it is some sort of empty \
ASCIIZ string), length of URL rounded to 4 bytes with zeroes;
<01> <FF> - end of SEPDefault.cnf (value isn't possible).

Load file isn't available at SEPDefault.cnf, phone asks CCM about firmware version by \
SCCP protocol at registration sequence, and this request handled by \
chan_skinny/chan_sccp internally.



WBR,
Paul.

----- Original Message -----
From: "Jennifer Archer" <ajener@qwest.net>
To: <asterisk-dev@lists.digium.com>
Sent: Friday, April 30, 2004 2:25 AM
Subject: [Asterisk-Dev] SEPDefault.cnf for 12SP/30VIP Discoveries


> (copied from lambda-solutions bug tracker)
> here it is in "hex dump" format: of sepdefault.cnf
> 
> 0000000 | 01 01 00 01 02 50 46 41 | . . . . . P F A
> 0000008 | 11 01 03 d0 07 00 00 04 | . . . . . . . .
> 0000010 | 07 00 68 74 74 70 3a 2f | . . h t t p : /
> 0000018 | 2f 38 30 2e 37 30 2e 36 | / 8 0 . 7 0 . 6
> 0000020 | 35 2e 31 37 2f 6c 6f 63 | 5 . 1 7 / l o c
> 0000028 | 61 6c 64 69 72 65 63 74 | a l d i r e c t
> 0000030 | 6f 72 79 00 00 00 01 ff | o r y . . . . .
> 
> when i let my phone use that SEPDefault.cnf file, it tries to
> connect to ip address 80.70.65.17, which is hex 50 46 41 11. you
> can see those bytes starting at offset 5.
> 
> and it looks like the call manager port number (2000, or 0xd0 0x07)
> is there at offset B.
> 
> also, you can see a URL starting at offset 0x12:
> "http://80.70.65.17/localdirectory"
> (i don't know what that's for.)
> 
> so, a struct for the file might look something like this:
> 
> struct SEP
> {
> char unknown0[5];
> int32_t ipAddress;
> char unknown9[2];
> int16_t port;
> char unknownD[5];
> char url[36];
> char unknown36[2];
> } __attribute__((packed));
> 
> Question! Where is the encapsulated version info for the load file in the
> hex dump? something like P002F300.bin would be a load file for a skinny
> phone from cisco 12sp/30vip era.
> 
> _______________________________________________
> Asterisk-Dev mailing list
> Asterisk-Dev@lists.digium.com
> http://lists.digium.com/mailman/listinfo/asterisk-dev
> To UNSUBSCRIBE or update options visit:
> http://lists.digium.com/mailman/listinfo/asterisk-dev
> 


[prev in list] [next in list] [prev in thread] [next in thread]