Hi all,
my FreePBX 16 with Asterisk 20 is experiencing a strange issue on receiving incoming calls directed queues. When tracing SIP messages, PBX tears down the call with BYE message “x-asterisk-hangupcause 16", Unrecognized SIP headers. Same calls are successfully received when routed to extension or ring group, but entering into queues breaks the call down. Older Asterisk versions, such as v16 did not thave the same issue. Driver is chan_sip. Please advise. Thanks in advance,
Call logs in the URL:
https://pastebin.freepbx.org/view/4b9fe853
Call looks to be reaching a Queue (301)
Can you give us a little background about how the queue is configured?
Do you have agents inside that queue?
Hi Sergio,
call does indeed reach the queue 301. Queue has dynamic agents logged in:
301 has 0 calls (max unlimited) in ‘rrmemory’ strategy (0s holdtime, 0s talktime), W:5, C:0, A:0, SL:0.0%, SL2:0.0% within 60s
Members:
Agent 3013 (Local/3013@from-queue/n from hint:3013@ext-local) (ringinuse disabled) (dynamic) (Not in use) has taken no calls yet (login was 98405 secs ago)
Agent 3011 (Local/3011@from-queue/n from hint:3011@ext-local) (ringinuse disabled) (dynamic) (Not in use) has taken no calls yet (login was 98405 secs ago)
Agent 3009 (Local/3009@from-queue/n from hint:3009@ext-local) (ringinuse disabled) (dynamic) (Not in use) has taken 1 calls (last was 90288 secs ago) (login was 90550 secs ago)
Agent 3012 (Local/3012@from-queue/n from hint:3012@ext-local) (ringinuse disabled) (dynamic) (Not in use) has taken no calls yet (login was 98405 secs ago)
No Callers
The queue is answering the call and the PBX sends back a 200 OK to indicate the call has been answered. The provider didn’t respond at least twice to the 200 OK (it was retransmitted twice) and then the provider sends a BYE.
I’d be curious as to why they are not responding to the initial 200 OK and why they are sending a BYE.
There are no timestamps, which means you used the console, rather than the full log. As such I can’t tell whether the BYE was premature. Assuming it was, that is typically because the SDP response was unacceptable, although there is no obvious reason for that. I’d assume the same would apply if the caller tried to allocated a resource, at the point of answer, and was unable to do so.
There is no reason code to distinguish the BYE from resulting from the normal end of call, so you will need logs, from the remote side, to find out why it ended the call.
Hi David,
Please advise on how to collect full log.
I have a PCAP file which can be used for analysis. It can be seen that PBX sends BYE due to Unrecognized Headers, and I will upload it here.
Please see this pcap file.
Normally PBX would refer to Asterisk. What do you mean by PBX here, and please provide the logs you are relying on to say it is claiming unknown headers.
I believe the correct action on a unknown header is to ignore it, but there are no unusual headers in the response.
See How to view logs or call logs in an ssh client regarding Asterisk log files.
Hi David,
it seems OK now. Seems like disabling Sangomaconnect module when troubleshooting another ticket also contributed to resolution of this one. Thanks alot, I appreciate your help. I will bemonitoring the situation, and provide feedback if anything outstanding occurrs regarding this.
