PJSIP Trunk, Flowroute POP, Chan_Sip Phones. Best Practice?


(Caribbean Voip) #1

Good Morning,
I’ve stepped in it and need some help.

FreePBX 14.0.13.12
Asterisk 15.7.3
Flowroute DID
Linux version 3.10.0-957.21.3.el7.x86_64

Our system was working fine until about 2 months ago it stopped registering with Flowroute. Looked like the issue was we were still using a chan_Sip trunk. So, I created a new PJSIP Trunk (using 5160) and followed the guide from Flowroute. (Our phones listen on 5060)


Registration fixed and all things worked fine. (Sip Registration with Flowroute)
Yesterday, we started getting calls dropped. Registration was failing/reconnecting over and over. I followed another guide to switch over to IP registration with flowroute.

(Nice, well done guide btw) I made all the changes in FreePBX and Flowroute.
However, this did not solve the registration problem. I felt this was b/c I was using 5060 for my sip phones and 5160 for the pjsip Trunk. So, I tried to swap those. I didn’t find a ‘How To’ for that so I winged it. Fail. Mistake. Lost connection to 50 phones. Time to punt. Did a restore from 2 days ago. Ran some important system and module updates. Network power-cycled the phones and now I am back to where I was. Internal communication is fine but no Flowroute registration so no calls going in/out. Understandable b/c I have not (and don’t want to) go back to Flowroute Sip Registration. Thanks for following me this far.
So, my question is: Is my problem that my pjsip trunk is using 5160 and my phones are on chan sip with 5060? How Should This be setup for the long term? System is broken now so I might as well fix it right. Is there a guide for changing my sip phones on 5060 to pjsip phones and should I do that? I’d bet there are guides but I’m not finding them. Let me know if I did not describe necessary details about my predicament.
I would appreciate any guidance, suggestions, useful links you can provide.
Thanks in advance.


#2

If you use IP routing , you should not also be trying to ‘register’.


(Caribbean Voip) #3

Understood. That’s incorrect terminology on my part. I switched to IP Authentication. That’s why I was not seeing Registration attempt messages in Asterisk.


(Caribbean Voip) #4

Update. I’m using IP registration now. No more dropped calls. Outgoing calls always successful.

However, I would guess that 1/2 of the incoming calls get “unable to complete call” message from ILEC. Any suggestions on what might be causing those failures or how to troubleshoot it?

Second, my pjsip trunk is using 5160 and my phones are on chan sip with 5060? Is that okay? Is there a guide for changing my sip phones on 5060 to pjsip phones and should I do that? Thanks.


(Dave Burgess) #5

Check your logs. I’m going to guess that half your calls are coming in as “anonymous” calls since you didn’t add the alternate POPs for your provider in the PJ-SIP Settings.

It’s not bad, but it is suboptimal. Chan-SIP is going away. There are VERY few cases where Chan-SIP is preferred over PJ-SIP now.

In your “extensions” app, there is an option to change your Chan-SIP extensions to PJ-SIP.

The gotcha is that I don’t think you can run PJ-SIP on two different channels at the same time. The “least painful” way to do this would be to move PJ-SIP to 5060 and update your ITSP settings to use 5060 instead of 5160 for your incoming connections.

Note, this is not a painless or easy way to do this - it’s possible that you’ll have to make configuration changes on the phones for some settings. Maybe not, but maybe. Also, the change from 5160 to 5060 for your provider is similarly not painless. All the work and testing you did to get that set up needs to be reaccomplished.

The advantage for you is that your system will then be set up for the removal of Chan-SIP as an active component coming soon. Doing it now, while you have the box open, would (to my way of thinking) be preferable to having to remember all of this stuff in a couple of years when you HAVE to do it.


(M Wise) #6

For others coming to this thread or searching for it later, chan_sip still works fine for Flowroute trunks with IP authentication, you just need to define a chan_sip trunk for each of the now-many IPs that Flowroute uses for incoming calls. I put this in sip_custom.conf and used some asterisk syntax for setting this up to reduce the length.

[flowroute-common](!)
disallow=all
type=friend
insecure=port,invite
;context=from-trunk
context=from-pstn-e164-us
canreinvite=no
qualify=no
allow=ulaw

[flowroute-va-in1](flowroute-common)
host=34.226.36.32

[flowroute-va-in2](flowroute-common)
host=34.226.36.33

[flowroute-va-in3](flowroute-common)
host=34.226.36.34

[flowroute-va-in4](flowroute-common)
host=34.226.36.35

[flowroute-va-in5](flowroute-common)
host=34.226.36.36

[flowroute-va-in6](flowroute-common)
host=34.226.36.37

[flowroute-va-in7](flowroute-common)
host=34.226.36.38

[flowroute-va-in8](flowroute-common)
host=34.226.36.39

[flowroute-va-in9](flowroute-common)
host=34.226.36.40

[flowroute-va-in10](flowroute-common)
host=34.226.36.41

[flowroute-va-in11](flowroute-common)
host=34.226.36.42

[flowroute-va-in12](flowroute-common)
host=34.226.36.43

[flowroute-va-in13](flowroute-common)
host=34.226.36.44

[flowroute-va-in14](flowroute-common)
host=34.226.36.45

[flowroute-va-in15](flowroute-common)
host=34.226.36.46

[flowroute-va-in16](flowroute-common)
host=34.226.36.47

[flowroute-nj-in1](flowroute-common)
host=147.75.65.192

[flowroute-nj-in2](flowroute-common)
host=147.75.65.193

[flowroute-nj-in3](flowroute-common)
host=147.75.65.194

[flowroute-nj-in4](flowroute-common)
host=147.75.65.195

[flowroute-nj-in5](flowroute-common)
host=147.75.65.196

[flowroute-nj-in6](flowroute-common)
host=147.75.65.197

[flowroute-nj-in7](flowroute-common)
host=147.75.65.198

[flowroute-nj-in8](flowroute-common)
host=147.75.65.199

[flowroute-nj-in9](flowroute-common)
host=147.75.65.200

[flowroute-nj-in10](flowroute-common)
host=147.75.65.201

[flowroute-nj-in11](flowroute-common)
host=147.75.65.202

[flowroute-nj-in12](flowroute-common)
host=147.75.65.203

[flowroute-nj-in13](flowroute-common)
host=147.75.65.204

[flowroute-nj-in14](flowroute-common)
host=147.75.65.205

[flowroute-nj-in15](flowroute-common)
host=147.75.65.206

[flowroute-nj-in16](flowroute-common)
host=147.75.65.207

[flowroute-or-in1](flowroute-common)
host=34.210.91.112

[flowroute-or-in2](flowroute-common)
host=34.210.91.113

[flowroute-or-in3](flowroute-common)
host=34.210.91.114

[flowroute-or-in4](flowroute-common)
host=34.210.91.115

[flowroute-or-in5](flowroute-common)
host=34.210.91.116

[flowroute-or-in6](flowroute-common)
host=34.210.91.117

[flowroute-or-in7](flowroute-common)
host=34.210.91.118

[flowroute-or-in8](flowroute-common)
host=34.210.91.119

[flowroute-or-in9](flowroute-common)
host=34.210.91.120

[flowroute-or-in10](flowroute-common)
host=34.210.91.121

[flowroute-or-in11](flowroute-common)
host=34.210.91.122

[flowroute-or-in12](flowroute-common)
host=34.210.91.123

[flowroute-or-in13](flowroute-common)
host=34.210.91.124

[flowroute-or-in14](flowroute-common)
host=34.210.91.125

[flowroute-or-in15](flowroute-common)
host=34.210.91.126

[flowroute-or-in16](flowroute-common)
host=34.210.91.127

[flowroute-wa-in1](flowroute-common)
host=147.75.60.160

[flowroute-wa-in2](flowroute-common)
host=147.75.60.161

[flowroute-wa-in3](flowroute-common)
host=147.75.60.162

[flowroute-wa-in4](flowroute-common)
host=147.75.60.163

[flowroute-wa-in5](flowroute-common)
host=147.75.60.164

[flowroute-wa-in6](flowroute-common)
host=147.75.60.165

[flowroute-wa-in7](flowroute-common)
host=147.75.60.166

[flowroute-wa-in8](flowroute-common)
host=147.75.60.167

[flowroute-wa-in9](flowroute-common)
host=147.75.60.168

[flowroute-wa-in10](flowroute-common)
host=147.75.60.169

[flowroute-wa-in11](flowroute-common)
host=147.75.60.170

[flowroute-wa-in12](flowroute-common)
host=147.75.60.171

[flowroute-wa-in13](flowroute-common)
host=147.75.60.172

[flowroute-wa-in14](flowroute-common)
host=147.75.60.173

[flowroute-wa-in15](flowroute-common)
host=147.75.60.174

[flowroute-wa-in16](flowroute-common)
host=147.75.60.175

[flowroute-in-legacy]
disallow=all
host=216.115.69.144
type=friend
insecure=port,invite
;context=from-trunk
context=from-pstn-e164-us
canreinvite=no

[flowroute-in-legacy2]
disallow=all
host=70.167.153.130
type=friend
insecure=port,invite
;context=from-trunk
context=from-pstn-e164-us
canreinvite=no

(system) closed #7

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