[Asterisk-Dev] SEPDefault.cnf for 12SP/30VIP Discoveries

Jennifer Archer ajener at qwest.net
Thu Apr 29 12:25:28 MST 2004


(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.




More information about the asterisk-dev mailing list