Jump to content

Incoming call to Snom but no outgoing to tetronic(Cerato)


adeope

Recommended Posts

I have been trying to setup trunk between two vendors (Snom and Tetronic).

 

The first time i have the trunk setup, it was on a NaTted network while I did it I was able to call from Tetronic to Snom but Snom couldn't call tetronic.

 

The I decided to try setting up the trunk on thesame subnet bypassing all NAT issues to see if it works but it was still thesame thing.

 

Please has anyone experienced this before and how can the problem be solved or is it that tetronics is not compactible with snom on Outgoing?.

Link to comment
Share on other sites

In order to make outbound calls, you need a trunk on the snom PBX and a dialplan that uses this trunk. Also, this dial plan must be associated to the user who is trying to make the outbound calls.

 

Check out some of the below links to get an overview on how to make outbound calls on snom PBX.

http://wiki.snomone.com/index.php?title=Dial_Plans

http://wiki.snomone.com/index.php?title=Trunk_Overview

http://wiki.snomone.com/index.php?title=SIP_Gateway

http://wiki.snomone.com/index.php?title=Outbound_Calls

Link to comment
Share on other sites

In order to make outbound calls, you need a trunk on the snom PBX and a dialplan that uses this trunk. Also, this dial plan must be associated to the user who is trying to make the outbound calls.

 

Check out some of the below links to get an overview on how to make outbound calls on snom PBX.

http://wiki.snomone.com/index.php?title=Dial_Plans

http://wiki.snomone.com/index.php?title=Trunk_Overview

http://wiki.snomone.com/index.php?title=SIP_Gateway

http://wiki.snomone.com/index.php?title=Outbound_Calls

 

 

 

I have a dial plan set and its correct, I am thinking if its an interoperability issues because when I set thesame trunk on snom to snom everythin work perfect, though I have not done it on a different network.

Link to comment
Share on other sites

Most of the problems with service providers come from the different interpretation of the SIP headers. If you are on pre-4.5, try different settings for the Caller-ID presentation (e.g. RFC3325). Since 4.5, you have a lot more options, but you can try some of the JavaScript-defined templates that are available on the trunk page.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...