search for: ubiphon

Displaying 4 results from an estimated 4 matches for "ubiphon".

Did you mean: ubiphone
2006 Nov 21
1
Hairping calls and Originating CLI
Skipped content of type multipart/alternative-------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 3659 bytes Desc: not available Url : http://lists.digium.com/pipermail/asterisk-users/attachments/20061121/10d6b6f8/smime-0001.bin
2007 Aug 14
1
Faulty voicemail
...bigradin-1 ","SIP/600-08e0b990","VoiceMail","u2000","2007-08-14 08:52:19","2007-08-14 08:52:34","2007-08-14 08:52:38",19,4,"ANSWERED","DOCUMENTATION" And my messages log for that time (for one failed call) shows: ubiphone*CLI> -- Accepting AUTHENTICATED call from 193.111.200.135: > requested format = alaw, > requested prefs = (), > actual format = ulaw, > host prefs = (ulaw|alaw), > priority = mine ubiphone*CLI> -- Executing Macro("IAX2/ubigrad...
2007 Sep 10
2
Siemans SIP/PSTN phone S450
...ust added a Siemens DECT SIP/PSTN S450 phone to login to my A*k server, and I see "Got SIP response 405 "Method Not Allowed" back from 192.168.3.64" but the phone seems to work ok. Any ideas where it falls over in the SIP protocol? I've included this in the debug below. ubiphone*CLI> <-- SIP read from 192.168.3.64:5060: --- (0 headers 0 lines) Nat keepalive --- ubiphone*CLI> <-- SIP read from 192.168.3.64:5060: --- (0 headers 0 lines) Nat keepalive --- -- Got SIP response 489 "Bad event" back from 192.168.3.10 ubiphone*CLI> <-- SIP read f...
2010 Nov 12
1
Context issue
...lled test-ubi/4201 And that test-ubi account on there has the same SIP account setup. The inbound server seems to skip the testinbound context completely though, jumping straight to incomming_pstn, but I've no idea why. I think it should be going to the context defined in test-ubi ubiphone*CLI> -- Executing [4201 at incomming_pstn:1] Answer("SIP/192.168.50.132-b7d4f6b0", "") in new stack -- Executing [4201 at incomming_pstn:2] SayDigits("SIP/192.168.50.132-b7d4f6b0", "2333") in new stack -- <SIP/192.168.50.132-b7d4f6b0>...