Hi,
So all you've gotta do with sngrep is select an INVITE and press Enter...it
will open up the whole signalling flow, you can use arrow keys up and down
to inspect individual packet as well. I was expecting that it'll be easier
for you to just start using it right away.
*Idx:*[ ] 1
*SIP
Can you use this to capture the signaling for reading and relaying here?
I'm assuming you are only listening on port 5060. Your details on the
packets do not help with a resolution.
ngrep -d eth0 -t -W byline "$1" port 5060 -q
Jeff Wilkie
Chief Technology Officer
US IP Communications
When i analyse the output of the command sngrep, there is something i don't
understand,
the sip to = 0972550428@10.7.1.68
I recognize the 0972550428, but don't recognize the other part. What that
mean?
Since yesterday i'm searching why the INVITE is rejected in Opensips.
Can somebody help please?
Hi.
Sometimes, the log of my OpenSIPS shows warnings like this:
Apr 14 00:04:33 colibri-imx6 opensips[6909]: Apr 14 00:04:30 [6918]
WARNING:core:handle_timer_job: timer job has a 52 us delay in
execution
Apr 14 00:04:36 colibri-imx6 opensips[6909]: Apr 14 00:04:30 [6920]
I'm trying to record ACCounting on a different database to the rest of
opensips.
Opensips is going to replace a gateway in asterisk which is currently
recording CDRs to a MSSQL database. the Billing is generated from there.
I'm happy that opensips uses MySQL locally, but would like the
Hello,
I setup a real provider and register opensips at the provider using username
and password i got from there.
Here is the call trace; anonymous@anonymous.inval is the number i used to
call my DID
root@front-2:/etc/opensips# sngrep -d eth0 -O save.pcap port 5060 and udp
