voip.ms atlanta2 issues / am I switching my inbound routing to new server correctly ...
-
This morning I'm having issues with voip.ms atlanta2 server. It seems to be intermittently going down. I've moved our outbound routing to the washington2 server but I can't seem to get our inbound routing to move from the atlanta2 server to washington2.
I went in to the portal and from the manage DID section I changed the pop from atlanta2 to washington2 but the routing doesn't seem to be changing to the new trunk. Does anyone know if there something else I need to be doing to get my inbound to switch to the new pop?
-
@BraswellJay said in voip.ms atlanta2 issues / am I switching my inbound routing to new server correctly ...:
This morning I'm having issues with voip.ms atlanta2 server. It seems to be intermittently going down. I've moved our outbound routing to the washington2 server but I can't seem to get our inbound routing to move from the atlanta2 server to washington2.
I went in to the portal and from the manage DID section I changed the pop from atlanta2 to washington2 but the routing doesn't seem to be changing to the new trunk. Does anyone know if there something else I need to be doing to get my inbound to switch to the new pop?
Did you update your PBX to register to Washington2?
-
@JaredBusch said in voip.ms atlanta2 issues / am I switching my inbound routing to new server correctly ...:
@BraswellJay said in voip.ms atlanta2 issues / am I switching my inbound routing to new server correctly ...:
This morning I'm having issues with voip.ms atlanta2 server. It seems to be intermittently going down. I've moved our outbound routing to the washington2 server but I can't seem to get our inbound routing to move from the atlanta2 server to washington2.
I went in to the portal and from the manage DID section I changed the pop from atlanta2 to washington2 but the routing doesn't seem to be changing to the new trunk. Does anyone know if there something else I need to be doing to get my inbound to switch to the new pop?
Did you update your PBX to register to Washington2?
Yes. That is successful and my outbound routing is going out over the new trunk correctly. It's only inbound that is still trying to come in over atlanta2 instead of washington2
-
@BraswellJay said in voip.ms atlanta2 issues / am I switching my inbound routing to new server correctly ...:
@JaredBusch said in voip.ms atlanta2 issues / am I switching my inbound routing to new server correctly ...:
@BraswellJay said in voip.ms atlanta2 issues / am I switching my inbound routing to new server correctly ...:
This morning I'm having issues with voip.ms atlanta2 server. It seems to be intermittently going down. I've moved our outbound routing to the washington2 server but I can't seem to get our inbound routing to move from the atlanta2 server to washington2.
I went in to the portal and from the manage DID section I changed the pop from atlanta2 to washington2 but the routing doesn't seem to be changing to the new trunk. Does anyone know if there something else I need to be doing to get my inbound to switch to the new pop?
Did you update your PBX to register to Washington2?
Yes. That is successful and my outbound routing is going out over the new trunk correctly. It's only inbound that is still trying to come in over atlanta2 instead of washington2
New trunk? do you have multiple trunks? Or did you just edit the existing.
disable the trunk in the PBX, apply changes, enable, apply changes.
-
@JaredBusch said in voip.ms atlanta2 issues / am I switching my inbound routing to new server correctly ...:
@BraswellJay said in voip.ms atlanta2 issues / am I switching my inbound routing to new server correctly ...:
@JaredBusch said in voip.ms atlanta2 issues / am I switching my inbound routing to new server correctly ...:
@BraswellJay said in voip.ms atlanta2 issues / am I switching my inbound routing to new server correctly ...:
This morning I'm having issues with voip.ms atlanta2 server. It seems to be intermittently going down. I've moved our outbound routing to the washington2 server but I can't seem to get our inbound routing to move from the atlanta2 server to washington2.
I went in to the portal and from the manage DID section I changed the pop from atlanta2 to washington2 but the routing doesn't seem to be changing to the new trunk. Does anyone know if there something else I need to be doing to get my inbound to switch to the new pop?
Did you update your PBX to register to Washington2?
Yes. That is successful and my outbound routing is going out over the new trunk correctly. It's only inbound that is still trying to come in over atlanta2 instead of washington2
New trunk? do you have multiple trunks? Or did you just edit the existing.
disable the trunk in the PBX, apply changes, enable, apply changes.
It's a new trunk. I had one going to atlanta2 which I left intact but added a new one to washington2. I went ahead and disabled the old one to see if that would somehow force it but that didn't have any effect.
I've opened a ticket with voip.ms.
In theory the only change I would need in the portal to change the inbound routing would be the change the POP in the manage DID I think. Is that correct?
This is how my POP reads for that number in the portal now:
It had said Atlanta-2 before I changed this morning.
-
@BraswellJay said in voip.ms atlanta2 issues / am I switching my inbound routing to new server correctly ...:
@JaredBusch said in voip.ms atlanta2 issues / am I switching my inbound routing to new server correctly ...:
@BraswellJay said in voip.ms atlanta2 issues / am I switching my inbound routing to new server correctly ...:
@JaredBusch said in voip.ms atlanta2 issues / am I switching my inbound routing to new server correctly ...:
@BraswellJay said in voip.ms atlanta2 issues / am I switching my inbound routing to new server correctly ...:
This morning I'm having issues with voip.ms atlanta2 server. It seems to be intermittently going down. I've moved our outbound routing to the washington2 server but I can't seem to get our inbound routing to move from the atlanta2 server to washington2.
I went in to the portal and from the manage DID section I changed the pop from atlanta2 to washington2 but the routing doesn't seem to be changing to the new trunk. Does anyone know if there something else I need to be doing to get my inbound to switch to the new pop?
Did you update your PBX to register to Washington2?
Yes. That is successful and my outbound routing is going out over the new trunk correctly. It's only inbound that is still trying to come in over atlanta2 instead of washington2
New trunk? do you have multiple trunks? Or did you just edit the existing.
disable the trunk in the PBX, apply changes, enable, apply changes.
It's a new trunk. I had one going to atlanta2 which I left intact but added a new one to washington2. I went ahead and disabled the old one to see if that would somehow force it but that didn't have any effect.
I've opened a ticket with voip.ms.
In theory the only change I would need in the portal to change the inbound routing would be the change the POP in the manage DID I think. Is that correct?
This is how my POP reads for that number in the portal now:
It had said Atlanta-2 before I changed this morning.
Correct, that is all you do at VoIP.ms
But you had two trunks trying to register with the same credentials. That is going to confuse e system about elsewhere to send the call
-
The Atlanta2 server has been overtaken by snakeheads...
