Running freepbx 17
Nextiva trunk can receive calls but not make calls.
I tried every possible combination in the outbound routes and fudged every setting in the pjsip trunk Nextiva PJSIP Settings Advanced, and Nothign Works I’m about ready to smash it. Please let me know if I forgot any needed parameters, I’m so dang upset I can spit.
Try turning on pjsip logging and making a test call. And pasting the output into the thread. Should provide the details of what’s going on.
Ok it let me do it
|1|0.000000|192.168.1.191|0.0.0.0|SIP/SDP|1505|Request: INVITE sip:[email protected]:5060;user=phone | |
|—|—|—|—|—|—|—|
|2|0.000412|0.0.0.0|192.168.1.191|SIP|574|Status: 401 Unauthorized | |
|3|0.024550|192.168.1.191|0.0.0.0|SIP|481|Request: ACK sip:[email protected]:5060;user=phone | |
|4|0.042830|192.168.1.191|0.0.0.0|SIP/SDP|1785|Request: INVITE sip:[email protected]:5060;user=phone | |
|5|0.043318|0.0.0.0|192.168.1.191|SIP|375|Status: 100 Trying | |
|6|0.160137|0.0.0.0|208.89.108.104|SIP/SDP|1726|Request: INVITE sip:bt.voipdnsservers.com | |
|7|0.208719|208.89.108.104|0.0.0.0|SIP|410|Status: 100 Trying | |
|8|0.262657|208.89.108.104|0.0.0.0|SIP|710|Status: 180 Ringing | |
|9|0.263751|0.0.0.0|192.168.1.191|SIP|661|Status: 180 Ringing | |
|10|0.348924|208.89.108.104|0.0.0.0|SIP/SDP|1037|Status: 200 OK (INVITE) | |
|11|0.349137|0.0.0.0|208.89.108.104|SIP|492|Request: ACK sip:208.89.108.104:5060;transport=udp | |
|12|0.354563|0.0.0.0|192.168.1.191|SIP/SDP|1155|Status: 200 OK (INVITE) | |
|13|0.387588|192.168.1.191|0.0.0.0|SIP|723|Request: ACK sip:192.168.1.2:5060;transport=TCP | |
|14|8.259775|0.0.0.0|192.168.1.161|SIP|461|Request: OPTIONS sip:[email protected]:5060 | |
|15|8.264135|192.168.1.161|0.0.0.0|SIP|401|Status: 200 OK (OPTIONS) | |
|16|9.778399|0.0.0.0|199.87.144.67|SIP|513|Request: OPTIONS sip:[email protected]:5060 | |
|17|9.859669|199.87.144.67|0.0.0.0|SIP|449|Status: 200 Keepalive (OPTIONS) | |
|18|17.864889|208.89.108.104|0.0.0.0|SIP|429|Request: BYE sip:[email protected]:5060 | |
|19|17.865073|0.0.0.0|208.89.108.104|SIP|436|Status: 200 OK (BYE) | |
|20|18.004529|0.0.0.0|192.168.1.191|SIP|473|Request: BYE sip:[email protected]:50509;transport=TCP | |
|21|18.019424|192.168.1.191|0.0.0.0|SIP|583|Status: 200 OK (BYE) | |
|22|42.042638|0.0.0.0|199.87.144.66|SIP|646|Request: REGISTER sip:sip.callcentric.net:5060 (1 binding) | |
|23|42.122941|199.87.144.66|0.0.0.0|SIP|588|Status: 407 Proxy Authentication Required | |
|24|42.123169|0.0.0.0|199.87.144.66|SIP|850|Request: REGISTER sip:sip.callcentric.net:5060 (1 binding) | |
|25|42.218157|199.87.144.66|0.0.0.0|SIP|550|Status: 200 OK (REGISTER) (1 binding) | |
|26|46.121434|0.0.0.0|192.168.1.191|SIP|461|Request: OPTIONS sip:[email protected]:5060 | |
|27|46.135406|192.168.1.191|0.0.0.0|SIP|529|Status: 200 OK (OPTIONS) | |
|28|46.753961|0.0.0.0|208.89.108.104|SIP|594|Request: OPTIONS sip:bt.voipdnsservers.com | |
Successful call from local endpoint to Callcentric.
Call cleared by Callecentric, after about 17.5 seconds.
No details of call clearing have been provided. Whilst Callcentric, might not say why they cleared it, it is possible that they have done so, but without the full BYE request, we will never know.
Successful registration and connectivity test with Callcentric
My guess would be that Callcentric are not receiving any media, in which case we really need the SDP, in both directions, for the incoming leg. We may also need RTP debugging.
This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.