It was originally varchar(50) and contained mailbox@context -- but that didn't work, so we tried changing it to bigint(10). It's been changed back and does contain varchar(50) with mailbox@context now.
Everything else seems to be working properly, yes. Here's one entry from our realtime table (MySQL): INSERT INTO `` (`id`, `name`, `username`, `secret`, `callerid`, `context`, `mailbox`, `mwi`, `host`, `setvar`, `nat`, `type`, `accountcode`, `amaflags`, `call-limit`, `callgroup`, `cancallforward`, `canreinvite`, `defaultip`, `dtmfmode`, `fromuser`, `fromdomain`, `insecure`, `language`, `md5secret`, `deny`, `permit`, `mask`, `musiconhold`, `pickupgroup`, `qualify`, `regexten`, `restrictcid`, `rtpholdtimeout`, `rtptimeout`, `disallow`, `allow`, `parkinglot`, `fullcontact`, `ipaddr`, `port`, `regserver`, `regseconds`, `lastms`, `defaultuser`, `subscribecontext`, `useragent`, `limitonpeers`) VALUES (96, '7191111111', '7191111111', '000000000000000000000000', NULL, 'outbound', '7191111111@default', NULL, 'dynamic', NULL, 'yes', 'friend', NULL, NULL, 2, NULL, 'yes', 'no', NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, 'all', 'ulaw', NULL, ' sip:7191111111@10.105.14.7:5060', '10.105.14.7', 5060, NULL, 1416407370, 6, '7196868170', NULL, 'Linksys/SPA2102-5.2.10', NULL); And then what "sip show peer 7191111111" shows: *CLI> sip show peer 7196868100 * Name : 7191111111 Description : Realtime peer: Yes, cached Secret : <Set> MD5Secret : <Not set> Remote Secret: <Not set> Context : outbound Record On feature : automon Record Off feature : automon Subscr.Cont. : <Not set> Language : Tonezone : <Not set> AMA flags : Unknown Transfer mode: open CallingPres : Presentation Allowed, Not Screened Callgroup : Pickupgroup : Named Callgr : Nam. Pickupgr: MOH Suggest : Mailbox : VM Extension : *98 LastMsgsSent : 32767/65535 Call limit : 2 Max forwards : 0 Dynamic : Yes Callerid : "" <> MaxCallBR : 384 kbps Expire : 53 Insecure : no Force rport : Yes Symmetric RTP: Yes ACL : No DirectMedACL : No T.38 support : No T.38 EC mode : Unknown T.38 MaxDtgrm: 4294967295 DirectMedia : No PromiscRedir : No User=Phone : No Video Support: No Text Support : No Ign SDP ver : No Trust RPID : Yes Send RPID : Yes Path support : No Path : N/A TrustIDOutbnd: Legacy Subscriptions: Yes Overlap dial : Yes DTMFmode : rfc2833 Timer T1 : 500 Timer B : 32000 ToHost : Addr->IP : (null) Defaddr->IP : (null) Prim.Transp. : UDP Allowed.Trsp : UDP Reg. exten : Def. Username: 7191111111 SIP Options : (none) Codecs : (ulaw) Auto-Framing : No Status : UNKNOWN Useragent : Linksys/SPA2102-5.2.10 Reg. Contact : sip:7191111111@10.106.1.17:5060 Qualify Freq : 60000 ms Keepalive : 0 ms Sess-Timers : Accept Sess-Refresh : uas Sess-Expires : 1800 secs Min-Sess : 90 secs RTP Engine : asterisk Parkinglot : Use Reason : No Encryption : No On Wed, Nov 19, 2014 at 7:12 AM, Matthew Jordan <mjor...@digium.com> wrote: > On Tue, Nov 18, 2014 at 6:36 PM, Jayson Baker <jay...@spectrasurf.com> > wrote: > > Using realtime for SIP. > > Using standard DB schema. > > Tried mailbox as varchar(50) and bigint(10) > > "sip show peer XXX" shows "Mailbox: " (empty) > > So MWI isn't working > > The "mailbox" column in a database schema should be varchar, and big > enough to hold a fully qualified mailbox name. > > > This happened before when we tried to go up to 1.8, so we stayed at 1.4 > > We're forced to go to 13 now. Obviously a lack of MWI is a big issue for > > 500 units. > > > > Any idea why we're not getting it? > > We're tried filling it into MySQL like "xxx@context" or just "xxx" > > No matter what, it doesn't work. > > Per the CHANGES notes, you must now fully qualify a mailbox: > > * Mailboxes defined by app_voicemail MUST be referenced by the rest of the > system as mailbox@context. The rest of the system cannot add @default > to mailbox identifiers for app_voicemail that do not specify a context > any longer. It is a mailbox identifier format that should only be > interpreted by app_voicemail. > > So, if using app_voicemail, your mailboxes should always be > 'xxx@vm_context' where appropriate. I don't think this is your problem > however. > > > Or maybe some how to debug/diagnose this? > > > > Are the rest of the fields in your peers being extracted correctly? > Can you provide the output from your database for one of your peers? > Which realtime backend are you using? > > > -- > Matthew Jordan > Digium, Inc. | Engineering Manager > 445 Jan Davis Drive NW - Huntsville, AL 35806 - USA > Check us out at: http://digium.com & http://asterisk.org > > -- > _____________________________________________________________________ > -- Bandwidth and Colocation Provided by http://www.api-digital.com -- > New to Asterisk? Join us for a live introductory webinar every Thurs: > http://www.asterisk.org/hello > > asterisk-users mailing list > To UNSUBSCRIBE or update options visit: > http://lists.digium.com/mailman/listinfo/asterisk-users >
-- _____________________________________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- New to Asterisk? Join us for a live introductory webinar every Thurs: http://www.asterisk.org/hello asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
