If you can help, I would really appreciate it. I’ve been struggling with this a lot.
I want to register a Cisco 7975G in FreePBX using the SEPxxxxxx.xml file method. I have tried many scripts, and now the phone shows the number and name on the screen, but it stays stuck on “Registering” and does not proceed further.
I created this configuration for SIP, and the phone is also running SIP firmware.
If you know the correct method or can guide me to fix this issue, I would be very grateful.
On Tuesday 10 March 2026 at 10:28:58, qfaizi wrote:
the phone shows the number and name on the screen, but it stays stuck on
“Registering” and does not proceed further.
At least show us a SIP dialogue as the phone is trying to register so we can
see what it is sending and how Asterisk is responding.
Antony.
–
The Free Software Foundation Europe was formed on this day in 2001
<— Transmitting SIP request (444 bytes) to UDP:172.30.30.12:5060 —>
OPTIONS sip:100@172.30.30.12:5060;user=phone SIP/2.0
Via: SIP/2.0/UDP 188.92.255.132:5060;rport;branch=z9hG4bKPjecb157a4-e503-4d2d-ad39-17bd74efb4c8
From: sip:100@172.30.31.254;tag=a2e4835f-82db-443a-aa60-d9b0217223cc
To: sip:100@172.30.30.12;user=phone
Contact: sip:100@188.92.255.132:5060
Call-ID: 47b1e1df-1799-49a1-af25-63d8ba646c99
CSeq: 57943 OPTIONS
Max-Forwards: 70
User-Agent: FPBX-17.0.28(22.7.0)
Content-Length: 0
<— Received SIP response (1347 bytes) from UDP:172.30.30.12:5060 —>
SIP/2.0 200 OK
Via: SIP/2.0/UDP 188.92.255.132:5060;rport;branch=z9hG4bKPjecb157a4-e503-4d2d-ad39-17bd74efb4c8;received=172.30.31.254
From: sip:100@172.30.31.254;tag=a2e4835f-82db-443a-aa60-d9b0217223cc
To: sip:100@172.30.30.12;user=phone;tag=002f5c6164c012773f3bf092-7d6478ee
Call-ID: 47b1e1df-1799-49a1-af25-63d8ba646c99
Session-ID: e57abede00105000a000002f5c6164c0;remote=00000000000000000000000000000000
Date: Tue, 10 Mar 2026 11:50:26 GMT
CSeq: 57943 OPTIONS
Server: Cisco-CP7821/12.6.1
Allow: ACK,BYE,CANCEL,INVITE,NOTIFY,OPTIONS,REFER,REGISTER,UPDATE
Allow-Events: kpml,dialog,refer
Accept: application/sdp,multipart/mixed,multipart/alternative
Accept-Encoding: identity
Accept-Language: en
Supported: replaces,join,sdp-anat,norefersub,resource-priority,extended-refer,X-cisco-callinfo,X-cisco-serviceuri,X-cisco-escapecodes,X-cisco-service-control,X-cisco-srtp-fallback,X-cisco-monrec,X-cisco-config,X-cisco-sis-7.0.0
Content-Length: 300
Content-Type: application/sdp
Content-Disposition: session;handling=optional
v=0
o=Cisco-SIPUA 23546 0 IN IP4 172.30.30.12
s=SIP Call
t=0 0
m=audio 0 RTP/AVP 0 8 116 18 101
b=TIAS:64000
a=rtpmap:0 PCMU/8000
a=rtpmap:8 PCMA/8000
a=rtpmap:116 iLBC/8000
a=fmtp:116 mode=20
a=rtpmap:18 G729/8000
a=fmtp:18 annexb=yes
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
<— Transmitting SIP request (443 bytes) to UDP:172.30.30.11:5060 —>
OPTIONS sip:104@172.30.30.11:5060;user=phone SIP/2.0
Via: SIP/2.0/UDP 188.92.255.132:5060;rport;branch=z9hG4bKPj6e372897-89c5-4e32-a89b-7a15f16516e4
From: sip:104@172.30.31.254;tag=2012d158-a7b8-469f-8e39-9c185e97d41f
To: sip:104@172.30.30.11;user=phone
Contact: sip:104@188.92.255.132:5060
Call-ID: 0233858f-1046-4ecf-8cc6-104a7b8a4c58
CSeq: 9317 OPTIONS
Max-Forwards: 70
User-Agent: FPBX-17.0.28(22.7.0)
Content-Length: 0
<— Received SIP response (1346 bytes) from UDP:172.30.30.11:5060 —>
SIP/2.0 200 OK
Via: SIP/2.0/UDP 188.92.255.132:5060;rport;branch=z9hG4bKPj6e372897-89c5-4e32-a89b-7a15f16516e4;received=172.30.31.254
From: sip:104@172.30.31.254;tag=2012d158-a7b8-469f-8e39-9c185e97d41f
To: sip:104@172.30.30.11;user=phone;tag=c444a075fe76129f7713c151-36b3d51e
Call-ID: 0233858f-1046-4ecf-8cc6-104a7b8a4c58
Session-ID: 73745a1400105000a000c444a075fe76;remote=00000000000000000000000000000000
Date: Tue, 10 Mar 2026 11:50:45 GMT
CSeq: 9317 OPTIONS
Server: Cisco-CP7821/14.2.1
Allow: ACK,BYE,CANCEL,INVITE,NOTIFY,OPTIONS,REFER,REGISTER,UPDATE
Allow-Events: kpml,dialog,refer
Accept: application/sdp,multipart/mixed,multipart/alternative
Accept-Encoding: identity
Accept-Language: en
Supported: replaces,join,sdp-anat,norefersub,resource-priority,extended-refer,X-cisco-callinfo,X-cisco-serviceuri,X-cisco-escapecodes,X-cisco-service-control,X-cisco-srtp-fallback,X-cisco-monrec,X-cisco-config,X-cisco-sis-7.0.0
Content-Length: 300
Content-Type: application/sdp
Content-Disposition: session;handling=optional
v=0
o=Cisco-SIPUA 12070 0 IN IP4 172.30.30.11
s=SIP Call
t=0 0
m=audio 0 RTP/AVP 0 8 116 18 101
b=TIAS:64000
a=rtpmap:0 PCMU/8000
a=rtpmap:8 PCMA/8000
a=rtpmap:116 iLBC/8000
a=fmtp:116 mode=20
a=rtpmap:18 G729/8000
a=fmtp:18 annexb=yes
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
On Tuesday 10 March 2026 at 13:01:51, qfaizi wrote:
<— Transmitting SIP request (444 bytes) to UDP:172.30.30.12:5060 —>
OPTIONS sip:100@172.30.30.12:5060;user=phone SIP/2.0
<— Transmitting SIP request (443 bytes) to UDP:172.30.30.11:5060 —>
OPTIONS sip:104@172.30.30.11:5060;user=phone SIP/2.0
Neither of these are Register requests.
Antony.
–
A committee is a group of people who keep minutes and waste hours.
Milton Berle
Please reply to the list;
please don't CC me.
I have registered many of these older Cisco devices to FreePBX. Please note that you should really be asking your question in the FreePBX community forum. In any case, I can guarantee to you that the problem is in your SEPMAC file. These phones are very sensitive in parsing this file. If you would kindly post your complete SEP file I will look though it and point out any issues.
Please also followup in https://community.freepbx.org/
I saw your post over there so I updated
with a copy of a SEPMAC config file that should work for you.