FreePBX | Register | Issues | Wiki | Portal | Support

Telmex ISP SIP account registers in MicroSIP but not in FreePBX


(Mjb2000) #1

My ISP here in Mexico, Telmex, provides a Fiber Optic Optical Network Terminal (ONT) - Essentially a piece of Consumer Premises Equipment (CPE) that functions as a modem, router, switch, WiFi access point and crucially - as an ATA, connecting to the ISP via SIP and offering a phone line from the telephone company.

I was able to obtain the SIP credentials by connecting a serial console to my modem. I have been able to use these credentials successfully with PhonerLite, Zoiper and MicroSIP (for all of these software packages I can register and make phone calls.

TELMEX seems to use SRV records which I couldn’t get working 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 correctly.

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

@Stewart1 was trying to help me on this thread, but suggesting creating a new thread specifically for my problem. One this he mentioned was “copying a register to a file and using sipsak”… This is above my level of understanding and I don’t know how I would go about this. Does anyone else know what might be going on here? How can I take my working MicroSIP config and use it successfully in FreePBX?

My current config is:

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

secret=PASSWORD
username=+520000000000
user=+520000000000
fromuser=+520000000000
realm=ims.telmex.com
domain=ims.telmex.com
authdomain=ims.telmex.com
fromdomain=ims.telmex.com
outboundproxy=189.247.242.147
host=189.247.242.147
fullcontact=+520000000000@ims.telmex.com
authname=+520000000000@ims.telmex.com
type=peer
insecure=very
context=from-sip-external

Register string:
+520000000000@ims.telmex.com:PASSWORD:+520000000000@189.247.242.147/+529848730302

Asterisk SIP log…

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

[2018-07-09 12:35:41] WARNING[1019] chan_sip.c: Section 'Telmex' lacks type
[2018-07-09 12:35:41] VERBOSE[1019] chan_sip.c: Really destroying SIP dialog '75db2cf62a7ed81e14c45f5e28956512@10.200.0.32' Method: REGISTER
[2018-07-09 12:35:41] NOTICE[1019] chan_sip.c: -- Re-registration for +520000000000@189.247.242.147
[2018-07-09 12:35:41] VERBOSE[1019] chan_sip.c: REGISTER 11 headers, 0 lines
[2018-07-09 12:35:41] VERBOSE[1019] chan_sip.c: Reliably Transmitting (NAT) to 189.247.242.147:5060:
REGISTER sip:ims.telmex.com SIP/2.0
Via: SIP/2.0/UDP *.*.*.*:5160;branch=z9hG4bK4af132fc;rport
Max-Forwards: 70
From: <sip:+520000000000@ims.telmex.com>;tag=as3d7f6af0
To: <sip:+520000000000@ims.telmex.com>
Call-ID: 1cbc86d41b0e907b31bf29842558a31e@10.200.0.32
CSeq: 102 REGISTER
Supported: replaces, timer
User-Agent: FPBX-14.0.3.6(14.7.6)
Expires: 120
Contact: <sip:+529848730302@*.*.*.*:5160>
Content-Length: 0


---
[2018-07-09 12:35:42] VERBOSE[1019] chan_sip.c: Retransmitting #1 (NAT) to 189.247.242.147:5060:
REGISTER sip:ims.telmex.com SIP/2.0
Via: SIP/2.0/UDP *.*.*.*:5160;branch=z9hG4bK4af132fc;rport
Max-Forwards: 70
From: <sip:+520000000000@ims.telmex.com>;tag=as3d7f6af0
To: <sip:+520000000000@ims.telmex.com>
Call-ID: 1cbc86d41b0e907b31bf29842558a31e@10.200.0.32
CSeq: 102 REGISTER
Supported: replaces, timer
User-Agent: FPBX-14.0.3.6(14.7.6)
Expires: 120
Contact: <sip:+529848730302@*.*.*.*:5160>
Content-Length: 0


---
[2018-07-09 12:35:43] VERBOSE[1019] chan_sip.c: Retransmitting #2 (NAT) to 189.247.242.147:5060:
REGISTER sip:ims.telmex.com SIP/2.0
Via: SIP/2.0/UDP *.*.*.*:5160;branch=z9hG4bK4af132fc;rport
Max-Forwards: 70
From: <sip:+520000000000@ims.telmex.com>;tag=as3d7f6af0
To: <sip:+520000000000@ims.telmex.com>
Call-ID: 1cbc86d41b0e907b31bf29842558a31e@10.200.0.32
CSeq: 102 REGISTER
Supported: replaces, timer
User-Agent: FPBX-14.0.3.6(14.7.6)
Expires: 120
Contact: <sip:+529848730302@*.*.*.*:5160>
Content-Length: 0

PhonerLite config (working)

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

MicroSIP config (working)

SIP Server: ims.telmex.com
SIP Proxy: 189.247.242.147
Username: +52xxxxxxxxxx
Domain: ims.telmex.com
Login: +52xxxxxxxxxx@ims.telmex.com
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:+52xxxxxxxxxx@ims.telmex.com>;tag=1934202406
To: <sip:+52xxxxxxxxxx@ims.telmex.com>
Call-ID: 80A6192D-2C81-E811-87B8-BB0BE53ECAEB@10.0.0.50
CSeq: 326 REGISTER
Contact: <sip:+52xxxxxxxxxx@10.0.0.50: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:+52xxxxxxxxxx@ims.telmex.com = 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:+52xxxxxxxxxx@ims.telmex.com SIP/2.0
Via: SIP/2.0/UDP 10.0.0.50:5060;branch=z9hG4bK80a6192d2c81e81187bcbb0be53ecaeb;rport
From: <sip:+52xxxxxxxxxx@ims.telmex.com>;tag=3576163364
To: <sip:+52xxxxxxxxxx@ims.telmex.com>
Call-ID: 80A6192D-2C81-E811-87B9-BB0BE53ECAEB@10.0.0.50
CSeq: 327 SUBSCRIBE
Contact: <sip:+52xxxxxxxxxx@10.0.0.50: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:+52xxxxxxxxxx@ims.telmex.com>;tag=3576163364
To: <sip:+52xxxxxxxxxx@ims.telmex.com>;tag=aprqngfrt-cpkluc30080e4
Call-ID: 80A6192D-2C81-E811-87B9-BB0BE53ECAEB@10.0.0.50
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:+52xxxxxxxxxx@ims.telmex.com>;tag=1934202406
To: <sip:+52xxxxxxxxxx@ims.telmex.com>;tag=dqdq0bbq
Call-ID: 80A6192D-2C81-E811-87B8-BB0BE53ECAEB@10.0.0.50
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:+52xxxxxxxxxx@ims.telmex.com>;tag=1934202406
To: <sip:+52xxxxxxxxxx@ims.telmex.com>
Call-ID: 80A6192D-2C81-E811-87B8-BB0BE53ECAEB@10.0.0.50
CSeq: 328 REGISTER
Contact: <sip:+52xxxxxxxxxx@10.0.0.50:5060>;+sip.instance="<urn:uuid:00D1773F-C27F-E811-97E2-EED72484AD05>"
Authorization: Digest username="+52xxxxxxxxxx@ims.telmex.com", 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:+52xxxxxxxxxx@ims.telmex.com>;tag=1934202406
To: <sip:+52xxxxxxxxxx@ims.telmex.com>;tag=k2dqaboc
Call-ID: 80A6192D-2C81-E811-87B8-BB0BE53ECAEB@10.0.0.50
CSeq: 328 REGISTER
P-Associated-URI: <sip:+52xxxxxxxxxx@ims.telmex.com;user=phone>
P-Associated-URI: <sip:+52xxxxxxxxxx@ims.telmex.com>
Accept-Resource-Priority: wps.4
Contact: <sip:+52xxxxxxxxxx@10.0.0.50: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:+52xxxxxxxxxx@ims.telmex.com:5060>;tag=2gdrr79g-CC-20
To: <sip:+52xxxxxxxxxx@ims.telmex.com:60580>;tag=003db22d2c81e81187bdbb0be53ecaeb
Call-ID: 8g323bee3s8749i8a4r9r9iaa2a34s93@19500.0.ATS.ats01.ims.telmex.com.20
CSeq: 1 NOTIFY
Contact: <sip:+52xxxxxxxxxx@10.0.0.50: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:52xxxxxxxxxx@voipnvcompigl.telmex.net>;tag=mTMk6w0eA
To: <sip:52xxxxxxxxxx@voipnvcompigl.telmex.net>;tag=uhf99zaa
CSeq: 210 REGISTER
Call-ID: grNrFpLzKe
Warning: 399 P.5.127.ims.telmex.com "SS170001F133L3261S0E0[00001] Hllm query failed"
Content-Length: 0


Trunk configuration help for a noob - infostrada/wind italian provider
(Dave Burgess) #2

Set type to ‘friend’ and see if that helps.


(Mjb2000) #3

Hi. Unfortunately changing to type=friend didn’t seem to change anything :frowning:


(Mjb2000) #4

Wow… something I have just found is that Telmex seem to purposely not responding to the default FreePBX User Agent FPBX-14.0.3.6(14.7.6)

I edited /etc/asterisk/sip_general_custom.conf and set:

useragent=MicroSIP/3.18.5

I also needed to change the register string slightly. From this voip-info page I found out that when using an AuthUser and a proxy then string should be as follows:
fromuser@fromdomain:secret:authuser@host:port/extension

Which, for my specific set-up would mean…

+520000000000@ims.telmex.com:PASSWORD:+520000000000@ims.telmex.com@189.247.242.147/+520000000000

Registration and incoming calls are now working perfectly… Now onwards to outgoing calls, but I don’t think that will be too much more of an issue (famous last words!).


(system) #5

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