M
M
Morty Rick2017-06-13 09:38:01
Asterisk
Morty Rick, 2017-06-13 09:38:01

How to fix INVITE header in asterisk?

There is a registered trunk on the asterisk with some cloud PBX.
When registering, I see from them:
Reg. Contact : sip : [email protected]ххх.ххх.ххх.ххх :5060;vireg =
ххххххххххххххх_15 IP:5060 SIP/2.0 And representatives of this cloud ast say that INVITE should contain this unknown parameter vireg=хххххххххххххххх_15 That is, it should look like this: Request-Line: INVITEsip:[email protected]:5060;vireg=ххххххххххххх_15 SIP/2.0
how can the header be modified using asterisk? I didn't find anything about vireg in rfc. On the asterisk forums, I did not see data on the Request-Line modification anywhere

Answer the question

In order to leave comments, you need to log in

3 answer(s)
G
gosha-z, 2017-06-13
@gosha-z

And how do these representatives justify the need for this parameter?

D
Dmitry Shitskov, 2017-06-13
@Zarom

Try writing like this:
This is part of the problem. You will also need to save the vireg received from the provider in the database (for example, Asterisk itself) and substitute it in Dial

M
Morty Rick, 2017-06-13
@MortyRick

Everything turned out to be much simpler:
The INVITE header of the packet differs depending on how the call is sent:
If you send (there may be discrepancies in terminology) as a final peer:
DIal(SIP/trunk_name,90,m)
Then in tcpdump I see Request-Line: INVITEsip :[email protected]:5060;vireg=ххххххххххххххххх_15 SIP/2.0
That is exactly as specified in Reg. contact.
And if you send it as a sip trunk, sending a DID number:
DIal(SIP/trunk_name/5555555,90,m)
Then I see Request-Line: INVITE sip:[email protected]:5060 SIP/2.0
The problem is solved, but if someone can explain the reason, I will be grateful.

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question