Ошибка регистрации voip оператора на сервере провайдера

[anonymous]

Добрый день! Столкнулись с проблемой регистрации на сервере провайдера. Создаем Voip general оператора, указываем все данные. Режим работы через stun. Однако регистрация не удается, в логах АТС пишет ошибку:12:58:14.186 [CM504005]: Registration failed for: 10009@003; Cause: 503 Service Unavailable; warning: ; internal


В логах винды пишет следующие: [CM104001]: Registration at '35' failed. Host 'sip:[email protected]:5060' is not available! хост доступен и пингуется. Если убрать требование регистрации, то звонки через него ходят. Но у провайдера надо именно зарегистрироваться.

Провайдер говорит что к нему запрос на регистрацию приходит, но отображается что он пришел не с внешнего ip подсети, а с внутреннего ip АТС-ки поэтому их сервер не может понять как ему ответить. Все порты на роутере через который выходит АТС прокинуты. В настройках сети 3сх указана работа через stun, вот что в логах пишет атс-ка по поводу stun:10:47:26.507 [CM506001]: STUN request to resolve SIP external IPort mapping is sent to STUN server 96.9.132.83:3478 over Transport 192.168.1.11:5060

Вот что выдала проверка файерволла:
3CX Firewall Checker, v1.0. Copyright (C) 3CX Ltd. All rights reserved.

: Phase 1, checking servers connection, please wait...
: Stun Checker service is reachable. Phase 1 check passed.
: Phase 2a, Check Port Forwarding to UDP SIP port, please wait...
: UDP SIP Port is set to 5060. Response received correctly with no translation. Phase 2a check passed.

: Phase 2b. Check Port Forwarding to TCP SIP port, please wait...
: TCP SIP Port is set to 5060. Response received correctly with no translation. Phase 2b check passed.

: Phase 3. Check Port Forwarding to TCP Tunnel port, please wait...
: TCP TUNNEL Port is set to 5090. Response received correctly with no translation. Phase 3 check passed.

: Phase 4. Check Port Forwarding to RTP external port range, please wait...
: UDP RTP Port 9000. Response received correctly with no translation. Phase 4-01 check passed.
: UDP RTP Port 9001. Response received correctly with no translation. Phase 4-02 check passed.
: UDP RTP Port 9002. Response received correctly with no translation. Phase 4-03 check passed.
: UDP RTP Port 9003. Response received correctly with no translation. Phase 4-04 check passed.
: UDP RTP Port 9004. Response received correctly with no translation. Phase 4-05 check passed.
: UDP RTP Port 9005. Response received correctly with no translation. Phase 4-06 check passed.
: UDP RTP Port 9006. Response received correctly with no translation. Phase 4-07 check passed.
: UDP RTP Port 9007. Response received correctly with no translation. Phase 4-08 check passed.
: UDP RTP Port 9008. Response received correctly with no translation. Phase 4-09 check passed.
: UDP RTP Port 9009. Response received correctly with no translation. Phase 4-10 check passed.
: UDP RTP Port 9010. Response received correctly with no translation. Phase 4-11 check passed.
: UDP RTP Port 9011. Response received correctly with no translation. Phase 4-12 check passed.
: UDP RTP Port 9012. Response received correctly with no translation. Phase 4-13 check passed.
: UDP RTP Port 9013. Response received correctly with no translation. Phase 4-14 check passed.
: UDP RTP Port 9014. Response received correctly with no translation. Phase 4-15 check passed.
: UDP RTP Port 9015. Response received correctly with no translation. Phase 4-16 check passed.
: UDP RTP Port 9016. Response received correctly with no translation. Phase 4-17 check passed.
: UDP RTP Port 9017. Response received correctly with no translation. Phase 4-18 check passed.
: UDP RTP Port 9018. Response received correctly with no translation. Phase 4-19 check passed.
: UDP RTP Port 9019. Response received correctly with no translation. Phase 4-20 check passed.
: UDP RTP Port 9020. Response received correctly with no translation. Phase 4-21 check passed.
: UDP RTP Port 9021. Response received correctly with no translation. Phase 4-22 check passed.
: UDP RTP Port 9022. Response received correctly with no translation. Phase 4-23 check passed.
: UDP RTP Port 9023. Response received correctly with no translation. Phase 4-24 check passed.
: UDP RTP Port 9024. Response received correctly with no translation. Phase 4-25 check passed.
: UDP RTP Port 9025. Response received correctly with no translation. Phase 4-26 check passed.
: UDP RTP Port 9026. Response received correctly with no translation. Phase 4-27 check passed.
: UDP RTP Port 9027. Response received correctly with no translation. Phase 4-28 check passed.
: UDP RTP Port 9028. Response received correctly with no translation. Phase 4-29 check passed.
: UDP RTP Port 9029. Response received correctly with no translation. Phase 4-30 check passed.
: UDP RTP Port 9030. Response received correctly with no translation. Phase 4-31 check passed.
: UDP RTP Port 9031. Response received correctly with no translation. Phase 4-32 check passed.
: UDP RTP Port 9032. Response received correctly with no translation. Phase 4-33 check passed.
: UDP RTP Port 9033. Response received correctly with no translation. Phase 4-34 check passed.
: UDP RTP Port 9034. Response received correctly with no translation. Phase 4-35 check passed.
: UDP RTP Port 9035. Response received correctly with no translation. Phase 4-36 check passed.
: UDP RTP Port 9036. Response received correctly with no translation. Phase 4-37 check passed.
: UDP RTP Port 9037. Response received correctly with no translation. Phase 4-38 check passed.
: UDP RTP Port 9038. Response received correctly with no translation. Phase 4-39 check passed.
: UDP RTP Port 9039. Response received correctly with no translation. Phase 4-40 check passed.
: UDP RTP Port 9040. Response received correctly with no translation. Phase 4-41 check passed.
: UDP RTP Port 9041. Response received correctly with no translation. Phase 4-42 check passed.
: UDP RTP Port 9042. Response received correctly with no translation. Phase 4-43 check passed.
: UDP RTP Port 9043. Response received correctly with no translation. Phase 4-44 check passed.
: UDP RTP Port 9044. Response received correctly with no translation. Phase 4-45 check passed.
: UDP RTP Port 9045. Response received correctly with no translation. Phase 4-46 check passed.
: UDP RTP Port 9046. Response received correctly with no translation. Phase 4-47 check passed.
: UDP RTP Port 9047. Response received correctly with no translation. Phase 4-48 check passed.
: UDP RTP Port 9048. Response received correctly with no translation. Phase 4-49 check passed.
: UDP RTP Port 9049. Response received correctly with no translation. Phase 4-50 check passed.


Application exit code is 0

Помогите разобраться с проблемой почему не получается зарегистрироваться.

 

[vpaulo]

сделай не через стан, а укажи явно в параметрах айпи который должен посылаться оператору.

 

[anonymous]

Указал в поле Исходящий ip внешний адрес. 3сх теперь пишет что оператор зарегистрирован. но провайдер не видит у себя регистрации. Исходящие вызовы по этой линии на любой номер приходят на внутренниий номер оператора в моей АТС.

Если на ПК с АТС повесить внешний ip то на сервере провайдера регистрация проходит успешно.

 

[anonymous]

@Salmih wrote:Указал в поле Исходящий ip внешний адрес. 3сх теперь пишет что оператор зарегистрирован. но провайдер не видит у себя регистрации. Исходящие вызовы по этой линии на любой номер приходят на внутренниий номер оператора в моей АТС.

Если на ПК с АТС повесить внешний ip то на сервере провайдера регистрация проходит успешно.
Я Вам PM выслал...

 

[aleksandr]

http: //www.3cx.com/forums/podkljuchenie-k-operatoru-telphin-14780.html Вот здесь посмотрите как настраивались на провайдера Telphin. Там были похожие проблемы. Удалось их решить.

 

[anonymous]

Благодаря помощи с форума. удалось понять что с нашей стороны все настройки верные. В единственном месте упоминался наш внутренний адрес при запросе на регистрацию, это в заголовке Via. Но сама регистрация шла с нашего внешнего ip. После того как передал эти сведения провайдеру, тот изменил настройки и нам удалось зарегистрироваться!