Hey all,
Just ran into a segfault. Happens almost right on startup with load. Not sure
of the cause. Any ideas? Segfault goes away when traffic is removed. Let me
know if I can provide more information. Thanks!
-Brett
dmesg shows this:
opensips[81661]: segfault at 0 ip 004bf1c7 sp 000
Hi Laszlo,
Unfortunately the effect for the caller would be the same - ringback would
stop.
Here's the whole flow. My terminating gateway is SIP to ISDN PRI. Call
terminates through the gateway to a particular mobile switching office. I
receive an ISDN PROGRESS message with inband audio. This
What if you simply drop the 180 in the onreply_route?
-Laszlo
2013/9/23 Jeff Pyle
> Hello,
>
> I have one particular PSTN call flow that causes a 183 with SDP, then a
> 180 without SDP prior to 200 OK. Some of my customer endpoints don't
> handle the 180 properly after a 183 and they cease to
The same behavior has appeared on the same system, this time causing it to
stop functioning. Logs show:
opensips[21368]: ERROR:core:parse_from_header: out of pkg_memory
opensips[21368]: ERROR:uac:restore_uris_reply: failed to find/parse FROM hdr
opensips[21368]: WARNING:core:fm_malloc: Not enough
Hello,
I have one particular PSTN call flow that causes a 183 with SDP, then a 180
without SDP prior to 200 OK. Some of my customer endpoints don't handle
the 180 properly after a 183 and they cease to hear ringback.
I'm thinking through how intercept the 180 and convert it to a 183 with
SDP. I
