I did run into an issue just after the upgrade whereby the VOIP provider (Pennytel) didnt seem to be picking up the disconnect if I hung up after dialing a number.The output from asterisk was: Quote Remote host cant match request CANCEL to call what would happen then was the provider would ring the dialed number up to 3 times after the initial call was cancelled.
Chan_Sip.C: Remote Host Can'T Match Request Cancel To Call Update Asterisk ImI solved the problem by updating asterisk from ATRPMS: yum --enablerepoatrpms update asterisk Im now running asterisk-1.4.24-73.el4 and eveything seems OK.
Chan_Sip.C: Remote Host Can'T Match Request Cancel To Call Upgrade Whereby TheThe PBX will send SIP traffic to the specified RegistrarProxy found in the VoIP providers configuration. The UDP port ranges that need to be forwarded are related to SIP (call signaling) and RTP (Voice data). If you are running the PBX on the standard SIP port 5060 then all packets to UDP port 5060 need to be forwarded to the PBX. For the second port range (audio) you must forward ports 9000-9255 UDP to the PBX. You can find out the exact port range that your PBX uses in the 3CX Phone System Management Console under Settings Network. On the other hand the PBX in reverse must also be allowed to send out SIP traffic (source and destination port 5060), RTP traffic (in this case traffic with source ports 9000-9255 UDP) and STUN requests (destination port 3478). It is highly recommended that you test with an open access, i.e. ALL outgoing traffic from the PBX. It needs this information so it knows how it is seen from the VoIP providers point of view. Successful log entries will reflect proper STUN resolution and will appear in the server status page on PBX at startup. For example, when a server has a public IP and no firewall in front of it. To tun off STUN resolution, from the 3CX Management Console, navigate to Settings Network STUN server tab. Check the Turn off STUN requests check box, enter the Static Public IP of the server and Select Network card Interface. For additional information regarding working without STUN resolution read our How and when can I switch off STUN Resolution article. Every NAT device will have a status monitor where its IP can be reviewed. If the port forwarding rules have been set correctly then (depending on the type of NAT implemented) no PAT (Port Address Translation) will occur. This means that the source port will not change when the PBX contacts the STUN server, the reported source port by the STUN server will remain 5060 unchanged. If the NAT device does not have the SIP port 5060 forwarding rules set, it would be very likely that the NAT device would change the source port along with the source IP when the request traverses the device. The log entry in this case would look something like the following. If your internet connection has a frequently changing IP address your PBX is running in what can be considered a hostile environment. This type of environment is highly discouraged as it will most likely lead to intermittent service. To see if you have a frequently changing IP by either reviewing the status monitor of your NAT device (WAN IP) or by reviewing the Resolved external IP in STUN server responses logged by the PBX in its status monitor page. If you choose to operate in such an environment make sure to have a short interval between external IP checks. From the 3CX Management Console, go to, Settings Network STUN server tab. In the Query STUN server every (sec) entry field, enter the time that the server will check for its external IP address.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |