[asterisk-bugs] [JIRA] (ASTERISK-25097) Asterisk13.3.2 PJSIP configuration user_agent doesn't go into effect

[Rusty Newton (JIRA)]

    [ https://issues.asterisk.org/jira/browse/ASTERISK-25097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=226275#comment-226275 ] 

Rusty Newton commented on ASTERISK-25097:
-----------------------------------------

We appreciate the difficulties you are facing, however this does not appear to be a bug report and your request or comments would be better served in a different forum.

The Asterisk community provides support over IRC, mailing lists, and forums as described at http://asterisk.org/community. The Asterisk issue tracker is used specifically to track issues concerning bugs and documentation errors.

Please see the Asterisk Issue Guidelines [1] for instruction on the intended use of the Asterisk issue tracker.

Thanks!

[1] https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines



> Asterisk13.3.2 PJSIP configuration user_agent doesn't go into effect
> --------------------------------------------------------------------
>
>                 Key: ASTERISK-25097
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-25097
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: pjproject/pjsip
>    Affects Versions: 13.3.2
>         Environment: raspbian wheezy on raspberry pi 2, OpenWRT Chaos Calmer on Linksys WRT1900ac
>            Reporter: Pablo Perla Hernandez
>
> With asterisk 13.3.2, provided a pjsip.conf file properly configurated with a global section like the following:
> [global]
> user_agent=Technicolor TG784n v3 Build 8.G.D.4
> default_outbound_endpoint=OutEndpoint
> Or with the user_agent variable set inside an endpoint:
> [endpoint]
> 100rel=yes
> rtp_engine=asterisk
> user_agent=Technicolor TG784n v3 Build 8.G.D.4
> sdp_session=Technicolor TG784n
> It doesn't change the user agent when sending the REGISTER messages to the SIP as seen in this message:
> REGISTER sip:111.111.111.111:5060 SIP/2.0
> Via: SIP/2.0/UDP 222.222.222.222:5060;rport;branch=z9hGabKPj84b86ce5-d65b-4149-8210-37d1g5d2e49e
> From: sip:+34917722311 at sip.domain.net;tag=ea7fd10c-b891-44ec-b9c6-373f6b077eff
> To: sip:+34917722311 at sip.domain.net
> Call-ID: ae95faf2-c8ad-4a4a-88fd-08a3a07151c7
> CSeq: 19574 REGISTER
> Contact: sip:s at 222.222.222.222:5060
> Expires: 3600
> Allow: OPTIONS, SUBSCRIBE, NOTIFY, PUBLISH, INVITE, ACK, BYE, CANCEL, UPDATE, PRACK, REGISTER, MESSAGE, REFER
> Supported: path
> Max-Forwards: 70
> User-Agent: Asterisk PBX 13.3.2
> Content-Length: 0
> This is working fine in the 13.2.0 version, it is causing my VoIP provider filter out the packages and not allowing me to register.
> PD: /paranoid mode on, personal information already modified both in packet info and ip/info



--
This message was sent by Atlassian JIRA
(v6.2#6252)