Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

If server A is down, request is sent to server B #6

Open
joserwan opened this issue Mar 11, 2014 · 1 comment
Open

If server A is down, request is sent to server B #6

joserwan opened this issue Mar 11, 2014 · 1 comment

Comments

@joserwan
Copy link

My request is like :

actionid: 1394553381.47397
action: QueuePause
Interface: SIP/300
Queue: zTest
Paused: false
ProxyKey: xxxxxxx
Server: 127.0.0.1

Astmanproxy logs :

Mar 11 12:01:10: connect_nonb: error 103, closing old fd and grabbing a new one...
Mar 11 12:01:10: asterisk@127.0.0.1: Connect failed, Retrying (1) Software caused connection abort [103]
Mar 11 12:01:12: asterisk@127.0.0.1: Connect failed, Retrying (1) Connection refused [111]
Mar 11 12:01:12: is_encrypted: 0
Mar 11 12:01:12: Connection received from 127.0.0.1
Mar 11 12:01:12: Set 127.0.0.1 input format to standard
Mar 11 12:01:12: Set 127.0.0.1 output format to standard
Mar 11 12:01:12: calling standard_read...
Mar 11 12:01:12: Returning standard block of 5 lines, res 1
Mar 11 12:01:12: standard_read result = 1
Mar 11 12:01:12: ValidateAction called for fd: 9, outbound
Mar 11 12:01:12: Message validated - no filtering
Mar 11 12:01:12: set destination: 127.0.0.1
Mar 11 12:01:12: writing block to 172.16.0.249
(...)

Config :

host = 127.0.0.1, 5038, ami_user, ami_password, off, off
host = 172.16.0.249, 5038, ami_user, ami_password, off, off

I think that if "Server" is not given in request, it could be OK to send it to the next server if the first one is down, but when "Server" is given, it should return an error, shouldn't it ?

PS : I use the master branch, up to date.

@davies147
Copy link
Owner

Hi,

I agree with you, but that is part of the code that I've never touched, so
I am not sure how easily you will achieve it! For a start it would rely on
an ordered list of server hosts so that you have a reliable method of
walking the list in a definite order.

Regards,
Steve

On 11 March 2014 16:09, joserwan notifications@github.com wrote:

My request is like :

actionid: 1394553381.47397
action: QueuePause
Interface: SIP/300
Queue: zTest
Paused: false
ProxyKey: xxxxxxx
Server: 127.0.0.1

Astmanproxy logs :

Mar 11 12:01:10: connect_nonb: error 103, closing old fd and grabbing a new one...
Mar 11 12:01:10: asterisk@127.0.0.1: Connect failed, Retrying (1) Software caused connection abort [103]
Mar 11 12:01:12: asterisk@127.0.0.1: Connect failed, Retrying (1) Connection refused [111]
Mar 11 12:01:12: is_encrypted: 0
Mar 11 12:01:12: Connection received from 127.0.0.1
Mar 11 12:01:12: Set 127.0.0.1 input format to standard
Mar 11 12:01:12: Set 127.0.0.1 output format to standard
Mar 11 12:01:12: calling standard_read...
Mar 11 12:01:12: Returning standard block of 5 lines, res 1
Mar 11 12:01:12: standard_read result = 1
Mar 11 12:01:12: ValidateAction called for fd: 9, outbound
Mar 11 12:01:12: Message validated - no filtering
Mar 11 12:01:12: set destination: 127.0.0.1
Mar 11 12:01:12: writing block to 172.16.0.249
(...)

Config :

host = 127.0.0.1, 5038, ami_user, ami_password, off, off
host = 172.16.0.249, 5038, ami_user, ami_password, off, off

I think that if "Server" is not given in request, it could be OK to send
it to the next server if the first one is down, but when "Server" is given,
it should return an error, shouldn't it ?

Reply to this email directly or view it on GitHubhttps://github.com//issues/6
.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants