My Trunk is successfully registered and work Properly when i dial calls from Extension. But i have activated find me follow me when extension is not reachable calls have to through trunk but this time it instantly show forbidened i have attached a detailed log pastebin Logs - FreePBX Pastebin
You received a malformed proxy authorisation request.
1987 SIP/2.0 407 Proxy Authentication Required
1988 Call-ID: 8c373939-8bc4-4a56-b758-264372f95423
1989 Via: SIP/2.0/UDP 10.15.250.138:5060;received=10.15.250.138;branch=z9hG4bKPj0a7e7122-784c-4a81-b3b7-accdf37120d5;rport=5060
1990 To: <sip:[email protected];user=phone>;tag=64827141-674deea221685bd;_intrsp_
1991 From: "192.168.70.34" <sip:[email protected]>;tag=f35f3f9d-a257-49ce-9847-a3b62f67e49a
1992 CSeq: 10180 INVITE
1993 Date: Mon, 02 Dec 2024 17:30:10 GMT
1994 Content-Length: 0
See the second item on page 163 of RFC 3261: SIP: Session Initiation Protocol which is mandatory, but not present.
At a guess, it is because the provider doesn’t like your from header. You have an IP address where a phone number would normally be expected.
As well as being an unusual user part, it is possible that the provider expects to see your official caller ID, rather than one passed through. As a further guess, I think the endpoint is trying to hide that fact that it is actually refusing the request, by sending the same response as it would if it wanted you to authorise it, but it is doing so wrongly, in that the missing header indicates it isn’t a genuine challenge for authentication.
1 Like
@david55 what is solution of this problem?
Answering that requires information about what you intended to send as the caller ID, and what the provider considers acceptable. I can only say what you actually sent, and possible reasons why that might cause problems.
The problem with the malformed 407 response can only be fixed by the provider. I can’t tell, for certain, whether you would have succeeded with a well formed request, although, as I said, I suspect it is mock response, and it really means you haven’t been recognized as a valid user of the service.
If they are expecting your account name, or public phone number, in the From header, I believe there are number of ways of fixing that, e.g. setting an explicit From user in the trunk definition, although there are several other places where the caller ID can be overridden.
I believe this describes the options for setting caller ID on follow me:
1 Like
Thank you point out issue. @david55. If I use custom dial plan this will help tackle the issue
@david55 i am working on this and still unable to solve the kindly help me with technical assistance
I don’t believe overriding the caller ID for follow me, or for an outbound route, requires custom code. If the problem isn’t the From user, or the correct value to send is not obvious, you will need help from the provider.
Changing the caller ID for follow me is documented at: https://sangomakb.atlassian.net/wiki/spaces/PG/pages/23593115/Follow+Me+User+Guide#Change-External-CID-Configuration
It looks like the follow me set value overrides the outbound route one: https://sangomakb.atlassian.net/wiki/spaces/PG/pages/26181933/Outbound+Routes+Module+User+Guide#Route-CID
Controlling the caller ID at the trunk level is described in https://sangomakb.atlassian.net/wiki/spaces/PG/pages/25690439/Trunks+Module-User+Guide#CID-Options
This version of the documentation doesn’t mention a GUI way of changing the From user, if it is not being used for caller ID, but that might have been added since, and is only relevant when you are doing strange things with PAI or RPID headers.
No Luck
This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.