search for: easybel

...erwise I'm >> getting the error message and asterisk does not register. >> >> Reading the comments in sip.conf.sample, I would assume that asterisk >> can not verify the certificate of the SIP provider.  Yet >> >> >> openssl s_client -connect secure.sip.easybell.de:5061 > > You know that you don't need an own certificate to connect via tls to the ISP? No, I didn't know that. However, there are local clients connecting to asterisk using encryption, so I suppose my own certificate is required. > To be able to verify the certificate of t...

...36c .Transaction created for Request msg REGISTER/cseq=36181 (tdta0x721d90) [Dec 22 19:24:24] DEBUG[25247] pjsip: tsx0x110736c Sending Request msg REGISTER/cseq=36181 (tdta0x721d90) in state Null [Dec 22 19:24:24] DEBUG[25247] pjsip: sip_resolve.c .Starting async DNS A query: target=sip1.easybell.de, transport=Unspecified, port=5060 [Dec 22 19:24:24] DEBUG[25247] pjsip: resolver.c .Transmitting 34 bytes to NS 0 (192.168.178.1:53): DNS A query for sip1.easybell.de: Success [Dec 22 19:24:24] DEBUG[25247] pjsip: tsx0x110736c .State changed from Null to Calling, event=TX_MSG [Dec...

...what is going on. > I attached the debug output I already created before. Interesting part starts around line 2740. 91 -> local pjsip fax-extension 127.0.0.1:5061 -> asterisk server local connect for fax-extension (-> not encrypted even if it is port 5061!) external fax number at easybell (195.185.37.60), which is called and which is answered here: 11111222222 Thanks, Michael -------------- next part -------------- A non-text attachment was scrubbed... Name: t38.debug.bz2 Type: application/x-bzip Size: 23348 bytes Desc: not available URL: <http://lists.digium.com/pipermail/a...

...ers to the SIP provider and there is no error message). Otherwise I'm getting the error message and asterisk does not register. Reading the comments in sip.conf.sample, I would assume that asterisk can not verify the certificate of the SIP provider. Yet openssl s_client -connect secure.sip.easybell.de:5061 seems to verify the certificate just fine. Previous tests seemed to show the asterisk is trying to verify its own certificate instead, or as well. What exactly is asterisk trying to verify, and what fails the verification? Suspicious is this: [Jul 5 12:48:00] NOTICE[7015]: chan_si...

On Mon, Jun 5, 2017, at 04:26 PM, Michael Maier wrote: > On 06/05/2017 at 06:29 PM, Joshua Colp wrote: > > On Mon, Jun 5, 2017, at 01:22 PM, Michael Maier wrote: > >> > >> Do you have any idea where to start to look at? Adding additional output > >> in the source code? Which functions could be interesting? I may add own > >> debug code to see why things

...cessing incoming message: Request msg INVITE/cseq=10 (rdata0x7f5f1801a758) <--- Received SIP request (918 bytes) from UDP:195.185.37.60:5060 ---> INVITE sip:+4911111111111 at 42.13.16.27:5061 SIP/2.0 Via: SIP/2.0/UDP 195.185.37.60;branch=z9hG4bKHeVwGavN;rport From: <sip:111111111111 at sip.easybell.de>;tag=72F0675F-5942027B00075955-FB9F9700 To: <sip:+4911111111111 at sip.easybell.de>;tag=f045584d-da09-4913-9b46-102361e397f2 CSeq: 10 INVITE Call-ID: 7f582402-0ce9-4a1a-87f6-b8de8b2a7bc8 Max-Forwards: 68 Allow: OPTIONS, SUBSCRIBE, NOTIFY, PUBLISH, INVITE, ACK, BYE, CANCEL, UPDATE, PRAC...

Hello! I'm facing ReInvites as caller from UAS despite configured session-timers=refuse (which can be seen in the SIP trace) always after 900s. (The behavior is the same if session-timers is set to accept). This just happens with one provider (German Telekom to callee at kabelbw). - The incoming ReInvite is answered immediately by asterisk (Status 100 / Status 200 - 0.02s). Media stream

...es basically unusable :( > > There are various options in the outbound registration that controls > behavior. I'd suggest providing your actual configuration. I have put the options that should make asterisk re-register in pjsip_wizard.conf as much as I could find them like this: [easybell_HW] type = wizard sends_auth = yes sends_registrations = yes max_retries = 0 auth_rejection_permanent = no forbidden_retry_interval = 200 transport = transport-tls endpoint/cos_audio = 5 endpoint/cos_video = 4 remote_hosts = secure.sip.easybell.de:5061 aor/qualify_frequency = 30 outbound_auth/user...

...Interesting part starts around line 2740. > > > > > > 91 -> local pjsip fax-extension > > > > 127.0.0.1:5061 -> asterisk server local connect for fax-extension (-> > > not encrypted even if it is port 5061!) > > > > external fax number at easybell (195.185.37.60), which is called and > > which is answered here: 11111222222 > > And the pjsip.conf endpoint entry for easybellPJSIP_FAX? I plugged the provided configuration into an existing testsuite test quickly and things still worked as expected, so it's something outside of...

On 06/14/2017 at 05:53 PM Joshua Colp wrote: > On Wed, Jun 14, 2017, at 12:47 PM, Michael Maier wrote: > > <snip> > >> >> I added this patch to see, if really all packages are are freed after >> they have been processed: >> >> --- b/res/res_pjsip/pjsip_distributor.c 2017-05-30 19:44:16.000000000 >> +0200 >> +++

Hello! unchanged asterisk crashes during udptl / t.38 negotiation with telekom - they do not support t.38 / udptl. In detail: fax client -> asterisk -> telekom -> easybell -> asterisk -> fax server Fax server sends t.38 reinvite via asterisk to easybell. Session Description Protocol Version (v): 0 Owner/Creator, Session Id (o): - 2447581897 4 IN IP4 46.17.15.23 Session Name (s): Asterisk Connection Information (c): IN IP4 46.17.15.23 Time Des...

Hi, how do I make a bug report? I filled in the form to make a report and https://issues.asterisk.org/jira/issues/?filter=-2 still shows no issues reported by me. If someone knows how to get asterisk to re-register when using pjsip after the registration shows as Rejected, like after the internet connection to the VOIP provider goes away (and comes back), please let me know. This bug makes

On 7/5/19 9:22 PM, Steve Murphy wrote: > hw-- > > I see this kind of behavior when the certificate expires... you've > probably checked this, but sometimes we > miss little details like that. I thought about that and checked the configuration I've been using to create the certificate, and I can't see anywhere that it would expire earlier than after 3650 days. Is

On 06/04/2017 at 01:41 PM Telium Technical Support wrote: > Just a guess (without knowing about your network), but are the two ends > points on public networks and visible to one another? If not the reinvite > may be passing an internal (nat'ed) address to the other and the connection > will fail...just a though t38modem -tt -o /var/log/t38modem.log --no-h323 -u 91 --sip-listen