Jump to content

snomone plus 16fxo


nathans
 Share

Recommended Posts

HI,

 

Setup: snomone+ 16FXO sangoma NBE cards.

 

 

On the "Trunk" definition for the Sangoma 16FXO tab I have set it up as a SIP Gateway, Inbound and outbound, NBE, Enabled and 12 ports. (see attachment)

 

Question:

1) On the "Number of ports" I'm limited to 12 while I have 16. How could I enable the whole 16 FXOs?

2) on the CO Lines: I just added 12 CO lines because of the above, but I'm guessing it should be the 16 as in the number of FXO channels, right?

3) How do I make inbound Caller ID work? I'm able to make outbound call no problem, but inbound I have not been able to get the caller ID to route calls. Any ideas?

 

 

Thanks!

Nathan

post-10331-0-79039400-1319579275_thumb.png

Link to comment
Share on other sites

Question:

1) On the "Number of ports" I'm limited to 12 while I have 16. How could I enable the whole 16 FXOs?

2) on the CO Lines: I just added 12 CO lines because of the above, but I'm guessing it should be the 16 as in the number of FXO channels, right?

Basically, you don't need to choose the NBE / 12 ports if you are using more than 12 ports FXO. You can just choose the "Generic SIP server" and type in the co-lines.

3) How do I make inbound Caller ID work? I'm able to make outbound call no problem, but inbound I have not been able to get the caller ID to route calls. Any ideas?

Generally, if you set the your office DID(s) to specific extensions, you should be able to see the caller ID as presented by the service provider.

Link to comment
Share on other sites

Thanks. #1 and #2 seem to be doing the trick.

 

As for recognizing the inbound caller ID, it seems like either the Telco or the Sangoma are not recognizing the number of the analog trunk that is ringing:

 

SIP/2.0 100 Trying

Via: SIP/2.0/UDP 127.0.0.1:5066;rport=5066;branch=z9hG4bKd9257140-1dd1-11b2-837e-fc130d81ef11

From: "unknown-caller-name" <sip:unknown-ani@192.168.31.2:5066>;tag=pxip-callid-1319747569-345281-720721662-1123ds-8f6ac0b-b574aab4

To: "111" <sip:111@localhost:5060>;tag=49dec7da98

Call-ID: d924f0f8-1dd1-11b2-903a-9ee89d225bf7@snomONE

CSeq: 9561457 INVITE

Content-Length: 0

 

[7] 2011/10/27 16:32:54: Set packet length to 20

[6] 2011/10/27 16:32:54: Sending RTP for d924f0f8-1dd1-11b2-903a-9ee89d225bf7@snomONE to 192.168.31.2:14612, codec not set yet

[5] 2011/10/27 16:32:54: Received incoming call without trunk information and user has not been found

[7] 2011/10/27 16:32:54: Set packet length to 20

[7] 2011/10/27 16:32:54: SIP Tx udp:127.0.0.1:5066:

 

My questions are:

1) Is there any settings on the Sangoma FXO config or the snomone+ to tweak to recognize the inbound trunk

2) If not, what is the best way of configuring the 16 FXO lines so that I can know which one is ringing and routed accordingly?

 

Any ideas?

Thanks!

Nathan

Link to comment
Share on other sites

Net border express on the snom ONE Plus, will use caller name before caller ANI. This will make the from header sent to the PBX unknown-caller-name when one is not present.

 

This can be changed by removing it from the Routing rules

 

http://wiki.sangoma.com/NBE-inbound-channel-grouping

 

<condition param="pstn.in.callerName" expr="(.*)"/>

<param name="sip.out.from.displayName" expr="%2"/>

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.

 Share

×
×
  • Create New...