I subscribe to our ftth provider with internet package that comes with telephone landine via gpon ont.I bypass and bridge mode gpon ont and let my pfsense do the pppoe authentication .II then connect my yealink T2IP and it register and can make regular calls.Can anyone help me set up it with my freepbx, please see below dumps and screenshot from yealink config
There is something strange about your having a public address and the proxy having a private one. Also you have a VoIP line, not a landline.
There isn’t enough information about how to identify incoming calls.
Otherwise:
Obviously use PJSIP
client URI is sip:[email protected]:5060
server URI is sip:fmc.stc.com.sa:5060
server name is fmc.stc.com.sa
transport is UDP
contact user is +96611239XXXX
username is +96611239XXXX
from_user is +96611239XXXX
password is ********
Authentication and registration are outbound
proxy is sip:10.200.42.121\;lr\;hide
match/permit - insufficient information
DID name is +96611239XXXX
callerid - insufficient information, although they may well not accept any explicit caller ID, and from user may be enough
Note the wiki is still down so I’m unable to double check some details.
I dont have any issues on network side…
PING 10.200.42.121 (10.200.42.121) 56(84) bytes of data.
64 bytes from 10.200.42.121: icmp_seq=1 ttl=252 time=100 ms
64 bytes from 10.200.42.121: icmp_seq=2 ttl=252 time=100 ms
The first issue is not specifying a least routing proxy. The \ was lost (garbled by the forum software) when I first specified this, but I did correct that.
The call-ID is perfectly valid. There is no requirement that it contain a domain name, only that it be globally unique.
I’m pretty sure that the 120001 error is happening before the request has been sent to the wire, and not a response from the far end.
The user part of the Contact header looks gibberish here, although maybe it was uploaded in the wrong font encoding.
You appear to be using an unsupported version of Asterisk, as line 4081 does not exist in any currently supported version. My guess is you are using 13, but you could be using an even older one.
hi thank you for your support…it was firewall problem on my pfsense, my bad…
one last issue is i cant hear a ringback tone when calling my voip line from my cellphone…i set my inbound to my ivr and i hear also nothing
They might be sending it as early media, in which case you will need to call Progress() before dialling. This assumes that you don’t prematurely answer.
Sorry. That was the pure Asterisk answer, although I think there is an equivalent option.
Try playing with the “Signal RINGING” and “Force Answer” options under Connectivity > Inbound Routes > [YOUR ROUTE] > Advanced.
Try Signal RINGING first, but if you’re still not hearing anything, you can try Force Answer, which will force your PBX to pick up the call and generate the ringing itself
Now that the wiki is back, I can’t actually find an option that controls the use of Progress.
However, Signal Ringing is going to give you ringback tone even if the call never gets to the point of ringing anyone, so, for outgoing calls makes little sense. It may be useful for incoming calls, to give the caller confidence, but for outgoing calls, it means the caller gets a false indication of partial success.
Sounds like the issue they are having is with with incoming calls, as they mentioned they’re not getting ringback when calling the VoIP line from their cell.
You will have to answer for IVRs to work, as the mobile network is unlikely to allow early media. I wouldn’t expect the IVR itself to generate an Alerting status on the mobile network, even if it does answer, but if it does answer, I would expect any ringback indication it receives to be passed back as in band audio.
Are the ring group and the misc destination behind the IVR? If not what is the general nature of the misc destination?
i dont hear any thing at all even the ivr announcement,dead silent but i can press digits upon call on ivr .i tried to change codecs(alaw, ulaw g729) under sip trunk but the same issue…misc destination was caller id digits announcement
In your firewall, confirm that you have forwarded the RTP port range (default is UDP 10000-20000) to the LAN address of the PBX. Also confirm that you have disabled source port rewriting; see
If no luck, in the Inbound Route, try setting Signal Ringing and/or setting Pause Before Answer to 2.
If still no luck, paste the Asterisk log for a problematic call (with pjsip logger on) at pastebin.freepbx.org and post the link here.
