Проблема с коннекцией на TCP 5060

anonymous

Well-Known Member
Регистрация
14 Янв 2008
Сообщения
19.170
Приветствую,
Есть проблема с коннекцией по TCP. У меня есть устройство, оно принимает по SIP только по TCP. Так уж сделано.
А 3CX ломится по UDP, причем самое странное, что то ломится то по TCP, то по UDP.
Дозвониться можно один раз из 3-4. Естественно это никуда не годится.
Как "заточить" 3CX на звонки поопределенному направлению только по TCP?
Сейчас стоит у меня 7-й 3CX.
Спасибо.
По трейсам я вижу
20:53:07.288050 IP sip.5060 > dsenvm.5060: UDP, length 800
20:53:07.288082 IP dsenvm > sip: icmp 556: dsenvm udp port 5060 unreachable
 
Your device should register against 3CX PBX using transport specification (TCP) in Contact header field. In this case PBX will use TCP connection to contact it back.
 
Thanks a lot. Sorry for such big delay but I found your answer only now.
Excuse me. How do I need to configure this field by 3CX? I don't see any possibilities for this. Everything is fixed for customizing.
 
Transport goes over Via
Via: SIP/2.0/UDP 192.168.2.109:5060;branch=z9hG4bK-d8754z-ca127e46e60bf96f-1---d8754z-;rport
Transport: UDP

It is INVITE from 3CX now.

I need the following:
Via: SIP/2.0/TCP 192.168.2.108:5060;branch=z9hG4bKD2E4034644938365135ea2.0,SIP/2.0/UDP 192.168.2.109:5060;psrrposn=1;received=192.168.2.109;branch=z9hG4bK-d8754z-a826da69b46b6f31-1---d8754z-;rport=5060
Transport: TCP

I had to install one more SIP server between 3CX and my equipment but it is bad.
 
Transport should be configured on your device. In Contact header which it sends -- it should specify "transport=TCP". It is good idea to make so in REGISTER and all consequent INVITEs. PBX is not configurable in this regards because it just uses information provided by device in incoming SIP requests. Via header is not used for consequent requests, because it just reflects transport used to deliver the message. It is used only to deliver reply to the message -- reply will be sent to the topmost Via using the transport it specifies.
 
Hi,
It looks as you are right person for such questions. :lol: Thanks.
Do I right understand that I need to put customized field "transport=TCP" to Outbound "Contact" field? But what is about add of Caller info to contact field?
Ok. I'll try. I don't know still how but I'll try. :roll:
I have one more complex question about 3CX.
I have incoming connection to 3CX from SIP SP. (Sipnet.ru). Everything is fine.
And I have IVR system which is connected to 3CX.
When I do tandem call from SP to IVR over 3CX I am lossing CPN. Voice is working fine. The issue with info.
When I configured outgoing SIP trunk to IVR I had to put AuthID. It is mandatory for 3CX.
And I have incoming call to IVR with CPN from AuthID which I configured to 3CX outgoing trunk to IVR.
It looks as 3CX can't send incoming CPN from "Contact' or 'From" to outgoing "Contact' or "From'. 3CX put it's AuthID or Extension number to "Contact" Field.
I did customization of outbound parameters. And It look as I can manipulate by Outgoing parameters only. I can't put Incoming info to Outgoing info.
Example: I have incoming call to 3CX. from SIP SP to xxxxx @10.10.10.10 with "From:[email protected]". I rerouted this call to outgoing trunk to IVR. I had to put AuthID 12345 because it is mandatory. My IVR doesn't need authorization. Need to send INVITE to IP only. But According to 3CX settings I had to put some AuthID. And I have outgoing call to IVR with "From:12345". An my IVR gets CPN: 12345. I need to get CPN: YYYYYYYY. It i my issue. Global issue.
Finally I can't get Incoming CPN to IVR. It is bad because my IVR needs to send feedback to mobile numbers according to incoming CPNs.
Actually Asterisk does this correctly but I prefer to move this task to 3CX. For me it looks more stable and understandable. :p
I really need the help about this. And more. I have 3CX7
 
Why not register your IVR as an extension, not trunk?
 
It is not possible.
It can receive INVITE only.
It doesn't do request for authorization. It doesn't ask autorization.
I need to send INVITE with CallerID and Called ID to dedicated IP.
I created SIP trunk without authorization. Why not? I had to put AuthID because it is mandatory for creation of trunk.
I rerouted from incoming trunk to External number. It is possible. Why Not?
I got a call to IVR. Everything is fine. IVR is SIP Adjunct. Very easy SIP Adjunct. It needs only incoming INVITE. It is not different SIP switch.
But I don't have CallerID because I had to put AuthID for outgoing trunk.
 
I'm pretty sure that SIP trunk scenario is also possible. I will come back later on with detailed solution.
You might be forced to set AuthID but I'm pretty sure that using a trunk doesn't force PBX to send any auth. as long as trunk's endpoint doesn't ask for it.
Also, using outbound params you can configure to send $CallerNum in whatever field you may need to.
 
1. Create a generic SIP trunk pointing it to IP:port of your IVR
2. Edit it, make sure that on 'Advanced' tab the field 'Require registration for:' is set to 'Do not require'
3. In Outbound Params tab set From:User to CallerNum
4. Make proper settings to other fields if necessary
5. Enjoy! :)
 
Hi,
I did so before. Without result.
1. The configuration of 'transport=TCP" in contact field for outboud parameters didn't help.
2. About issue with CallerID.
I did so as you told me. I did this before and now I upgraded my 3CX by 7.1b and the same still.
1. Create a generic SIP trunk pointing it to IP:port of your IVR
Created.
2. Edit it, make sure that on 'Advanced' tab the field 'Require registration for:' is set to 'Do not require'
Yes, of course.
3. In Outbound Params tab set From:User to CallerNum
Yes, sure. It is configured so.
4. Make proper settings to other fields if necessary
Nothing more.
5. Enjoy!
No. Sorry. 3CX sends AuthID still.
I really can send you screenshots and traces. It is really so. Actually I believe you can recreate the issue very easy.
To do tandem call and you can see. It is really so.
And additional. If you put * to Auth field and press "Ok" then you will get crash of web page.
 
@dsen wrote:1. The configuration of 'transport=TCP" in contact field for outboud parameters didn't help.

Ah, I forgot you need it in TCP. Well, than you can try to use FQDN as an address of SIP trunk and a technique described in RFC3263, somewhere around p. 4.1
Don't ask me 'how to setup my DNS'? I'm not network admin, you know.

@dsen wrote:No. Sorry. 3CX sends AuthID still.

Well, it is pretty strange. I would suggest you to describe this specific thing about AuthID in main english-speaking forum (you have excellent english for that). Than it may come back to me as a bug report and has a good chances to get resolved as a result.
Though I will try to look at it closer tomorrow if my list of urgent tasks will let me enough time. But if not - after tomorrow I will forget about it for sure. Sorry. Too much things to remember, you should understand.

Btw, what is tandem call you've mentioned?
 
Erm, tell me honestly, you aren't try to connect to MS Exchange's IVR, are you?
Because if you do - forget it. It is not possible using trunk. There's many other things on MS side which prevents normal TCP connection.
 
Ok. Will do.
Actually it is not ver critical task but quite urgent. Need to decide: Or move to Asterisk or move to 3CX.
It is Avaya IVR. Actually everything is working. For resolving of TCP issue I put one more SIP server with fixing transport for trunks.
I would like to skip it but it is not critical.
About second. Connection is established. Voice is going. Everything is fine. CallerID is absent only. We are starting IVR project with sending feedback to mobile numbers and we need CallerID mandatory.
Thanks. I'll put bug report to main forum.
 

Для администраторов

Статистика форума

Темы
20.795
Сообщения
104.449
Пользователи
69.695
Новый пользователь
PERRINBRI
Установите 3CX - Совершенно бесплатно!

Соединяйте сотрудников и клиентов Телефонная система Чат для сайта Видеоконференции

На хостинге или своих ресурсах. До 10 пользователей - бесплатно навсегда. Без банковских карт и рисков.

3CX
Аккаунт 3CX с таким e-mail уже существует. Вы будете переадресованы на Портал пользователя, где сможете ввести учетные данные или восстановить пароль.