Trunk configuration help for a noob - infostrada/wind italian provider

Hi all. Sorry to have to bother you but I’m not able to resolve a configuration issue that seems simple but, even if i’ve searched a lot, i can figure out how to solve.

I’d like to use a sip number provided by my ISP (Wind/3/infostrada).
I’m able to setup and use a softphone (PhonerLite) using this information:
Proxy/Registrar: voip.libero.it
Realm: sip.infostrada.it
user: 390377xxxxxx
password: xxxxx
Auth Name: 390377xxxxxx (same as user)
localport: 5060
transport: UDP

I’m able to call/receive and have a full audio support.
The softphone (and the preepbx as well) are behind a router/nat with SIP/ALG enabled ad there aren’t any specific port mapping configured (no 5060, no rtp ports).

Now I’d like to use this info in order to configure a sip trunk on my freepbx (all my house comminications run around this pbx), but I’ve done a lot of test but never the trunk registers to the servers.

I kindly ask if someon can post me how to configure the trunk. I’m using freepbx 13.0.192.19

In order to give you much info as possible following the log from the softphone:

> 192.168.XXX.XXX:5060;branch=z9hG4bK00735521bccae711a24343d9e197f2c0;rport
> From: "PhonerLite" <sip:[email protected]>;tag=3284728896
> To: "PhonerLite" <sip:[email protected]>
> Call-ID: [email protected]
> CSeq: 1 REGISTER
> Contact: <sip:[email protected]:5060>;+sip.instance="<urn:uuid:006CC480-45CA-E711-BD9F-51ED84AB9938>"
> Allow: INVITE, ACK, BYE, CANCEL, INFO, MESSAGE, NOTIFY, OPTIONS, REFER, UPDATE, PRACK
> Max-Forwards: 70
> Allow-Events: org.3gpp.nwinitdereg
> User-Agent: SIPPER for PhonerLite
> Supported: replaces, from-change, gruu
> Expires: 900
> Content-Length: 0
> 11:51:42,179: Facility Confirm: 16 00 01 00 80 81 06 00 01 00 00 00 00 00 03 00 05 01 00 02 00 00 
> 11:51:42,179: Facility Confirm (Supplementary Services)
> 11:51:42,179:  Listen: success
> -------------------------------------------
> 11:51:42,179: T: 151.6.177.6:5060 (UDP)
> SUBSCRIBE sip:[email protected] SIP/2.0
> Via: SIP/2.0/UDP 192.168.XXX.XXX:5060;branch=z9hG4bK00735521bccae711a24443d9e197f2c0;rport
> From: "PhonerLite" <sip:[email protected]>;tag=2033211642
> To: <sip:[email protected]>
> Call-ID: [email protected]
> CSeq: 2 SUBSCRIBE
> Contact: <sip:[email protected]:5060>;+sip.instance="<urn:uuid:006CC480-45CA-E711-BD9F-51ED84AB9938>"
> Max-Forwards: 70
> User-Agent: SIPPER for PhonerLite
> Expires: 1800
> Event: message-summary
> Accept: application/simple-message-summary
> Content-Length: 0
> -------------------------------------------
> 11:51:42,190: R: 151.6.177.6:5060 (UDP)
> SIP/2.0 403 Forbidden
> Via: SIP/2.0/UDP 192.168.XXX.XXX:5060;branch=z9hG4bK00735521bccae711a24443d9e197f2c0;rport=60081
> From: "PhonerLite" <sip:[email protected]>;tag=2033211642
> To: <sip:[email protected]>;tag=aprqngfrt-5plj0p3000040
> Call-ID: [email protected]
> CSeq: 2 SUBSCRIBE
> -------------------------------------------
> 11:51:42,205: R: 151.6.177.6:5060 (UDP)
> SIP/2.0 401 Unauthorized
> Via: SIP/2.0/UDP 192.168.XXX.XXX:5060;branch=z9hG4bK00735521bccae711a24343d9e197f2c0;rport=60081
> From: "PhonerLite" <sip:[email protected]>;tag=3284728896
> To: "PhonerLite" <sip:[email protected]>;tag=59cac1cb-5a1010bd7ba3b88
> Call-ID: [email protected]
> CSeq: 1 REGISTER
> Date: Sat, 18 Nov 2017 10:51:41 GMT
> Server: Alcatel-Lucent-HPSS/3.0.3
> WWW-Authenticate: Digest realm="sip.infostrada.it", nonce="b7c9036dbf3054aea5a1010ba940e9703dc8f84c1708", opaque="ALU:xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx", algorithm=MD5, qop="auth"
> Content-Length: 0
> -------------------------------------------
> 11:51:42,205: T: 151.6.177.6:5060 (UDP)
> REGISTER sip:sip.infostrada.it SIP/2.0
> Via: SIP/2.0/UDP 192.168.XXX.XXX:5060;branch=z9hG4bK00735521bccae711a24743d9e197f2c0;rport
> From: "PhonerLite" <sip:[email protected]>;tag=3284728896
> To: "PhonerLite" <sip:[email protected]>
> Call-ID: [email protected]
> CSeq: 3 REGISTER
> Contact: <sip:[email protected]:5060>;+sip.instance="<urn:uuid:006CC480-45CA-E711-BD9F-51ED84AB9938>"
> Authorization: Digest username="39XXXXXXXXXX", realm="sip.infostrada.it", nonce="b7c9036dbf3054aea5a1010ba940e9703dc8f84c1708", uri="sip:sip.infostrada.it", response="53226206cffd75893c924182a09dc8f4", algorithm=MD5, cnonce="00735521bccae711a24643d9e197f2c0", opaque="ALU:QbkRBthOEgEQAkgVEwwHRAIBHgkdHwQCQ1lFRkZWGA4iIyd0d2gqISUrJSNjOSY-NTw0JHs.I2JsagYC", qop=auth, nc=00000001
> Allow: INVITE, ACK, BYE, CANCEL, INFO, MESSAGE, NOTIFY, OPTIONS, REFER, UPDATE, PRACK
> Max-Forwards: 70
> Allow-Events: org.3gpp.nwinitdereg
> User-Agent: SIPPER for PhonerLite
> Supported: replaces, from-change, gruu
> Expires: 900
> Content-Length: 0
> -------------------------------------------
> 11:51:42,277: R: 151.6.177.6:5060 (UDP)
> SIP/2.0 200 OK
> Via: SIP/2.0/UDP 151.65.61.70:60081;branch=z9hG4bK00735521bccae711a24743d9e197f2c0;rport=60081
> From: "PhonerLite" <sip:[email protected]>;tag=3284728896
> To: "PhonerLite" <sip:[email protected]>;tag=59cac1cb-5a1010bdbe8f87e
> Call-ID: [email protected]
> CSeq: 3 REGISTER
> Allow-Events: reg
> Contact: <sip:[email protected]:60081>;expires=3600;+sip.instance="<urn:uuid:006CC480-45CA-E711-BD9F-51ED84AB9938>"
> Date: Sat, 18 Nov 2017 10:51:41 GMT
> P-Associated-URI: <sip:[email protected]>
> P-Associated-URI: <tel:39XXXXXXXXXX>
> P-Associated-URI: <sip:[email protected]>
> Server: Alcatel-Lucent-HPSS/3.0.3
> Content-Length: 0
> -------------------------------------------
> 11:51:45,612: R: DNS lookup for 'voip.libero.it'
> start resolving SRV (UDP)...
> -------------------------------------------
> 11:51:45,697: R: DNS lookup for 'voip.libero.it'
> 151.6.177.6 (TTL=7200)
> -------------------------------------------
> 11:51:45,698: R: DNS lookup for 'voip.libero.it'
> start resolving SRV (UDP)...
> -------------------------------------------
> 11:51:45,736: R: DNS lookup for 'voip.libero.it'
> 151.6.177.6 (TTL=7200)
> -------------------------------------------
> 11:51:45,736: T: 151.6.177.6:5060 (UDP)
> REGISTER sip:sip.infostrada.it SIP/2.0
> Via: SIP/2.0/UDP 192.168.XXX.XXX:5060;branch=z9hG4bK80361f23bccae711a24843d9e197f2c0;rport
> From: "PhonerLite" <sip:[email protected]>;tag=3284728896
> To: "PhonerLite" <sip:[email protected]>
> Call-ID: [email protected]
> CSeq: 4 REGISTER
> Contact: <sip:[email protected]:5060>;+sip.instance="<urn:uuid:006CC480-45CA-E711-BD9F-51ED84AB9938>"
> Authorization: Digest username="39XXXXXXXXXX", realm="sip.infostrada.it", nonce="b7c9036dbf3054aea5a1010ba940e9703dc8f84c1708", uri="sip:sip.infostrada.it", response="df513407786c53d6ff8be6c25f498cc1", algorithm=MD5, cnonce="80361f23bccae711a24743d9e197f2c0", opaque="ALU:QbkRBthOEgEQAkgVEwwHRAIBHgkdHwQCQ1lFRkZWGA4iIyd0d2gqISUrJSNjOSY-NTw0JHs.I2JsagYC", qop=auth, nc=00000002
> Allow: INVITE, ACK, BYE, CANCEL, INFO, MESSAGE, NOTIFY, OPTIONS, REFER, UPDATE, PRACK
> Max-Forwards: 70
> Allow-Events: org.3gpp.nwinitdereg
> User-Agent: SIPPER for PhonerLite
> Supported: replaces, from-change, gruu
> Expires: 900
> Content-Length: 0
> -------------------------------------------
> 11:51:45,747: R: 151.6.177.6:5060 (UDP)
> SIP/2.0 200 OK
> Via: SIP/2.0/UDP 151.65.61.70:60081;branch=z9hG4bK80361f23bccae711a24843d9e197f2c0;rport=60081
> From: "PhonerLite" <sip:[email protected]>;tag=3284728896
> To: "PhonerLite" <sip:[email protected]>;tag=aprqek5k7r1-2pnlhf3000080
> Call-ID: [email protected]
> CSeq: 4 REGISTER
> Contact: <sip:[email protected]:60081>;expires=3596

While from freepbx log full i can see only a timout or a “wrong password” messages depending of the configuration attempt but I don’t know how to get the same detailed log (I’ve set all switches to ON in the log file settings).

Thanks a lot for support.
f

It seems a problem related to the register string and the outboud proxy.

I’ve user the CLI and the sip debug to collect info.
Using the register string:
39XXXXXXXXXX:[email protected]/39XXXXXXXXXX

in the log i find that the register call is done to:

> Reliably Transmitting (no NAT) to 54.72.52.58:5060:
> REGISTER sip:sip.infostrada.it SIP/2.0
> Via: SIP/2.0/UDP 151.65.61.70:5060;branch=z9hG4bK5f0acd44
> Max-Forwards: 70
> From: <sip:[email protected]>;tag=as2f6a2a40
> To: <sip:[email protected]>
> Call-ID: [email protected]
> CSeq: 102 REGISTER
> Supported: replaces, timer
> User-Agent: FPBX-13.0.192.19(13.13.1)
> Expires: 120
> Contact: <sip:[email protected]:5060>
> Content-Length: 0

and no answer will return. While if i use the string:
39XXXXXXXXXX:[email protected]/39XXXXXXXXXX

i get in the log:

> Reliably Transmitting (no NAT) to 151.6.177.6:5060:
> REGISTER sip:voip.libero.it SIP/2.0
> Via: SIP/2.0/UDP 151.65.61.70:5060;branch=z9hG4bK2cad8619
> Max-Forwards: 70
> From: <sip:[email protected]>;tag=as1a0ceb40
> To: <sip:[email protected]>
> Call-ID: [email protected]
> CSeq: 102 REGISTER
> Supported: replaces, timer
> User-Agent: FPBX-13.0.192.19(13.13.1)
> Expires: 120
> Contact: <sip:[email protected]:5060>
> Content-Length: 0

I get a:

> <--- SIP read from UDP:151.6.177.6:5060 --->
> SIP/2.0 403 Forbidden
> Via: SIP/2.0/UDP 192.168.10.246:5060;branch=z9hG4bK2cad8619
> From: <sip:[email protected]>;tag=as1a0ceb40
> To: <sip:[email protected]>;tag=59cac13f-5a1018e13299dd68
> Call-ID: [email protected]
> CSeq: 102 REGISTER
> Date: Sat, 18 Nov 2017 11:26:25 GMT
> Server: Alcatel-Lucent-HPSS/3.0.3
> Content-Length: 0

The problem seems that i have to registrer to server voip.libero.it but using the sip.infostrada.it as realm.

I setup these parameter in freepbx this way:

> username=39XXXXXXXXXX
> user=39XXXXXXXXXX
> type=friend
> secret=XXXXXXXX
> realm=sip.infostrada.it
> outboundproxy=voip.libero.it:5060
> insecure=invite
> host=voip.libero.it
> fromuser=39XXXXXXXXXX
> context=from-sip-external

How i can force to use the “proxy” ignoring the registrer string?
Thanks again
f

Now that I’ve better focused on the problem I’ve found some hint in the asterisk manual and using a bit more complex register string:
[email protected]:XXXXXXXX:[email protected]

I’m able to success in the registration.

Sorry for the posts, hope they can help some other asterisk noob.

Now the next step… in and out calling.

1 Like

Hi

Did you ever get this all working? I am in a really similar situation where I can get everything to work in PhonerLite (and Zoiper and MicroSIP), but I can’t work out how to translate those software settings to the chan_sip config inside FreePBX.

I can’t even get the registration to work (which you seem to have achieved).

What does Reports -> Asterisk Info -> Registries show for the trunk?

Do you have any other trunks on your system that are working?

At the Asterisk command prompt, type
sip set debug on
and you should then see the registration attempts and any replies. If it doesn’t make sense, post them here (redact usernames and any other private info).

Hi. Thanks for helping me out with this… I have a few other regular sip providers registered through PJSIP,

This particular SIP Trunk is the VoIP service for my ISP. Normally this is registered by the CPE mdoem provided by the ISP, but since I have the modem in bridge mode the VoIP functionalities are disabled. I know the registration details and have been able to get them registered and working in PhonerLite, Zoiper and MicroSIP. The ISP seems to use SRV records which seem to work with MicroSIP, so I substituted the proxy domain name with the IP address that PhonerLite was using and that meant I was able to get MicroSIP to register too.

Asterisk info shows “Request sent” for registration, but is never registers.

My current config is:

Outbound
Trunk Name: Telmex
PEER Details: [BLANK]
Inbound
USER Context: +52xxxxxxxxxx
USER Details:

username=+52xxxxxxxxxx
user=+52xxxxxxxxxx
type=friend
secret=############
realm=ims.telmex.com
outboundproxy=189.247.242.147
insecure=invite
host=189.247.242.147
fromuser=+52xxxxxxxxxx
[email protected]
context=from-sip-external

Register string:
[email protected]:############:[email protected]

Asterisk SIP log…

*.*.*.* = my external IP address, not the IP of the FreePBX box (which is 10.0.0.32)

[2018-07-08 09:42:14] NOTICE[1019]: chan_sip.c:15890 sip_reg_timeout:    -- Registration for '[email protected]' timed out, trying again (Attempt #50)
Really destroying SIP dialog '[email protected]' Method: REGISTER
Retransmitting #1 (NAT) to 189.247.242.147:5060:
REGISTER sip:ims.telmex.com SIP/2.0
Via: SIP/2.0/UDP *.*.*.*:5160;branch=z9hG4bK0af907e1;rport
Max-Forwards: 70
From: <sip:[email protected]>;tag=as40f406f2
To: <sip:[email protected]>
Call-ID: [email protected]
CSeq: 151 REGISTER
Supported: replaces, timer
User-Agent: FPBX-14.0.3.6(14.7.6)
Expires: 120
Contact: <sip:[email protected]*.*.*.*:5160>
Content-Length: 0


---
Retransmitting #2 (NAT) to 189.247.242.147:5060:
REGISTER sip:ims.telmex.com SIP/2.0
Via: SIP/2.0/UDP *.*.*.*:5160;branch=z9hG4bK0af907e1;rport
Max-Forwards: 70
From: <sip:[email protected]>;tag=as40f406f2
To: <sip:[email protected]>
Call-ID: [email protected]
CSeq: 151 REGISTER
Supported: replaces, timer
User-Agent: FPBX-14.0.3.6(14.7.6)
Expires: 120
Contact: <sip:[email protected]*.*.*.*:5160>
Content-Length: 0

PhonerLite config (working)

Proxy/Registrar: voipnvcompigl.telmex.net
Domain/Realm: ims.telmex.com
Username: +52xxxxxxxxxx
Password: ############
Authentication name: [email protected]

MicroSIP config (working)

SIP Server: ims.telmex.com
SIP Proxy: 189.247.242.147
Username: +52xxxxxxxxxx
Domain: ims.telmex.com
Login: [email protected]
Password: ############

PhonerLite log

From here you can see why I ended up using the proxy IP address

I am not sure what the various forbidden and timeout messages are, but PhonerLite does seem to work correctly (I can make and receive calls).

-------------------------------------------
09:52:17,558: R: DNS lookup for 'voipnvcompigl.telmex.net'
start resolving SRV (UDP)...
-------------------------------------------
09:52:17,561: R: DNS lookup for 'slbcompigl.voip.telmex.net'
189.247.242.147:5060 (TTL=1699)
-------------------------------------------
09:52:17,561: R: open UDP port (SIP): 5060

-------------------------------------------
09:52:17,562: R: open TCP port (TLS listen): 5061

-------------------------------------------
09:52:17,562: R: open TCP port (TCP listen): 5060

09:52:17,611: Listen Confirm: 0E 00 08 00 05 81 9E 02 01 00 00 00 00 00 
09:52:17,611: Listen Confirm
-------------------------------------------
09:52:17,563: R: open UDP port (mDNS): 5353

09:52:17,621: Facility Confirm: 1A 00 08 00 80 81 A0 02 01 00 00 00 00 00 03 00 09 00 00 06 00 00 3D 01 00 00 
09:52:17,621: Facility Confirm (Supplementary Services)
09:52:17,621: Facility Request: 16 00 08 00 80 80 A1 02 01 00 00 00 03 00 07 01 00 04 3D 01 00 00 
09:52:17,621: Facility Request (Listen To Supplementary Services)
09:52:17,621:  Get Supported Services: success
-------------------------------------------
09:52:17,563: T: 189.247.242.147:5060 (UDP)
REGISTER sip:ims.telmex.com SIP/2.0
Via: SIP/2.0/UDP 10.0.0.50:5060;branch=z9hG4bK80a6192d2c81e81187bbbb0be53ecaeb;rport
From: <sip:[email protected]>;tag=1934202406
To: <sip:[email protected]>
Call-ID: [email protected]
CSeq: 326 REGISTER
Contact: <sip:[email protected]:5060>;+sip.instance="<urn:uuid:00D1773F-C27F-E811-97E2-EED72484AD05>"
Allow: INVITE, ACK, BYE, CANCEL, INFO, MESSAGE, NOTIFY, OPTIONS, REFER, UPDATE, PRACK
Max-Forwards: 70
Allow-Events: org.3gpp.nwinitdereg
User-Agent: SIPPER for PhonerLite
Supported: replaces, from-change, gruu
Expires: 900
Content-Length: 0


-------------------------------------------
09:52:17,563: T: mDNS refresh: sip:[email protected] = 169.254.106.102:5060, ttl=900
SIPPER for PhonerLite
09:52:17,621: Facility Confirm: 16 00 08 00 80 81 A1 02 01 00 00 00 00 00 03 00 05 01 00 02 00 00 
09:52:17,621: Facility Confirm (Supplementary Services)
09:52:17,621:  Listen: success
-------------------------------------------
09:52:17,621: T: 189.247.242.147:5060 (UDP)
SUBSCRIBE sip:[email protected] SIP/2.0
Via: SIP/2.0/UDP 10.0.0.50:5060;branch=z9hG4bK80a6192d2c81e81187bcbb0be53ecaeb;rport
From: <sip:[email protected]>;tag=3576163364
To: <sip:[email protected]>
Call-ID: [email protected]
CSeq: 327 SUBSCRIBE
Contact: <sip:[email protected]:5060>;+sip.instance="<urn:uuid:00D1773F-C27F-E811-97E2-EED72484AD05>"
Max-Forwards: 70
User-Agent: SIPPER for PhonerLite
Expires: 1800
Event: message-summary
Accept: application/simple-message-summary
Content-Length: 0


-------------------------------------------
09:52:17,705: R: 189.247.242.147:5060 (UDP)
SIP/2.0 403 Forbidden
Via: SIP/2.0/UDP 10.0.0.50:5060;received=*.*.*.*;branch=z9hG4bK80a6192d2c81e81187bcbb0be53ecaeb;rport=60580
From: <sip:[email protected]>;tag=3576163364
To: <sip:[email protected]>;tag=aprqngfrt-cpkluc30080e4
Call-ID: [email protected]
CSeq: 327 SUBSCRIBE


-------------------------------------------
09:52:17,847: R: 189.247.242.147:5060 (UDP)
SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP 10.0.0.50:5060;received=*.*.*.*;branch=z9hG4bK80a6192d2c81e81187bbbb0be53ecaeb;rport=60580
From: <sip:[email protected]>;tag=1934202406
To: <sip:[email protected]>;tag=dqdq0bbq
Call-ID: [email protected]
CSeq: 326 REGISTER
WWW-Authenticate: Digest realm="ims.telmex.com", nonce="PBk3fi0dSOVla8Cwre8YRw==",algorithm=MD5
Content-Length: 0


-------------------------------------------
09:52:17,848: T: 189.247.242.147:5060 (UDP)
REGISTER sip:ims.telmex.com SIP/2.0
Via: SIP/2.0/UDP 10.0.0.50:5060;branch=z9hG4bK80a6192d2c81e81187bdbb0be53ecaeb;rport
From: <sip:[email protected]>;tag=1934202406
To: <sip:[email protected]>
Call-ID: [email protected]
CSeq: 328 REGISTER
Contact: <sip:[email protected]:5060>;+sip.instance="<urn:uuid:00D1773F-C27F-E811-97E2-EED72484AD05>"
Authorization: Digest username="[email protected]", realm="ims.telmex.com", nonce="PBk3fi0dSOVla8Cwre8YRw==", uri="sip:ims.telmex.com", response="bd636de3caf80c6c64ba2910c30555f9", algorithm=MD5
Allow: INVITE, ACK, BYE, CANCEL, INFO, MESSAGE, NOTIFY, OPTIONS, REFER, UPDATE, PRACK
Max-Forwards: 70
Allow-Events: org.3gpp.nwinitdereg
User-Agent: SIPPER for PhonerLite
Supported: replaces, from-change, gruu
Expires: 900
Content-Length: 0


-------------------------------------------
09:52:18,100: R: 189.247.242.147:5060 (UDP)
SIP/2.0 200 OK
Via: SIP/2.0/UDP 10.0.0.50:5060;received=*.*.*.*;branch=z9hG4bK80a6192d2c81e81187bdbb0be53ecaeb;rport=60580
From: <sip:[email protected]>;tag=1934202406
To: <sip:[email protected]>;tag=k2dqaboc
Call-ID: [email protected]
CSeq: 328 REGISTER
P-Associated-URI: <sip:[email protected];user=phone>
P-Associated-URI: <sip:[email protected]>
Accept-Resource-Priority: wps.4
Contact: <sip:[email protected]:5060>;expires=30;q=1;+sip.instance="<urn:uuid:00D1773F-C27F-E811-97E2-EED72484AD05>"
Content-Length: 0


-------------------------------------------
09:52:18,123: T: 189.247.242.147:5060 (UDP)
SIP/2.0 200 OK
Via: SIP/2.0/UDP 189.247.242.147:5060;branch=z9hG4bKrc0icv204g1ge1u3epu0.1
From: <sip:[email protected]:5060>;tag=2gdrr79g-CC-20
To: <sip:[email protected]:60580>;tag=003db22d2c81e81187bdbb0be53ecaeb
Call-ID: [email protected]m.20
CSeq: 1 NOTIFY
Contact: <sip:[email protected]:5060>
Allow: INVITE, ACK, BYE, CANCEL, INFO, MESSAGE, NOTIFY, OPTIONS, REFER, UPDATE, PRACK
Server: SIPPER for PhonerLite
Content-Length: 0


-------------------------------------------
09:52:18,293: R: 189.247.242.147:5060 (UDP)
SIP/2.0 480 Temporarily Unavailable
Via: SIP/2.0/UDP 10.0.0.50:5060;received=*.*.*.*;branch=z9hG4bK.bbkAMUUuC;rport=60580
From: <sip:[email protected]>;tag=mTMk6w0eA
To: <sip:[email protected]>;tag=uhf99zaa
CSeq: 210 REGISTER
Call-ID: grNrFpLzKe
Warning: 399 P.5.127.ims.telmex.com "SS170001F133L3261S0E0[00001] Hllm query failed"
Content-Length: 0

I am very puzzled. I tried to replicate your issue (no response to REGISTER from Asterisk but ok from PhonerLite). I don’t have a Telmex account, so just tried +525522223333 and a dummy password.

Indeed, there was no response on my test system in Google Cloud. But unfortunately, there was also no response in PhonerLite. Possibly, requests with an invalid username are simply discarded.

It seems that you are not alone; see https://asteriskmx.org/foros/forum/asterisk/instalación-y-primeros-pasos/38921-configuracion-de-troncal-freepbx-telmex . Using that proxy, I did get a 403 with a Warning header showing “invalid user”, but don’t know whether that proxy would be valid for your account.

You posted in an old thread about a specific Italian provider. Try starting a new thread with Telmex in the title – with luck a Telmex user who has solved this will respond.

If not, one approach would be to copy a successful initial register to a file and send it with sipsak. Assuming that you get a response, gradually change it to what Asterisk was sending, one header at a time, testing after each change. Once you learn which header is the culprit, you should be able to change the Asterisk config to fix the problem.

Not sure if you have seen my reply on my new thread, but it seems like your comment about not getting a response from the server was quite critical… It seems like they are purposefully ignoring and not responding to the FPBX user-agent. I changed the user agent and BAM! - It works.

Thanks for your time in looking in to this.