Trying to register cisco 7942G with Freepbx End Point Manager failed

faisalkhan · March 16, 2022, 8:51pm

hi Team,

trying to register the Cisco 7942G with EPM Module but phone is not registering.

Please see the traces below:

1 0.000000000 Cisco_e2:5d:f0 ->              ARP 62 Who has 172.16.10.20?  Tell 172.16.17.211
  2 0.000010300 Microsof_0a:9f:10 ->              ARP 44 172.16.10.20 is at 00:15:5d:0a:9f:10
  3 0.000414801 172.16.17.211 -> 172.16.10.20 TFTP 75 Read Request, File: CTLSEP1CAA07E25DF0.tlv, Transfer type: octet
  4 0.001487403 172.16.10.20 -> 172.16.17.211 TFTP 63 Error Code, Code: File not found, Message: File not found
  5 0.078462963 172.16.17.211 -> 172.16.10.20 TFTP 76 Read Request, File: SEP1CAA07E25DF0.cnf.xml, Transfer type: octet
  6 0.079411865 172.16.10.20 -> 172.16.17.211 TFTP 560 Data Packet, Block: 1
  7 0.080297767 172.16.17.211 -> 172.16.10.20 TFTP 62 Acknowledgement, Block: 1
  8 0.080319767 172.16.10.20 -> 172.16.17.211 TFTP 560 Data Packet, Block: 2
  9 0.081094869 172.16.17.211 -> 172.16.10.20 TFTP 62 Acknowledgement, Block: 2
 10 0.081114569 172.16.10.20 -> 172.16.17.211 TFTP 560 Data Packet, Block: 3
 11 0.081883171 172.16.17.211 -> 172.16.10.20 TFTP 62 Acknowledgement, Block: 3
 12 0.081902371 172.16.10.20 -> 172.16.17.211 TFTP 560 Data Packet, Block: 4
 13 0.083098473 172.16.17.211 -> 172.16.10.20 TFTP 62 Acknowledgement, Block: 4
 14 0.083117073 172.16.10.20 -> 172.16.17.211 TFTP 560 Data Packet, Block: 5
 15 0.083872775 172.16.17.211 -> 172.16.10.20 TFTP 62 Acknowledgement, Block: 5
 16 0.083891475 172.16.10.20 -> 172.16.17.211 TFTP 560 Data Packet, Block: 6
 17 0.084630876 172.16.17.211 -> 172.16.10.20 TFTP 62 Acknowledgement, Block: 6
 18 0.084648576 172.16.10.20 -> 172.16.17.211 TFTP 560 Data Packet, Block: 7
 19 0.085404878 172.16.17.211 -> 172.16.10.20 TFTP 62 Acknowledgement, Block: 7
 20 0.085423678 172.16.10.20 -> 172.16.17.211 TFTP 560 Data Packet, Block: 8
 21 0.086187180 172.16.17.211 -> 172.16.10.20 TFTP 62 Acknowledgement, Block: 8
 22 0.086210180 172.16.10.20 -> 172.16.17.211 TFTP 560 Data Packet, Block: 9
 23 0.086969481 172.16.17.211 -> 172.16.10.20 TFTP 62 Acknowledgement, Block: 9
 24 0.086987781 172.16.10.20 -> 172.16.17.211 TFTP 560 Data Packet, Block: 10
 25 0.087752083 172.16.17.211 -> 172.16.10.20 TFTP 62 Acknowledgement, Block: 10
 26 0.087770383 172.16.10.20 -> 172.16.17.211 TFTP 560 Data Packet, Block: 11
 27 0.088525284 172.16.17.211 -> 172.16.10.20 TFTP 62 Acknowledgement, Block: 11
 28 0.088553584 172.16.10.20 -> 172.16.17.211 TFTP 560 Data Packet, Block: 12
 29 0.089299386 172.16.17.211 -> 172.16.10.20 TFTP 62 Acknowledgement, Block: 12
 30 0.089320486 172.16.10.20 -> 172.16.17.211 TFTP 560 Data Packet, Block: 13
 31 0.090118388 172.16.17.211 -> 172.16.10.20 TFTP 62 Acknowledgement, Block: 13
 32 0.090142788 172.16.10.20 -> 172.16.17.211 TFTP 472 Data Packet, Block: 14 (last)
 33 0.090869689 172.16.17.211 -> 172.16.10.20 TFTP 62 Acknowledgement, Block: 14
 34 4.344664632 172.16.17.211 -> 172.16.10.20 TFTP 86 Read Request, File: English_United_Kingdom/mk-sip.jar, Transfer type: octet
 35 4.345833234 172.16.10.20 -> 172.16.17.211 TFTP 63 Error Code, Code: File not found, Message: File not found
 36 4.582169126 172.16.17.211 -> 172.16.10.20 TFTP 66 Read Request, File: /g3-tones.xml, Transfer type: octet
 37 4.583262728 172.16.10.20 -> 172.16.17.211 TFTP 63 Error Code, Code: File not found, Message: File not found
 38 5.013550222 Microsof_0a:9f:10 ->              ARP 44 Who has 172.16.17.211?  Tell 172.16.10.20
 39 5.013995823 Cisco_e2:5d:f0 ->              ARP 62 172.16.17.211 is at 1c:aa:07:e2:5d:f0
 40 5.507079548 172.16.17.211 -> 172.16.10.20 SIP 920 Request: REGISTER sip:172.16.10.20 | 
 41 5.507273849 172.16.10.20 -> 172.16.17.211 SIP 607 Status: 401 Unauthorized    (0 bindings) | 
 42 5.581445503 172.16.17.211 -> 172.16.10.20 TFTP 78 Read Request, File: dialplan-1CAA07E25DF0.xml, Transfer type: octet
 43 5.582579405 172.16.10.20 -> 172.16.17.211 TFTP 168 Data Packet, Block: 1 (last)
 44 5.590234321 172.16.17.211 -> 172.16.10.20 TFTP 62 Acknowledgement, Block: 1
 45 5.984224640 172.16.17.211 -> 172.16.10.20 SIP 920 Request: REGISTER sip:172.16.10.20 | 
 46 5.984361040 172.16.10.20 -> 172.16.17.211 SIP 607 Status: 401 Unauthorized    (0 bindings) | 
 47 6.973906497 172.16.17.211 -> 172.16.10.20 SIP 920 Request: REGISTER sip:172.16.10.20 | 
 48 6.974051198 172.16.10.20 -> 172.16.17.211 SIP 607 Status: 401 Unauthorized    (0 bindings) | 
 49 8.983899876 172.16.17.211 -> 172.16.10.20 SIP 920 Request: REGISTER sip:172.16.10.20 | 
 50 8.984052376 172.16.10.20 -> 172.16.17.211 SIP 607 Status: 401 Unauthorized    (0 bindings) | 
 51 12.974195970 172.16.17.211 -> 172.16.10.20 SIP 920 Request: REGISTER sip:172.16.10.20 | 
 52 12.974358171 172.16.10.20 -> 172.16.17.211 SIP 607 Status: 401 Unauthorized    (0 bindings) | 
 53 16.964657866 172.16.17.211 -> 172.16.10.20 SIP 920 Request: REGISTER sip:172.16.10.20 | 
 54 16.964857066 172.16.10.20 -> 172.16.17.211 SIP 607 Status: 401 Unauthorized    (0 bindings) | 
 55 20.984698522 172.16.17.211 -> 172.16.10.20 SIP 920 Request: REGISTER sip:172.16.10.20 | 
 56 20.984820322 172.16.10.20 -> 172.16.17.211 SIP 607 Status: 401 Unauthorized    (0 bindings) | 
 57 24.975109117 172.16.17.211 -> 172.16.10.20 SIP 920 Request: REGISTER sip:172.16.10.20 | 
 58 24.975246918 172.16.10.20 -> 172.16.17.211 SIP 607 Status: 401 Unauthorized    (0 bindings) | 
 59 28.965506612 172.16.17.211 -> 172.16.10.20 SIP 920 Request: REGISTER sip:172.16.10.20 | 
 60 28.965623213 172.16.10.20 -> 172.16.17.211 SIP 607 Status: 401 Unauthorized    (0 bindings) | 
 61 32.985525469 172.16.17.211 -> 172.16.10.20 SIP 920 Request: REGISTER sip:172.16.10.20 | 
 62 32.985654169 172.16.10.20 -> 172.16.17.211 SIP 607 Status: 401 Unauthorized    (0 bindings) | 
^C62 packets captured

faisalkhan · March 17, 2022, 1:13pm

Hi Sangoma team,

any help regarding this commercial module not able to let us register the phones.

Stewart1 · March 17, 2022, 2:01pm

I don’t believe that the issue is related to EPM. If using a pjsip extension, confirm that Force rport and Rewrite Contact are set to No. For chan_sip, NAT set to Never.

Also, confirm that in Asterisk SIP settings, External Address and Local Networks are correctly set.

If you still have trouble, paste the pjsip logger (or sip debug) output for a registration attempt.

faisalkhan · March 17, 2022, 3:37pm

50 8.984052376 172.16.10.20 -> 172.16.17.211 SIP 607 Status: 401 Unauthorized    (0 bindings) | 
 51 12.974195970 172.16.17.211 -> 172.16.10.20 SIP 920 Request: REGISTER sip:172.16.10.20 | 
 52 12.974358171 172.16.10.20 -> 172.16.17.211 SIP 607 Status: 401 Unauthorized    (0 bindings) | 
 53 16.964657866 172.16.17.211 -> 172.16.10.20 SIP 920 Request: REGISTER sip:172.16.10.20 | 
 54 16.964857066 172.16.10.20 -> 172.16.17.211 SIP 607 Status: 401 Unauthorized    (0 bindings) | 
 55 20.984698522 172.16.17.211 -> 172.16.10.20 SIP 920 Request: REGISTER sip:172.16.10.20 | 
 56 20.984820322 172.16.10.20 -> 172.16.17.211 SIP 607 Status: 401 Unauthorized    (0 bindings) | 
 57 24.975109117 172.16.17.211 -> 172.16.10.20 SIP 920 Request: REGISTER sip:172.16.10.20 | 
 58 24.975246918 172.16.10.20 -> 172.16.17.211 SIP 607 Status: 401 Unauthorized    (0 bindings) | 
 59 28.965506612 172.16.17.211 -> 172.16.10.20 SIP 920 Request: REGISTER sip:172.16.10.20 | 
 60 28.965623213 172.16.10.20 -> 172.16.17.211 SIP 607 Status: 401 Unauthorized    (0 bindings) | 
 61 32.985525469 172.16.17.211 -> 172.16.10.20 SIP 920 Request: REGISTER sip:172.16.10.20 | 
 62 32.985654169 172.16.10.20 -> 172.16.17.211 SIP 607 Status: 401 Unauthorized    (0 bindings) | 
^C62 packets captured

Check this out Register attempt

however in the logs above it’s requesting for some files which are missing.

lgaetz · March 17, 2022, 3:42pm

I have zero cisco experience, but I recall reading on many occasions here that some of these old legacy devices had a SIP Secret length of 8 chars, considerably fewer than the defaults for freepbx.

billsimon · March 17, 2022, 3:45pm

The missing files are not a problem. The phone is getting the main file it needs which is the SEPxxx.cnf file.

The phone you’re using will also provision over HTTP on port 6970 - you may want to try that instead if you are having problems with TFTP.

Pay attention to @Stewart1 suggestion - you need to turn off the NAT handling for these phones.

faisalkhan · March 21, 2022, 1:44pm

thanks guys.

you are super heroes… I just changed the Nat settings to never and it worked like a charm.

system · March 28, 2022, 1:45pm

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.