Anveo Direct

<< < (2/4) > >>

Zopa:
Thank you for jumping in.


Quote

Will Anveo Direct be your primary line? How do you want to route calls to GV or Anveo?  What SP trunk is defined as the Proxy?

SP4 is a proxy for my IP Phone system.

Anveo Direct will only be used for outbound calls for now.

As for routing calls, think that I have figured out more more or less. I will route domestic calls via GV, international via AD (Anveo Direct) for my setup. Here is my SP4/X_InboundCallRoute --> {8888888888>(011x.):tg2},{8888888888>(xx.):tg1}. I have my Trunk Groups setup in different order failing over to various SPs. I have another location, however, which will be setup with outbound service via Anveo Direct (or similar commercial provider), because I need outbound CID info to be set correctly and not who the GV number.

[Side note, I need a better DigitMap for international call routing to include international destination starting that start with 1, but that's a separate isssue]


Quote

When you define a VG you must specify a SIP SP trunk to route the call. That is why you need spx(sbc.anveo.com) . You will have to modify the VG DigitMap.

Do this mean that I must have a matching relationship between SP and VG, or did I get it wrong? Or is would I be using my SP4 (proxy SP) in my case? Not very clear here. I like to use VGs to setup multiple providers like CallWithUS or Anveo Direct and not be limited by 4 x SP limit in Obi202.

Quote

I assume you need to register your public IP address with Anveo Direct, not the address of the OBi.

This is an obvious pre-req and has already been done. I have a proper static address, so this is a non issue.

Quote

You shouldn't have to port forward for outbound calls, but you will for inbound calls. I don't know how Anveo handles inbound calls. Do they route them to a specific port number and can you configure it? It can't be the port number used for GV.

I don't really worry about incoming calls for now, as I'll use GV presentation and added services for that, or Anveo retail for a more complex setup. I strictly like to learn how to use Anveo Direct for cheap outbound calls.

azrobert:
You need to specify a SIP trunk in the VG definition to be used for routing outbound calls. The VG definitions will override the SP definitions. You can point several VGs to a single SP trunk.

Voice Gateway 1
Name: Anveo Direct
AccessNumber: sp4(sbc.anveo.com)
DigitMap: (<011:000000>xx.)

Trunk Group 2
TrunkList: vg1,..........
DigitMap: (011xx.)

drgeoff:
I deleted two versions of my earlier post in this thread after reading through the DSLreports thread and concluding this could be a real can of worms.  :(

You are welcome to try to use anything from them that you managed to grab before they disappeared but even less guarantees than usual, ie none. :)

Zopa:
Quote from: drgeoff on December 15, 2015, 10:54:05 am

I deleted two versions of my earlier post in this thread after reading through the DSLreports thread and concluding this could be a real can of worms.  :(

You are welcome to try to use anything from them that you managed to grab before they disappeared but even less guarantees than usual, ie none. :)


Why delete the posts though? Can of worms is about the summary of getting Obi work with any of these techs or providers. Why not work through the issues, instead of deleting posts? Perhaps I'm not getting something...

drgeoff:
Quote from: Zopa on December 15, 2015, 12:12:23 pm

Quote from: drgeoff on December 15, 2015, 10:54:05 am

I deleted two versions of my earlier post in this thread after reading through the DSLreports thread and concluding this could be a real can of worms.  :(

You are welcome to try to use anything from them that you managed to grab before they disappeared but even less guarantees than usual, ie none. :)


Why delete the posts though? Can of worms is about the summary of getting Obi work with any of these techs or providers. Why not work through the issues, instead of deleting posts? Perhaps I'm not getting something...

I had hoped that no-one had seen those posts before I deleted them and I was not aware that you had, until I saw you quoting bits from them. I had surmised (wrongly it appears) that you did not have much experience in these matters and I did not want to lead you up a garden path with suggestions that were too simplistic compared to the real situation.  Anyway on reading the DSLreports thread they covered everything and more of what I had written.  They were written by people who had first hand experience of trying it for themselves.  Mine were untested ideas.

Navigation

[0] Message Index

[#] Next page

[*] Previous page